A method built to survive contact with a real operation.
Our process exists to prevent the three ways technology programmes fail: solving the wrong problem, building something nobody adopts, and losing the plot after go-live. Each stage has a defined output, so you always know what you are buying next.
We sell a decision before we sell a build.
Every engagement starts by establishing what is actually worth changing and what it is worth. That plan belongs to you. If it says the answer is smaller than you expected — or that a different partner suits it better — the plan will say that, and you will still have something valuable.
It is a slower way to sell. It is a far more reliable way to deliver.
Stage 01In the room with the operators
Stage 02 – 03Prototype, then build
Stage 04 – 05Live, measured, improvedStrategy → experience design → technology → implementation → optimisation.
Each stage produces something you can hold, review and act on independently.
Strategy & Discovery
Interviews, process walk-throughs, systems and data review, and commercial analysis. Output: a prioritised roadmap with business cases, target architecture, sequencing and indicative investment.
Experience Design
Customer journeys and staff workflows designed and tested as interactive prototypes with the people who will use them. Output: validated design system and a scope locked to the business case.
Technology & Engineering
Architecture, data model, integrations and secure build in short cycles with automated tests and review. Output: working software you can see and use throughout, not at the end.
Implementation & Change
Data migration, role-based training, phased or parallel-run cutover, hypercare. Output: a system genuinely in use by the people it was built for.
Optimisation & Evolution
Instrumented measures, review cadence and a backlog prioritised on measured impact. Output: benefit tracked against the original case, and a system that keeps improving.
Three ways to work with us.
All three start with discovery. Which model follows depends on how defined the work is and how much capability you want to keep in-house.
One owner, one measure, one plan everybody can see.
The governance below is not paperwork. It is the difference between a programme that lands and one that is quietly written off two budget cycles later — and it is why we occasionally decline engagements.
What keeps a programme honest.
These are the conditions we hold ourselves and our clients to. They are also the reasons we occasionally decline engagements.
One accountable owner
A single named person on your side with authority to decide. Committees can advise; they cannot own a programme.
A measure agreed before build
What number should move, from what baseline, by when. Without it, “success” becomes a matter of opinion after the fact.
Access to the people doing the work
Not only to management. The design has to survive contact with the person who actually processes the order.
Working software throughout
You see and use real software from early in the engagement, so risk surfaces while it is still cheap to address.
Documented decisions
Architecture, data and access decisions are written down with their reasoning, so future teams inherit the thinking, not just the code.
We qualify, and we expect you to.
Before a proposal exists, we establish three things: the business objective, the timeline, and the project size. It saves everyone weeks.
What must be different?
Expressed commercially — revenue, cost, capacity, risk, service — rather than as a feature list. If the objective is unclear, discovery is the right first purchase.
By when, and why then?
A date driven by a real business event — a season, a funding round, a contract, an opening — makes sequencing decisions straightforward.
What is the investment envelope?
Not a fixed budget, an order of magnitude. It determines whether the honest answer is a strategic build, a focused intervention, or a recommendation to spend nothing yet.
What buyers ask us first.
Why do you insist on paid discovery?
Because a free proposal is guesswork dressed as certainty, and it is paid for anyway — inside the build price, as contingency. A paid discovery produces a plan you own outright, with real numbers, and it is deliberately useful even if you never build with us.
What does a typical engagement cost?
Engagements are scoped after discovery. We give indicative ranges early, based on project size, timeline and objective, so nobody spends weeks on a conversation that was never going to fit. Fixed price for defined scope, or time-and-materials for evolving programmes — agreed before we start.
Who actually does the work?
A small senior team. The people who scope your engagement are the people who deliver it. We do not sell with principals and staff with juniors.
How do you handle change during a project?
Iteratively and openly. Scope changes are assessed for impact on cost, timeline and the business case, and decided by you. Working software throughout the engagement means change is discovered early, when it is still cheap.
What do you need from us?
An accountable owner with authority to decide, access to the people who do the work, honesty about what is broken, and a defined success measure. Engagements that lack the first of those fail regardless of the technology.
What happens after go-live?
Hypercare through the first operating cycles, then either handover to your team with documentation and training, or a managed support and evolution arrangement. Both are priced before go-live, not improvised after it.
Bring the objective. We will bring the plan.
A first conversation takes about thirty minutes and covers the objective, the constraints and whether we are the right partner. No proposal is written before that is clear.
Projects scoped after discovery. We qualify on objective, timeline and project size before any proposal.