Our approach
From the first question to a system that runs.
One engagement model, four stages, whichever practice leads. Each stage ends with something you keep.
One model, four stages
Every engagement moves through the same four stages, whichever practice leads it. Each one ends with something you keep.
- 2-6 weeks
Assess
We measure how the work runs today, from its own data, and put a value on each possible change.
What you get
A baseline measured from your own data
Opportunities ranked by value, cost and risk
What is not worth doing, and why
Decision at the end: Which opportunity goes forward, if any.
- 3 weeks
Design
A target process, an architecture and a ranked backlog, detailed enough to price and build from.
What you get
Target process and architecture
A business case with the baseline attached
Fixed scope and exit criteria for the build
Decision at the end: Go or no-go on a fixed-price build.
- In releases
Deliver
Short releases into production, tested on your own data and its real edge cases.
What you get
Working releases, tested on real cases
A parallel run against your own history
Monitoring, alerting and an audit trail
Decision at the end: Switch on, once the evidence supports it.
- Rolling
Operate
We run, monitor and improve what we built, or hand it to your team.
What you get
Runbooks and a named owner on your side
A monthly performance review
A prioritised improvement backlog
Decision at the end: Run it with us, or run it yourselves.
Principles we work by
Evidence over opinion
If the data disagrees with the room, the data wins.
Simplest technology first
An API beats a bot, a bot beats manual work, and an agent is for what is left.
Fixed scope to start
Every engagement opens with something priced, bounded and yours to keep.
Designed for the bad day
Exceptions, monitoring and rollback are designed first, not added later.
Governance that keeps it honest
A small, fixed rhythm, so everyone knows when decisions are made and who makes them.
Weekly
Working session
Your process owner and our delivery lead review progress and blockers.
Every two weeks
Demo
Working software on real data, never slides.
Monthly
Steering
Your sponsor and our engagement partner review value, risk and spend.
End of each stage
Stage gate
A written decision to continue, change course or stop.
Who sits at the table
- Your sponsor
- Owns the outcome and the budget.
- Engagement partner
- Accountable for what we deliver.
- Delivery lead
- Runs the team and the plan, day to day.
- Process owner
- Your expert, and the future owner of the system.
Common questions
No. Each stage ends with a written decision. You can stop after any of them and keep what was delivered.
The one closest to the outcome you need. The model is the same whichever practice leads, and specialists join when the work calls for them.
Assess and Design are fixed scope and fixed fee, agreed before we start. Delivery and Operate are priced against the roadmap you approve at the end of Design.
You do. Code, documentation, process maps and the backlog are yours, whether or not we continue.
Next step
Tell us what has to change.
A 30-minute call with a partner. You leave with a view, whether or not we work together.
Or write to us directly: •••••@•••••••.•••
- A reply from a partner within one business day
- Fixed scope and fixed fee, agreed before we start
- The maps and the backlog are yours either way