How we work
What working with us looks like
We work with your leaders to get more of the gains from AI through to your customers. Once the first change we agree on is live, you take your board an honest answer to whether your AI is paying off.

The method
The Four Handoffs
Engineers report working faster with AI, and too often that never reaches the customer. DORA, Google’s research program on software delivery, says in its 2026 report on AI returns that without the right organizational foundation, “AI creates localized pockets of productivity that are often lost in downstream chaos.” Those gains leak out at the handoffs, the points where work passes from one person or team to the next, and AI puts four of them under new strain.
Here is what we work toward at each one, each with a measure your CTO agrees on:
- Intent, strategy to the people building. Engineering time goes to your top goals, and you can see how much each one gets.
- Ownership, decision to owner. Less work waits on decisions, because everyone knows who can say yes.
- Review, AI output to trusted code. Fewer mistakes reach your customers, and finished work reaches them sooner.
- Learning, one engineer to the whole team. What one engineer learns about working with AI reaches everyone, so the same mistakes repeat less.
The engineering side shows how each one works and how we measure it.
What the business needs
- 1 · IntentStrategy to the people buildingThe plan changes on the way down.
- 2 · OwnershipDecision to ownerWork waits while nobody is sure who can say yes.
- 3 · ReviewAI output to trusted codeCode gets written faster than anyone can review and trust it.
- 4 · LearningOne engineer to the whole teamThe gains stay with one person.
Results your board sees
Working together
The three steps
In the first few conversations we’re mostly listening, to you, to your leaders, to the engineers, to sales and to a couple of customers if we can get them. Our founder, Jeremy Brooks, once listened to another founder for about twenty-five minutes before everything she was dealing with came down to one sentence: “We just keep missing dates or building the wrong thing.” That’s where the work started, with the question Jeremy has borrowed from Gary Keller for years: which one thing, done well, makes everything else easier or unnecessary?
When you take the readout to your board, your CTO presents its engineering side.
- Find what pays You know where the gains from AI are leaking and where you are starting from. Work starts on the handoff costing you the most, then on the others, and the first signals show up in your own numbers.You come away with measures your CTO has agreed, each with a baseline from your own systems.
- Build it in The numbers show how far things have moved at each handoff, and when the first change is live, you take your board a readout against where you started.You come away with that readout, built with your CTO, and the practices your team now runs at each handoff we worked through.
- Keep it runningIf you choose After the readout, you decide whether we keep going.Everything we created stays in your systems, and your team already runs it.
A normal week
Jeremy meets with you and your CTO regularly on the problems and where the company needs to go, and you stay out of the engineering detail.
The rest of his time goes to your leaders, managers and engineers, turning what we learn into action and bringing it back to you and your CTO, with our senior builders joining your team when the work needs them.
Your team stays in charge
We work with every layer between you and your engineers rather than going around anyone. Your CTO or VP of Engineering stays in charge. Our team is Jeremy, senior builders like Patrick Hrabos who sit with your engineers in the detail, and the AI agents we work alongside. What your engineers tell us goes to your CTO first, and nothing about any one person goes up the chain.
- We start from what already works, why it was built that way, and the chores your engineers most want to give to agents.
- Nothing changes how your engineers work until your CTO says yes.
- Everything we create, from code to prompts and agent settings, lives in your systems and belongs to you, and our agreement says so.
How we measure it
Your board will ask three things, and the measures build on DORA’s delivery research and on DX’s frameworks for developer productivity.
- Are we building what the business needs? Progress on your top two or three goals against their baselines, how much of what engineering commits to gets delivered, and how much engineering time goes to each goal and to new capabilities.
- Is delivery faster without getting riskier? Time from idea to customer, how long work waits on review, how often a change fails in production, and how many deployments are unplanned fixes.
- Is the AI spend paying back? AI spend and use by team, set against those results, with any self-reported time savings checked against what actually shipped.
Everything is reported by team and never by person, with no leaderboards. Numeric targets go on your business goals and never on the delivery measures, because a measure that becomes a target stops telling you the truth, as Goodhart’s law warns. Early numbers can dip while a team changes how it works, which DORA’s 2026 report on AI returns expects, so the first signals are an early read and the readout is the one to judge by. Jeremy wrote more about what to bring when your board asks if AI is paying off.
The readout
What you take to your board
- Answers to the three questions above, in the same order, each set against the baseline from your own systems.
- What changed in each handoff we worked through, and what your team now owns.