Project
A defined scope, a fixed price where the scope genuinely is defined, and a plan with dates. Ends in a handover.
Best for: A formation, an implementation, a specific build.
The same four steps whether the engagement is a licence application or an ERP rollout. The sequence is what keeps the second half honest.
We map the process with the people who run it, before anything is designed. This step regularly changes the brief.
Before any designScope, structure and a plan with dates and costs you can take to a board.
Board-readyIn increments you can see. Working software every two weeks; on advisory work, a decision closed at every step.
Every two weeksDocumentation, training and full ownership. Support afterwards if you want it, not because you are stuck.
Full ownershipPick the shape that fits the work. We will tell you which one an engagement should be.
A defined scope, a fixed price where the scope genuinely is defined, and a plan with dates. Ends in a handover.
Best for: A formation, an implementation, a specific build.
An agreed capacity each month across whichever of the two practices you need it in. Priorities are reset monthly, not annually.
Best for: Ongoing advisory, compliance and system evolution.
Our people working inside your team, reporting into your structure, on your tooling. Reviewed quarterly.
Best for: Filling a capability gap without hiring for it yet.
Fixed price for well-defined scopes, and time-and-materials for discovery or open-ended work. We will not quote a fixed price for something nobody understands yet — that pricing model only works by padding the number or cutting quality later.
The firm that designs the operating model is the firm that has to make it work in the system.
A meaningful share of our analyses end in a recommendation not to build. That is a better outcome than finding out after the second sprint.
Code, infrastructure, documentation, and the reasoning behind each decision.
Not a translation applied at the end. Interfaces, documents, reporting and training in both languages from the start.
A short call to understand the problem, then an honest view on scope, cost and whether it is worth doing.
Start a ConversationTell us the problem, not the specification.