Bookkeeper, controller, or CFO

The bookkeeper

A bookkeeper records what happened. Transactions categorized, accounts reconciled, bills paid, payroll recorded. It's necessary and it's the foundation of everything else. What a bookkeeper is not hired to do is tell you what any of it means, and it's unfair to expect it — the role was never scoped for interpretation.

If your practice is simple, single-location, and you're comfortable reading a P&L yourself, a good bookkeeper may genuinely be all you need. We'll tell you if we think that's the case.

The controller

A controller owns accuracy and control: making sure the close is right, on time, and consistent, that the chart of accounts is appropriate, that reconciliations tie, and that the reporting can be trusted. In a practice this often looks like the person who makes sure deferred revenue is stated correctly and the practice management system reconciles to the books.

Most owner-operated practices can't justify a full-time controller, which is why the function usually gets outsourced or, more commonly, simply goes undone.

The CFO

A CFO interprets accurate numbers into decisions: forecasting, pricing, provider economics, capital and financing choices, growth planning, and eventually exit. A CFO with unreliable data is worse than useless, because confident conclusions drawn from wrong numbers are more dangerous than no conclusions at all.

That sequencing is the whole point. You need controller-level accuracy underneath any CFO-level strategy, which is why we won't run advisory on top of books we haven't fixed.

What a practice usually actually needs

For most owner-operated practices: bookkeeping and controller-level close done properly, plus CFO-level interpretation a few hours a month. That's a strange shape to hire for directly — nobody wants a fifth of a controller and a tenth of a CFO — which is precisely why the fractional model exists in this category.