For CTOs, VPs of Engineering and tech leads
Your team got faster. Did the product?
AI made building cheap and fast. It made deciding and specifying the bottleneck, and most teams haven't reorganised around that yet. I set up the product side so the speed turns into shipped, measured outcomes rather than rework.
Sound familiar?
The agents are fast. The specs aren’t.
Coding agents build whatever they’re given, so a one-line ticket now becomes the wrong feature in an afternoon instead of a fortnight. The bottleneck moved to the brief and nobody updated the process.
Rework is eating the speed
Build time dropped; review-and-redo time didn’t. If a third of tickets come back, the team isn’t faster, it’s busier.
You’re making product calls you didn’t sign up for
When nobody owns the product decision, it lands on engineering by default. You can make those calls, but it isn’t your job and it isn’t what you’re measured on.
The board wants an AI story you can stand behind
You’d like to say the team is measurably faster and the quality held. Right now you’d be guessing.
What I'd suggest
To see the method first
Workshop
From £2,500, half a day
Spec-driven delivery, practised on one of your real features, with templates you keep. Credited against the full setup.
The main thing
AI Delivery Setup
From £15,000, four to six weeks
Spec standard, toolchain in your tools, review gates, one real feature shipped through it with before-and-after numbers, and a playbook the team keeps.
If the product seat is empty
Fractional Head of Product
From £5,000/month
Someone who owns the product calls, reads the code, and gives you a straight answer on trade-offs, one or two days a week.
Not sure where you stand? The free assessment takes five minutes, and you can share your roadmap for a personalised read. The £195 personal review gets you my own read on your roadmap.
Questions people ask
- Isn’t this a product problem, not an engineering one?
- It’s both, which is why it falls between the two. I work with the engineering lead and whoever owns product (often the founder) so the spec standard is one the team will actually use, and the product decisions get made by someone with the authority to make them.
- Which tools do you set this up in?
- Yours. I’ve built it on Claude, Linear, Notion and GitHub; it ports to Jira, Confluence and whatever agents you run. The method matters, the tools are interchangeable.
- Will this slow the engineers down?
- For about a week, while the spec standard beds in. Then it speeds them up, because they stop building the wrong thing and stop waiting on clarification. The pilot feature is how we prove that with your numbers rather than my claims.
- Can we start small?
- Yes. The half-day workshop (From £2,500) covers the method with your team on one of your real features, and is credited in full against the full setup.
Talk through where the time goes
Thirty minutes. Bring a recent feature that took longer than it should have; we'll trace where the time went.
Taking on one new client from November 2026.