A transformation plan the engineers will actually build.
Strategy written by people who ship: the operating model, the systems and the sequence — with every initiative tied to a number the business already tracks and a team ready to deliver it.
- Discovery
- Options and sequence
- The plan
- Delivery and review
You do not have to use us to build it.
Most transformation strategies are written by people who will not be there when the work gets hard. They describe a target state, list dozens of initiatives, and leave the organisation to discover that many of them depend on a core system nobody dares touch. Years later the deck is still accurate and nothing has changed.
We write strategy the way we would want to receive it as the team that has to deliver: a short list of initiatives in dependency order, each tied to a measure the business already reports, each with a first release small enough to prove the direction early. Because we build and operate platforms ourselves, the plan carries the engineering judgement a strategy consultancy cannot: what is cheap, what is slow, what will break.
The plan is written so any competent team can execute it — but we will have skin in it, because we expect to be asked.
Four things a transformation plan has to settle.
Each is written down, argued with your leadership, and revised until the people who will own the result agree with it.
Where the money leaks
A current-state map of the processes, systems and hand-offs that cost the most — measured with your own data, not benchmarks. The plan targets the leaks, not the technology fashions.
The operating model
Who decides what, how work flows between business and technology, what gets built versus bought versus configured. The engagement model for each initiative is part of the plan.
The system landscape
Which systems stay, which go, which get wrapped. A target architecture with the integration layer, data flows and the order in which the estate changes so nothing is cut over before its replacement is proven.
The sequence and the measures
Initiatives in dependency order, each with a first release, a measure, a budget band and an owner. The first phase is planned in detail; the rest is planned to the level the evidence allows.
How the work runs, day to day.
Sequence by dependency and by proof, not by ambition.
The order of initiatives is decided by two questions: what has to exist before this can work, and what will prove the direction fastest. The result is a plan whose first phase produces evidence — a working slice, a measured number — rather than a platform nobody can see yet.
- Every initiative names the measure it moves and the baseline it starts from
- Dependencies on core systems, data and people are explicit, with the risk written next to them
- A first release per initiative that a real user can touch early
How the work runs.
Discovery
Interviews with leadership and operators, a review of the systems and the data, and the cost map built from your own numbers.
Options and sequence
Target operating model and landscape, initiatives scored and sequenced, budget bands and risks. Argued with your leadership in working sessions.
The plan
The written roadmap: first phase in detail, the rest to the level of evidence, a governance cadence and the measures that will be reported.
Delivery and review
Build with us or with your own teams. Either way, a regular review against the measures, at a rhythm agreed with you — and the plan changes when the evidence does.
What you keep.
- A current-state cost map built from your own data
- Target operating model and system landscape
- A sequenced roadmap with measures, owners and budget bands
- A detailed first-phase plan with a first release per initiative
- A governance cadence and a review template
When this is the right call.
Choose this when leadership has decided the organisation must change how it works, several initiatives compete for the same budget and people, and nobody has yet written the order in which they should happen.
Look elsewhere if what you need is a single system built or replaced — go straight to modernisation or custom software and skip the strategy phase.
Frequently asked questions
Services that pair with this.
Have a transformation that keeps stalling?
Bring the current plan, or the lack of one. An AI-native engineer reads it and replies in writing with a view of what should go first and why.