This conversation happens every month. In every company under 200 people. It's not the accountant's fault — it's a systems problem.
Every finance person I know has lived this conversation. The CEO needs a forward-looking number. The accounting system only produces backward-looking reports. And the person in the middle — the accountant — gets blamed for a gap that is entirely structural.
The scenario is specific enough that everyone recognizes it, but universal enough that it has become background noise in most small companies. The CEO wants to know something. The data isn't ready. The accountant explains why. The CEO is frustrated. Nothing changes. It happens again next month.
Here is the exchange as it actually happens — not dramatized, just accurate. I've had versions of this conversation from both sides of the desk.
The CEO isn't making an unreasonable request. Knowing next week's cash position before a board call is basic financial management. The accountant isn't making an excuse. You genuinely cannot build an accurate forward projection on unreconciled data. Both of them are operating correctly inside a broken system.
When a CEO asks "what's next week's cash flow," they are not asking for an accounting report. They are asking a planning question: do we have the financial capacity to make a specific decision right now? That question has a three-part answer — current position, expected inflows, scheduled outflows — and none of those three things require the month to be closed.
"The CEO needs a planning answer. The accounting system only produces compliance answers. Those are two different things, built on two different time orientations."
The monthly close is a compliance artifact. It exists because GAAP, tax authorities, and auditors need a clean, reconciled record of what happened. That record is valuable — but it is inherently backward-looking. It tells you what the position was. It cannot tell you what the position will be on Wednesday.
This is the part that CEOs often don't understand, and that accountants struggle to explain without sounding like they're making excuses. The gap between "open month" and "accurate projection" isn't bureaucratic caution. It's a data quality problem.
| What the CEO needs to know | Available without close? | Available with real-time system? |
|---|---|---|
| Current bank balance | Yes — via bank feed | Automatic, live |
| Outstanding supplier invoices due this week | Only if manually tracked | Auto-pulled from AP system |
| Expected client payments incoming | Not without open AR reconciliation | Tracked against invoice due dates |
| Payroll amount and date | Known in advance | Pre-loaded in projection model |
| Projected balance Friday EOD | Requires all of the above reconciled | Calculated automatically, updated daily |
| Risk flags (balance below threshold) | Nobody is watching in real time | Alert sent before the problem, not after |
The problem isn't that the data doesn't exist. It's that the data lives in three or four separate systems — the bank, the accounting software, the AP tracker, the payroll system — and nobody has connected them into a single forward-looking view. The accountant's job is currently to do that manually, every time someone asks. Which is why the answer is always "not until the close is done."
Most small company finance setups are built for compliance, not for decisions. The accounting system is designed to produce clean historical records. That's what it's optimized for. Asking it for a forward cash projection is like asking a camera to predict what will happen next — it can only record what already did.
The Friday 4pm call doesn't disappear when you build real-time cash visibility. The CEO still calls. What changes is the answer. Instead of "I can't give you that until next week," the answer is "it's already in the dashboard — here's the link."
The accountant doesn't spend their Friday afternoon manually pulling data and building a projection under pressure. That time goes somewhere more valuable — reviewing the numbers the system already produced, adding context, flagging anomalies that require human judgment. The compliance work still gets done. The planning work stops being blocked by it.
"When the CEO gets their answer in 30 seconds instead of 3 days, the finance function stops being a bottleneck. It becomes the fastest person in the room."
That shift — from bottleneck to fastest person in the room — is what I've been building toward for the last two years. Not with enterprise software. Not with a team of developers. With a handful of connected systems, a few AI agents, and a clearer understanding of which problems are people problems and which ones are architecture problems.
The Friday 4pm call is an architecture problem. And architecture problems have solutions.
Post #6 goes into the exact architecture I built — what systems connect to what, and how the CEO dashboard actually gets populated without anyone pressing a button.
Has this conversation ever happened in your company?
No spam. One post per week. Unsubscribe any time.