When to call finance: an implementer's guide
A brutally practical guide for EOS implementers: the exact moments in a session when the real problem is finance — and what to do about it without becoming the accountant.
- Certain patterns in the room often point to finance as the constraint, rather than strategy or accountability.
- Your job is to recognize the pattern, name it as a question, and point toward what good looks like.
- The fix is almost always controller-level: a reliable close and trustworthy measurables.
You're facilitating, not doing the books — but finance problems surface in your sessions constantly, disguised as other things. This is a practical guide to the exact moments when you should suspect finance is the real issue, and what to do in the room. It's written to be used, not admired.
Call finance when you hear the numbers questioned
The signal: a Scorecard measurable gets a caveat every week — "that's not quite right," "let me check that number." What it means: the close underneath is unreliable, so nobody trusts the data. What to do: ask, "Is finance giving you a reliable monthly close?" You've just reframed a data-quality complaint as a solvable finance-system problem.
Call finance when a green Scorecard hides a bad result
The signal: the Scorecard is green and Rocks get done, but profit or cash doesn't improve. What it means: the measurables track activity, not economics — they don't connect to outcomes. What to do: ask what financial measurable would have predicted the disappointing result. Usually there isn't one, and that's the gap.
Call finance when the same money Issue keeps regenerating
The signal: a cash or margin Issue gets IDS'd, disappears, and comes back a month later. What it means: the team is solving symptoms because they can't see the underlying financial picture. What to do: name it — "we keep solving this downstream; is the real issue that we can't see it coming?" That points toward forecasting and a forward cash view.
Call finance when planning runs on gut
The signal: budgets and V/TO financial targets are round numbers picked because they sound right. What it means: there's no reliable forecast to plan against. What to do: ask what the numbers would need to look like for the plan to work — and whether anyone can model it. If not, that's a finance-seat gap.
Call finance when the founder is the bottleneck
The signal: every financial question routes to the founder, who answers from memory. What it means: nobody owns the financial system — the finance seat is effectively empty. What to do: raise it as a seat question. Who owns finance on the Accountability Chart? Is that seat actually filled, or is the founder covering it?
You don't diagnose the general ledger. You recognize the pattern, name it as a question, and point toward what good looks like — a reliable close, trustworthy measurables, a forward cash view. Naming a finance-shaped problem accurately is high-value facilitation, and it stays firmly in your lane.
What to point them toward
Once you've named it, the fix is almost always controller-level: someone to systemize the numbers, own the close, and produce measurables the team trusts. Whether the client builds that in-house or brings in help is their call. To make the conversation concrete, bring the printable What the Finance Seat Should Own one-pager or the Finance Readiness Check to your next session.
Frequently asked
When should an EOS implementer suspect a finance problem?
When numbers get questioned every week, a green Scorecard hides a bad profit or cash result, the same money Issue keeps regenerating, planning runs on gut, or every financial question routes to the founder. These patterns point to finance, not strategy.
What should an implementer do when finance is the issue?
Recognize the pattern, name it as a question rather than a diagnosis, and point toward what good looks like — a reliable close, trustworthy measurables, and a forward cash view. The fix itself is controller-level work the company owns or outsources.
Should an implementer fix the client's finances?
No. That's outside the facilitation role. The implementer's value is recognizing and naming the finance-shaped problem so the leadership team can solve it — not doing the controller-level work themselves.