ReplacesCausalJiravspreadsheet models
Scenario Planner
vs the disconnected FP&A model
What-if planning over your live operation, not a spreadsheet copy of it. Move the levers — headcount, contract mix, rates, utilisation — and see revenue, cost and margin respond off the same numbers that run the business, so the plan and the operation never drift apart.
Why it wins
- Models over your live operational and financial data — not a separate copy
- Levers map to real drivers: headcount, contract mix, rates, utilisation
- Revenue, cost and margin respond on the same numbers that run the business
- One tenant-isolated record — the plan cannot drift from the operation
How it compares
Measured on publicly available data against the named market leader(s) it replaces. Every row links its source.
| IMAISA | The market leader | |
|---|---|---|
| Data source | Plans model your live operational and financial data | An FP&A model fed by exports, maintained separatelysource for the Data source comparison |
| Drift | One record — the plan and the operation cannot diverge | A separate planning tool reconciled to actuals periodicallysource for the Drift comparison |
| Domain fit | Levers are FM drivers: contract mix, engineer utilisation, rates | General financial modelling; FM drivers are yours to buildsource for the Domain fit comparison |
Live datanot a spreadsheet copy
Leversheadcount/mix/rate/util
to £revenue/cost/margin
Onerecord with the operation
Engineered across 1 architecture decision records (scenario_planner) — a deliberately-built module, not a checkbox.