How it works
Understand first. Build second.
This is a serious piece of work, and the order matters more than anything else about it. Each phase exists so that the next one is decided on evidence rather than assumption — and so that you can see what you're getting before committing to the part that builds it.
01
Diagnose
Understanding
02
Blueprint
Design
03
Build
Implementation
04
Evolve
Continuous
At a glance
Four phases, in order.
Phase 01 · Understanding
Diagnose
We sit with the people doing the work: operations, delivery, finance, leadership. We map the real workflows, the tools in use, the spreadsheets holding everything together, and the questions nobody can answer quickly. You get an honest picture of where time and clarity are being lost, whether or not you build anything with us.
What you get
- Workflow and systems map
- Where time and clarity are being lost
- Prioritised opportunities
01
Diagnose
What actually happens here?
We spend time with the people who run the work day to day — not only the leadership team. Operations managers know where the process breaks. Delivery leads know which spreadsheet is load-bearing. Finance knows which numbers are reconstructed at month end.
We map the real path a piece of work takes through the company: who touches it, what gets re-entered, where it waits, and which decisions are delayed because the information isn't at hand. Where the cost of a gap can be worked out honestly, we work it out.
The output is useful on its own. If the diagnosis leads you to fix three things yourself and stop there, that is a legitimate outcome — and we will tell you when we think it is the right one.
- Interviews
- Conversations across every function, not only leadership
- Systems audit
- Every tool, subscription, spreadsheet and manual step
- Friction model
- Where hours and clarity are being lost
- Opportunity map
- What to fix first, and what not to build
02
Blueprint
What should the system be?
We decide the shape of it before we build anything: what connects, what changes, what gets built, the data model, the roles and permissions, and the screens each team will live in. Then we make it clickable, so your leadership can walk through it and argue with it while changes are still free.
We also decide what stays outside. If your accounting system works, we integrate rather than replace. Restraint at this stage is what keeps a platform maintainable in year four.
Blueprint ends with an agreed sequence and a clear view of what each part of the work involves — including what it will cost, which is a question we can finally answer honestly by this point. You are free to take the blueprint elsewhere; it's yours.
- Architecture
- Modules, data model, permissions, integrations
- Prototype
- Clickable, reviewable, argued over before code
- Scope
- What gets built, and just as importantly what doesn't
- Sequence
- What happens first, and why
03
Build
When does it become real?
Early. We build in working slices, starting with whatever is costing the most time now — often reporting or capacity. Your team uses real functionality long before the end, and each release retires a specific spreadsheet or subscription.
We migrate historical data properly, because a platform that starts empty gets abandoned. We connect the systems worth keeping. We train the people who will use it every day, in their own workflows rather than a generic session.
Adoption is treated as part of the build, not a phase after it. If people go back to the spreadsheet, the project failed regardless of the code.
- Short cycles
- Something usable at the end of each one
- Data migration
- Your history moves in with you
- Integrations
- Accounting, calendars, e-signature, industry tools
- Rollout
- Training, documentation, and hands-on support
04
Evolve
What happens after launch?
A platform that stops changing starts decaying. Companies add service lines, enter new markets, restructure teams and face new reporting obligations. The platform has to keep pace or it becomes the next legacy system.
We stay close to the system so it keeps pace: a roadmap you agree, ongoing support, new capability as needs emerge, and automation or intelligence introduced once there's real evidence it will help.
What we build for your business is yours. The systems and code we create specifically for you are built for you, not rented back to you.
- Roadmap
- Agreed with your leadership team
- Support
- The people who built it stay close to how it evolves
- New capability
- Built as the business changes
- Measurement
- Whether it actually removed the work it was meant to
Commercials
Plainly stated.
We can't price what we haven't understood yet. Diagnose comes first because it is the point at which the shape of the work stops being guesswork — and cost follows shape.
What the work costs depends on what we find: how much needs connecting, how much needs changing, and how much has to be built. We'd rather tell you that plainly than quote a number that pretends we already know your business.
Common questions
Who owns what you build?
You do. What we create specifically for your business is built for you, not rented back to you.
What if we stop after Blueprint?
That's a legitimate outcome. You keep the architecture and the prototype.
Do you replace everything?
No. We keep and integrate systems that work; replacing them would be waste.
How involved does our team need to be?
Meaningfully, during Diagnose. Lightly after that — a weekly review.