Product leadership
Fractional or interim. For leadership teams with engineers and budget but nobody owning what gets built and why. Fewer things, shipped on time.
Fifteen years, forty products, and a company I now run with three people and a fleet of agents. I ask why before anything gets built, and I cut the roadmap before I add to it.
For fifteen years the expensive part of a product was building it. AI changed that. Now the expensive part is knowing what to build, for whom, and why. That is the question I ask first, and the one most teams skip.
He led with empathy, rigor, and an obsession with simplicity. 50,000 customers rapidly onboarded, and a product people still describe as just so easy to use, years later. Janaka doesn't just design interfaces; he builds trust.CAL.lk, on the retail investing product
His leadership of a small development team got our product to a stable production v1 which enabled us to go to market. When COVID put five hours of timezone between us, he maintained the communications and the roadmap.SaaS founder, six years as development lead
Grit, dedication, and determination. Highly ethical, always putting the interests of his customers and colleagues first.RMIT Activator, Melbourne
Also: Colombo Stock Exchange · metjip · Humanised Payroll · takso · Hendry Group · Common Code · RMIT · Beta Launch, forty people, fully remote, ISO 27001 · and thirty more on the Portfolio page.
In Sri Lanka one acre is less than what a normal person can afford, always rural, never the city. It was the size of plot I could buy after Melbourne, with the savings and the comforts gone.
First I built before there was a road, and everything cost five times what it should. Then I went organic with nobody who knew how, me included. Both times I had stopped asking why I wanted it. Every team I meet is making one of those two mistakes with AI.
Every engagement runs in that order. Read everything, talk to everyone separately, come back with one page: what to stop, what to keep, what to ship next. Then weekly. I stopped my own product, Teamchain, this way. The timing was off and the runway was short, so we lived to fight another day.
Fractional or interim. For leadership teams with engineers and budget but nobody owning what gets built and why. Fewer things, shipped on time.
One workflow at a time, where AI removes real hours. Built in your stack, measured against the manual way, handed over with the code. No wrappers.
Founders and leadership teams, in the room or remote. 120 people trained with RMIT Activator, USAID and ICTA, and the one sentence I keep having to say.
Three lines: what you're building, what you have to build it with, and what's not working. I reply within two working days, and the first question I ask is why.
janaka@oneacrefields.com