Engineering leadership · AI-augmented teams
You adopted the tools. We fix how you lead, measure, and hire around them.
Your best engineers are drowning in review load. Your juniors aren't growing the way they used to. And you genuinely can't tell whether any of it made you faster. That's not a tooling problem. It's a leadership one.
Operators who’ve held the chair · still shipping production code · vendor-neutral on tools
01/The opening
The gap between felt speed and proven outcome.
AI-assisted development crossed from novelty to default. Teams ship faster — they can feel it. What almost nobody can answer is the next question: are we actually more productive, or just busier?
The tools landed; the org chart didn’t change to match. Leaders now run teams whose output they can’t cleanly measure, whose juniors aren’t learning the way they used to, and whose hiring signal has quietly died. That gap is the whole job.
And some of the best leaders we meet are quietly wearing the person-suit of the role — performing the engineering leader they were eighteen months ago, running the playbook that used to work, while the ground under the job moved beneath them. It isn't impostor syndrome. The role genuinely changed underneath you. That's fixable — but only once we're willing to name it.
“Your DORA dashboard is lying to you.”
Read the manifesto02/The product surface
One operating system. Four pillars.
Managing the augmented team is the wedge — the thing you feel first, at 2am. Performance management is where the felt problem gets instrumented and acted on. Hiring decides who you’re amplifying in the first place. Governance keeps the whole thing auditable.
- 01
Managing the augmented team
Your best developers can suddenly do it alone — and some will wonder why they shouldn't.
Used well, AI turns ordinary developers into something close to 10x — but that's a leadership problem disguised as a productivity win. The job shifts from writing code to conducting it, and two new gaps open up: managers who were never taught to lead an AI-amplified developer (it is not the same job), and the amplified developers themselves, who quietly realise they could ship without you. Get it wrong and your seniors burn out, your juniors never build the mental models, and your strongest people start working for themselves long before they hand in notice. Get it right and the whole team levels up — and stays.
See the work - 02
Team performance management
An honest number is worth nothing until someone acts on it.
Measuring the team truthfully is step one — and most dashboards fail even that (see the manifesto). Step two is the harder one: turning the picture into action. Which managers are quietly underwater. Who on the team has checked out and needs a real conversation this week. Which conditions — not which people — predict good engineers leaving, so you can fix them while it's still cheap. Performance management in an AI-amplified team isn't a ranking exercise; it's knowing where to put your attention before the cost shows up in someone's resignation.
See the work - 03
Hiring & interviews in the age of AI
The take-home is dead and you already know it.
Coding tests and take-homes have lost their signal — anyone can submit work that isn't theirs. AI widens the gap between strong and weak engineers rather than closing it, which makes the interview more important, not less. And the interview itself has to change: testing recall of syntax is pointless when the machine has all of it; what you're now hiring for is judgement, review skill, and the ability to reason about code they didn't write. Most teams also have no policy at all on AI in the interview — allowed, banned, or watched — so they're flying blind on the one decision that compounds hardest.
See the work - 04
Governing AI in the SDLC
Everyone's using it. Nobody's governing it.
The bottleneck moved from writing code to reviewing and governing it. Most organisations stall between experimentation and scale — pockets of heavy use, no shared standard, no audit trail, and a growing unease about what's shipping and who's accountable for it.
See the work
03/How we work together
A ladder, not a retainer trap.
Start small and paid. Each rung earns the next, and every engagement leaves a working artifact behind — never just a deck.
Engineering Leadership Diagnostic
£5,000
A scored maturity assessment across the four pillars, plus a prioritised 90-day action plan. Credited in full against a programme if you go further.
You leave knowing exactly where you stand — and what the gap is costing you.
Fixed-scope programmes
£35,000–95,000
Managing the Augmented Team · Team Performance Management · Hiring & Interview Redesign · SDLC Redesign. Each ships a working artifact — a live picture of team health, a real handbook, an interview loop, a governed workflow.
Never just recommendations. Something that works, in your hands.
AI-Era Engineering Advisor
From £12,000 / month
An ongoing advisor relationship for leaders who'd rather have senior operators on call than keep rebuilding the playbook alone every month. A small number of seats, held open by invitation.
The annuity layer — opened once a programme has proven its value.
We work with a small number of teams at a time, and we don't compete on price. If the fee is the hard part of the decision, we're probably not the right fit yet — the teams that get the most from this are already losing far more than it costs to the problem it solves.
04/Why us
Operators who’ve held the chair — and still ship.
Not a strategy deck and not a tool reseller. People who have carried the pager, made the calls, and are hands-on in AI-augmented builds today.
Held the chair. Still ship the code.
We've run engineering as CTO and VP — and we still ship production software today, across native mobile, embedded, backend AI/ML, and on-device edge AI. We've lived both the leadership problem and the hands-on AI-augmented build. Most advisors have done one or the other.
We've been the 10x developer who left — so we know how to keep yours.
We know the amplified developer who realises he could ship alone, because we've been him. That's exactly why we know what makes those people stay: how to scale a regular developer into a 10x one with AI, what managers get wrong with them, and how to keep your strongest people building for the team instead of quietly building for themselves.
Depth most AI consultancies can't reach.
Native mobile, embedded and edge, the AI/ML backend behind it, and — the rare part — deploying AI to run on the device itself, with the UI/UX to make it usable. The leadership advice is credible because the hands are real, in the hardest corner of the field.
Vendor-neutral advice. Optional instruments — never a stack sell.
No AI tool to resell, no kickback, no allegiance: which tools your team codes with is your call, and we take nothing from that decision. The only tools we ever bring are our own measurement instruments, which read your team's health and push nothing into your stack. Neutral advice, optional add-on, hard line between the two. This is not Copilot training with a consultancy invoice attached.
Anchored to before-and-after numbers.
Every engagement ties to outcomes you can measure, starting with our own. The first proof is our proving ground — real production apps, shipped on the same AI-augmented workflow we bring to you, with the bottleneck tracked to where it actually moved.
Start here
See where your team actually stands.
A four-minute self-assessment across the four pillars — with a maturity read and your most urgent next move. No email required to see your result.