Where Strategy
Meets Execution

A large asset-based government organisation in EMEA engaged our firm to lead a digital transformation of FP&A processes and Enterprise Master Data & Data Management — a SaaS deployment covering 11 distinct processes with $20M in engagement value. We stepped in to turn around a failing programme. On day two, the client had issued a soft legal notice; two CRPs had failed and a third was cancelled. The implementation team carried support backgrounds, not functional design expertise. No Income Statement or Balance Sheet structure existed, the ERP and Chart of Accounts were being restructured concurrently, and true completion stood at approximately 30% against a management assumption of 80%.

Three options were evaluated: a full transparent reset (risking legal escalation), maintaining the status quo (ethically and technically indefensible), or an engagement freeze. We chose to freeze all implementation work for two weeks, creating space for SME-led validation sessions with the client's CFO team and PMO across PBCS, FCCS, DRM, and Strategic Planning. For the first time, the client saw their own financial reporting complexity accurately reflected in the architecture. We traded the appearance of momentum for a partial timeline reset, restructured governance, and rebuilt the team around functional design expertise.

A global hi-tech firm with $8B in annual revenue engaged our team to lead a large EPM transformation covering Consolidations, FP&A, and Integrations. The programme was considered nearly complete. The SOW listed 2 integrations; a proper solution design revealed the true number was 120+. The root cause was a current-state assessment conducted by an ERP team with no EPM depth — presentable slides that failed to reflect how external reporting and multi-GAAP consolidation actually functioned. Hidden complexity included Joint Ventures, multi-GAAP reporting, multiple cash-flow treatments, multiple reporting currencies, and 20+ complex holding-subsidiary-equity calculations. Scope was off by approximately 1,500%.

A full public reset was not viable — it would have ended the engagement. We continued building what could safely be built (applications, dimensions, hierarchies, core structures) while running deep requirements and design sessions in parallel to quietly surface true scope. Once the full picture was mapped end-to-end, we aligned internally — including senior partners — on a strategy to surface the scope gap without alarming the client. By the time the plan was reset, meaningful build progress was visible, trust was established, and critical timeline impacts were framed as design decisions owned by the client.

The CFO of a ~$10B revenue conglomerate asked: 'Can you deliver this EPM programme in 7 months?' The organisation held approximately 1,800 legal entities, operations across 40+ countries, and multiple verticals spanning retail, hotels, real estate, and entertainment — all underpinned by deep legacy systems and complex holding structures. A realistic roadmap required 14–18 months with strong governance in place. What followed is a case study in how large transformations fail — not from technical complexity, but from governance collapse across four compounding failure modes.

Partner selection ignored RFP evidence: the only viable option was a dedicated internal team, but a partner was chosen who staffed supposed experts part-time, losing eight months before the error was acknowledged. Finance leadership failed to enforce cross-vertical accountability, leaving critical decisions unanswered for months. Business resistance in the recently acquired retail vertical — the second largest globally — went unmanaged for nearly 20 months, driven not by politics but by fear of role loss. Our team was given accountability without authority: escalation paths were shut down, converting every structural failure into an execution problem with no resolution mechanism.

Across $20M+ programmes in the US, EMEA, and Gulf region, a consistent pattern emerges: EPM success is rarely a technology problem — it is a reality problem. Whether in Consolidations, FP&A, or Master Data Management, the programmes that go live are not the fastest; they are the ones with the architectural honesty to face uncomfortable truths early. Three pillars separate programmes that reach production from those that don't: disciplined investigation over documentation, the strategic courage to pause, and deep domain expertise rather than raw headcount.

An SOW might list 2 integrations while reality holds 120+. A cycle described as sequential is actually parallel. Requirements gathering is not a sign-off exercise — it is a disciplined interrogation of what stakeholders forgot to say, assumed didn't matter, and cannot yet articulate. The hardest decision in transformation leadership is knowing when to slow a programme down so it can actually go live; pausing is a strategic trade of visible momentum for technical certainty. And expertise is not a staffing metric — it is what converts early signals into decisions before they become crises.