How the work actually runs.
Not a philosophy. The sequence, the people, the cadence and the numbers we hold ourselves to — from the first assessment to the release that is still compounding a year later.
Six movements, in this order, every time.
The order matters more than the names. Diagnosis comes before framing, framing before design, and measurement never comes last.
Diagnose
An AI readiness and opportunity assessment, run against the work as it actually happens.
A ranked opportunity map with evidence behind each line.
Frame
Outcomes, KPIs and a fixed-scope first sprint agreed before anyone designs anything.
A named outcome, a date and a price.
Design
Research, service and interface design running alongside architecture, not ahead of it.
Tested flows and a validated technical approach.
Build
Senior engineering and AI architecture building the release that was scoped.
Working software, reviewed weekly.
Release
The first release ships in eight to ten weeks, instrumented against the KPIs.
Live product and a measurement baseline.
Compound
Post-launch measurement, iteration and the next release sequence.
Returns that keep accruing after launch.
Eight to ten weeks to first release.
Not because we move faster through the same relay, but because the lanes overlap. Engineering and AI architecture join at week one to set technical strategy and validate feasibility before design hardens.
Twelve commitments, three questions.
Who does the work
The people on the call are the people on the programme.
Founder involvement
Our founder oversees every engagement end to end — quality, detail and vision alignment stay accountable to one person.
A senior-only team profile
Every engagement is staffed with AI architects, product, design, quality and delivery leaders. No bench juniors learning on your programme.
Dedicated staffing
The team that starts the work finishes the work, led throughout by the same accountable leader.
How the work is scoped
Evidence sets the scope, and the scope has a date on it.
AI-first diagnosis
Every engagement opens with an AI readiness and opportunity assessment, so investment follows evidence rather than enthusiasm.
Fixed-scope start
We begin with a fixed-price transformation sprint and convert into an ongoing relationship once the value is proven.
Release plans
Work is broken into shippable releases with dates, not open-ended programmes with milestones nobody remembers.
Ideas bank
Ideas are captured throughout and tested for desirability, feasibility and viability before they earn a place in a release.
Clear KPIs
Outcomes are defined on day one. Every design, architecture and sequencing decision is measured against them.
How the work is measured
Outcomes are named on day one and reviewed until they land.
8—10 weeks to first release
Overlapping strategy, design, AI and engineering means the first release usually ships within eight to ten weeks.
Technology from day one
Engineering and AI architecture join at the start to set technical strategy and validate feasibility before design hardens.
Balanced scorecard
We review tangible outcomes and relationship health monthly, so nothing important drifts unnoticed.
Optimisation
Post-launch measurement and iteration continue to compound results long after the first release.
What you get, and how often.
Every week
- A release note: what shipped, what moved, what is blocked.
- A working session with the accountable leader — not a status email.
- The ideas bank reviewed, so nothing good gets lost in delivery.
Every month
- KPI review against the outcomes agreed on day one.
- A balanced scorecard covering delivery and relationship health.
- Re-sequencing of the release plan if the evidence has changed.
Start with a fixed-scope sprint.
Most engagements open with a fixed-price transformation sprint and convert into an ongoing relationship once the value is proven.