Simulator · CFO office · 36 months

The CFO's levers: what a day is worth, and what the tools actually unlock

DSO, DPO, WIP, inventory, close time — then EPM vs. ERP↔SaaS integration vs. a finance transformation. Move the dials, spend the change capacity, and see which number moved and which one was load-bearing.

The belief this is built to replace

From a list of KPI projects to one cash-conversion cycle

❌ The KPI-by-KPI business case

"DSO is a project. DPO is a project. Close time is a project. Pick the platform with the best ROI deck, add up the line items, and the benefits stack." Every metric has an owner, a target and a vendor.

✅ One system, three capabilities, one scarce resource

The levers share the same cash cycle, and the tools don't move metrics — they raise the ceiling on policies you already control. How much of each lever you can actually pull depends on your data and process foundation, and on a finance team with a finite capacity to absorb change.

What one day is worth

A day of working capital is a one-time stock of cash, not a recurring gain — its recurring value is only the carry (9% cost of capital here). That's why a DSO number looks heroic in a deck and modest in the P&L.

The board

Pull the levers. Fund the tools. Watch what the finance team can absorb.

Company
Start from
 
DATA & PROCESS FOUNDATION — the slow dialPatchy · 40
One dial, four mechanisms. Foundation (clean master data, standard processes, one definition of each KPI) (1) sets how well any tool you buy is adopted, (2) sets how much of each policy lever you actually realise, (3) drives invoice disputes and so late-payment days, and (4) scales the change-capacity drain and cost overruns of every project (×1.3 at 0 → ×0.7 at 100). It moves over years, a finance transformation raises it slowly, and nothing on this page can buy it in a month.

Operating policies — what the CFO office does with today's systems

Investments — when each is funded (months from now); each raises a capability, not a metric

F
☆☆☆☆☆
0%
Net cash value over 36 months (% of revenue)
$0
One-time cash released
$0
Run-rate EBITDA change / yr
0
Cash conversion cycle (days)
Cumulative net cash against the do-nothing baseline (teal), and the one-time working-capital stock released (green dashed). The red floor is where programme cost has not yet been earned back; if the line stops in red, the programme stalled.
Change capacity — lowest point—
Drains with every project in build (more than linearly when they overlap) and every aggressive policy; refills slowly, faster as wins land. Below 40 adoption quality slips; at 0 the programme stalls — whatever the spreadsheet says.
Share of cash release that is borrowed from suppliers—
Stretching beyond contract terms is float, not value: it reverses when suppliers reprice or tighten. The score counts it at 50%.

The metric tree, live

The bad-quarter test

Month 12: the programme loses its sponsor's attention. Either discipline lapses for a few months and resumes, or the finance team reverts to the old habits for good.

Months where discipline lapses3 months
—
Plan as set
—
After the lapse
—
If the old habits return for good
Why it works

The loops underneath

Capability gates policy

Every collections, supplier and inventory lever is realised at 30% + 70% × capability. With today's systems you get roughly half of what the policy promises; integration, planning and process maturity raise the other half. Tools don't pull the lever — they let you pull it harder without breaking something.

Dispute loop

Billing errors → disputed invoices → late payment. Aggressive dunning on a dirty ledger chases the wrong customers, so level-3 collections costs sales and discounts before it gains days. Integration and foundation shrink the dispute rate and make the same policy cheaper.

Borrowed vs. owned cash

DSO, WIP and inventory days are yours once released. Days stretched from suppliers beyond contract are a loan: suppliers reprice (0.25–1.2% of purchases) and claw back up to half within two years.

Change capacity

Three projects at once cost more than three times one project, because the same people carry them. Wins refill capacity; stalls are the way programmes actually end. Sequencing mostly buys headroom, not extra value — the thing it protects is the run.

The deck's additive blind spot

EPM's cash value runs through data it doesn't create; transformation pays back mostly by raising the foundation under everything else; integration unlocks the policies you already have, so it's worth more than its own claim. Valuing each in isolation gets all three wrong in different directions.

Integral, not final frame

The score is cumulative net cash over 36 months after programme cost and carry, with borrowed float at 50%. A programme that releases cash in month 30 and costs a stall in month 31 is not a good programme.