Owners don't need another report. They need an answer.
An owner calls the CFO on a Tuesday at 9:14 a.m.: «How much did we make in April and where is the cash?» That's not a request for a report. That's a request for an answer.
A report vs an answer
A report is static, historical, comprehensive. Built around a date. Has a cover slide, a ProForma table, footnotes. Born out of a close routine. Not built for a question nobody anticipated.
An answer is live, contextual, decision-ready. Exists because the number already exists. Not «when can we prepare» but «I'm looking at it right now». Not a PDF — a single number with drill-down.
Why reports don't answer
- Latency. T+14 monthly close → an answer 2 weeks stale. May decisions on April data is the norm.
- Structure. GL accounting logic isn't built for decision-making. «Where's the cash» isn't a debit/credit question.
- Format. An 18-page PDF is not an answer. It's a place where the answer lives — if you know where to look.
What's actually needed
A 10-second answer. Power-of-one-screen. Six metrics that tell the owner where we are at a glance.
| Cash position (live) | $ today / $ 30d / $ 90d |
|---|---|
| Revenue MTD vs plan | % deviation |
| Margin trend | 12-week sparkline |
| Top 3 deviations | category + Δ |
| AR ageing alert | > 30d overdue $ |
| Forward visibility | 13w cash floor |
Six weeks of work on a typical mandate. Not magic — engineering: single source of truth, pre-computed metrics, mobile-first interface, automated anomaly detection.