Two states. You've already lived through a failed finance transformation, or you're about to start one.
The numbers say it's roughly 50/50. 70% don't deliver. The ones that do, sequence by risk, not ambition.
Sequence by blast radius, not by ambition.
P2P first because the radius of getting it wrong is small. R2R next because the team can absorb it. O2C last because that's where the customer sees a wobble.
Sequence by blast radius.
Most finance transformations sequence by ambition, what the executive team wants live first, what the board has been promised, what the platform demo showed off. That's how the 70% fail.
The ones that succeed sequence by where the damage lands if a process breaks.
Internal-facing
Errors hit suppliers and back-office, not customers. The platform is well-suited to this work, the early wins build credibility, and the team learns the system on processes that won't damage the business if they stumble.
Regulator-facing
Close, consolidation, statutory reporting. Errors are visible to auditors and the board but contained within finance. The foundations these set must be right before anything customer-facing scales on top.
Customer-facing
Revenue, cash collection, brand. The smallest revenue entities go first inside this wave, the team gets to fail safely before touching the entities that matter most to the P&L.
You're not the first.
of finance transformations fail to deliver forecast outcomes.
days is the average mid-market month-end close. Best-in-class is four.
the average split of programme spend on technology versus change. The single clearest predictor of failure.
If two of these describe your last finance transformation, sequencing is why. If two describe the one you're about to start, sequencing is the lever that changes the outcome.
Diagnose. Deliver. Hold the discipline.
Three engagements, designed to be bought separately or sequenced together.
Sequencing Diagnostic
A short, fixed-scope engagement that maps the state of the finance estate, the readiness of the organisation, and the right order and pace for the work ahead. Output: a costed, phased roadmap with the absorption gates marked.
Phased Transformation
The transformation itself, run in waves. Internal-facing first, regulator-facing next, customer-facing last. Each wave self-contained, each wave delivering standalone value, each wave de-risking the one after it.
Absorption Measurement
The work most programmes skip. We measure whether the organisation can absorb the next wave before the platform serves it up. Built on Process Intelligence, the same telemetry layer we use in field service, applied to the finance estate.
How the sequence holds in delivery.
The risk-sequencing principle is intellectual. A programme is not. What turns the principle into delivery is three things: phase boundaries that hold, absorption gates that bite, and a discipline of releasing nothing the organisation can't yet absorb.
Phase boundaries that hold
Each wave is contained. Internal-facing processes go live, the team absorbs them, the early benefits land, invoice cycle compression, supplier self-service, transaction automation. The next wave is not designed in detail until the first is stable. This is unusual. Most programmes design all waves up front and then defend the design against operational reality. We don't.
Absorption gates that bite
Between every wave there is a gate. Three questions: is the previous wave actually working, is the team operating it without consulting support, and is the data clean enough to base the next wave on. If any answer is no, the next wave slips. The gate is not advisory. It is binding.
The discipline of not releasing
The hardest part of a sequenced transformation is holding back. Stakeholders ask for the next module. The platform supports it. The build team is ready. We measure what the organisation can absorb and we hold the line where the answer is 'not yet'. Saturation is the most common cause of stall, and the cure is structural.
Where the value actually sits.
Sequencing tells you the order of work. It doesn't tell you where the return comes from.
A successful finance transformation delivers value across four interdependent dimensions. Each one multiplies the others. Underspend on any one and the others quietly weaken.
The transactional roles consolidate, the retained roles shift from running the platform to acting on what it tells them. This is where the largest return sits, and where most programmes underspend most heavily.
Manual work automates. Cycles compress. Close goes from weeks to days, procurement from approval queues to flow. This is the value most platform demos focus on, and it is real, but it is less than half of the total.
A single template replaces the patchwork of local operating models accumulated through the years. End-to-end ownership of process replaces functional silos. Decisions move faster because the structure is designed to let them.
One trusted view of the group's numbers replaces the local spreadsheets each business unit secretly relies on. The platform becomes the foundation every AI use case in the next decade will sit on.
Underspend on any one tower and the others weaken. The single clearest predictor of programme failure is the average split of programme spend: 92% on technology, 8% on the change required to make the technology land. That ratio is the failure pattern in one number.
Composite analysis: BCG, McKinsey, Hackett Group, Prosci, Forrester. Percentages are directional, drawn from multi-year transformation research across ERP, CRM and HCM programmes.
29 entities. 21 countries. One template.
A European communications-platform business with operations across 20+ countries, mid-replatform from a fragmented multi-ledger estate to a single Dynamics 365 Finance template.
We arrived to a programme that had been scoped ambitiously, every entity in scope from day one, every workstream parallel, a go-live timeline that hadn't survived contact with the operating model.
We re-sequenced. Internal-facing processes first across a controlled set of entities. Regulator-facing next, with the close cycle stabilised before anything customer-facing went live. Smallest revenue entities ahead of the largest inside the final wave.
Functional MVP at twelve months. Full rollout across all 29 entities at twenty-four.
The programme is in flight. The trajectory is clean. We will publish outcomes when they're defensible.
We build on Microsoft.
Two platforms, one strategic boundary.
For groups operating across multiple entities, multiple countries, and multiple ledgers. Built for scale, regulator-facing complexity, and the governance demands of mid-market and upper-mid-market groups. The platform behind the case above.
For single-entity and low-multi-entity businesses where the operating model is contained and the finance team is small but ambitious. Faster to deploy, lighter to run, with a clear upgrade path to F&O when the business outgrows it.
One discipline, four service lines.
Finance Transformation is one of four service lines. The same risk-sequencing discipline shapes all of them, different processes, different risks, the same principle.
The shadow sales team. How the front line of the business gets transformed without breaking it.
The front of the funnel just moved. Most sales operations aren't designed for what comes next.
Work management, redesigned. For the businesses whose output is the business.