01 — The foundation
Current state first. Without exception.
Before any strategy is defined or investment committed, organisations need an accurate picture of what they have. Not what the documentation says they have. What actually exists today — the applications, integrations, data flows, and the informal dependencies that never made it into any formal register.
Every engagement where assumptions replaced analysis has cost more, taken longer, and delivered less than planned. The current state is not a starting point to be rushed through. It is the work.
02 — THE APPROACH
Four steps. One consistent sequence.
The sequence is the same regardless of the engagement type — M&A, transformation, or standalone current-state analysis. What changes is the scope and depth of each step.
Step 01 Discover
Map what exists. Applications, data flows, integrations — documented and informal. We do not assume. We verify.
Step 02 Analyse
Build the capability model. Surface the complexity, dependencies, and structural fragility.
Step 03 Identify risks
Name the undocumented dependencies. Produce the evidence base for decisions that previously relied on intuition.
Step 04 Target state
Define where the organisation should go — realistically, sequenced, and grounded in what actually exists.
How we work
How we think about the problem.
Most engagements fail not because the target state was wrong — but because the current state was misunderstood. We invest in understanding what actually exists before we recommend what should come next.
“The organisations that invest time in understanding what they have consistently outperform those that skip straight to where they want to go.”
Organisation Insights
04 — Why it matters
The cost of skipping the current state.
Transformation programmes
The most common cause of cost overrun and timeline failure in transformation is not technology — it is undiscovered complexity in the current state. Systems that were assumed to be replaceable turn out to be operationally critical. Integrations that were assumed to be simple turn out to be structural.
M&A integration
Post-merger integration consistently underestimates the IT and data complexity of what has been acquired. The gap between what due diligence captures and what actually exists determines how much the integration costs and how long it takes.
Platform investment
Organisations investing in new ERP, CRM, or HRM platforms consistently underestimate the data migration and integration complexity — because they have not mapped what they are migrating from. The current state is discovered mid-project, when changing course is expensive.