Bookkeeper, controller, or CFO?
Three different finance roles, three different jobs. Here's who owns the finance seat as an EOS company grows — and when each earns its place.
"We need finance help" can mean three very different things. Knowing which role a company actually needs prevents both overspending on a CFO too early and starving the business of the controller-level work that makes the Data component real.
Bookkeeper — records the numbers
Enters transactions, categorizes, keeps the ledger current. Essential and foundational, but the job stops at recording what happened. A bookkeeper alone rarely produces a reliable close or trustworthy Scorecard measurables.
Controller — makes the numbers trustworthy
Owns the monthly close, reconciliations, and reporting. The controller is the role that makes the Data component real: books that close on time, numbers the team can trust, and measurables that reflect true health. For most growing EOS companies, this is the missing piece — not a CFO.
CFO — uses the numbers to decide
Strategy, capital, forecasting at a high level, board and investor relationships. A CFO is powerful, but only once the controller-level foundation is solid. A CFO hired onto shaky books spends their time fixing the books instead of leading.
Most growing companies think they need a CFO when they need a controller first. Get the close and the Scorecard trustworthy, and a future CFO — full-time or fractional — can actually do their job.
How to tell where you are
If your core need is "our numbers need to be right and on time," that's a controller. If it's "we need help raising capital or planning an exit," that's a CFO — assuming the controller layer already exists underneath.