← All work

Case study · Strategic Finance + Governance

From two days to two minutes: rebuilding a corporate plan as an operating system

A master developer's plan took two days to re-run, so the leadership team debated last month's numbers. The rebuild let them test the question in the room.

2 minplan re-run time, down from 2 days
OrganisationPublic Investment Fund-backed master developer, Saudi Arabia
AudienceManagement Committee and Board
ScopeCorporate financial plan for a multi-phase, mixed-use master development

01 · The situation

A plan too slow to steer by

The corporate financial plan was a static, consultant-built model. Each re-run took two days, so by the time a scenario came back the question had usually moved on. Assumptions changed without a clear owner, and leadership discussions centred on the last version rather than the next decision.

02 · What I did

Rebuilt the plan as a governed system, not a bigger spreadsheet

  • Rebuilt the corporate model top-down, modular and auditable, cutting run-time complexity.
  • Added an assumptions register: every critical input tiered, owned and logged, with material changes escalated.
  • Linked it to a risk register and a scenario engine, so timing, pricing, cost and funding could be stress-tested on demand.
  • Put a monthly business review on top, so the model drives the monthly executive conversation instead of reporting the past.

03 · The decision it enabled

Bringing Phase 2 forward, tested in the room

With re-runs in two minutes, the Management Committee could see the effect of a change before it decided, not two days after.

Development phasing

The Committee was able to assess the financial implications of bringing forward Phase 2 versus retaining the original development programme, including the impact on peak equity requirements, cash flow and overall project returns.

04 · The outcome

2 minRe-run timeFrom 2 days
25×Scenario capacityMore scenarios per cycle
Real-timeDecision supportScenarios tested in the meeting

What other Boards can take from this

Speed without governance just produces wrong answers faster. The gain came from pairing a faster model with owned assumptions and a monthly rhythm, so the leadership team could trust the number it was looking at.