About

I have built seven engineering teams. When AI arrived, my playbook for that stopped working.

I have built two startups, one of which won the Top Innovation Award at the India Innovation Growth Programme, run with Stanford GSB. Across twenty years I have built seven engineering teams, mostly in core engineering, and what I have always cared about is engineering efficiency: how a team actually turns intent into shipped software, and where that leaks.

When AI arrived, the playbook stopped working. Agents made writing cheap, and nothing downstream got cheaper. So I went deep into what replaces it, and that is now the whole of my work: the software factory, four pieces, built inside a real organisation with its real repositories, conventions and approval boundaries.

I contract on outcomes, not time. A small number of defined dones, written down before we start, and payment tied to those rather than to days spent. No FTE, no open-ended retainer. It is the difference between a transformation that lands and a pilot that stops without anyone deciding to stop it.

Ways to work together

The factory build

Six weeks or so. Discovery and a validation baseline, then the four pieces built to fit your organisation, then integrated and gated, then owned by your team. Four dones, not a calendar.

The one-hour session

For founders and engineering leaders. The maturity ladder so you can place your own team on it, what a software factory is and is not, where teams stall, the baseline to capture before starting, and how to contract this so it produces an outcome instead of a pilot.

Senior peer advisory

For leaders already at the frontier who want the live decisions pressure-tested: squad shape, agent boundaries, context engineering, build versus buy. Judgement, not deliverables.

Book a conversation