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. With a T+14 monthly close, the answer is 2 weeks stale. May decisions on April data is the norm. For comparison, according to APQC data (over 11,000 companies), the median company prepares consolidated monthly statements in 6 calendar days.
- 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 |
This is not «a report cut down to one page». It is a fundamentally different unit of information, built to answer, not to record.
A report is an archive. An answer is an interface.
How we build it
Single source of truth (a consolidated ledger by entity), pre-computed metrics (a nightly job, not real-time calculation), mobile-first interface (the dashboard opens on a phone in 3 seconds), automated anomaly detection (not «what happened» but «where the deviation is»). Not magic. Engineering. Six weeks of work on a typical mandate.
Why an in-house finance team doesn’t build this
Because a finance team is not an engineering department. They have no mandate for infrastructure. They serve the report cycle; they don’t design an interface for the owner. These are two different disciplines, and one needs outside hands that have seen how this looks in other companies.