Bookkeeper, controller, or CFO: who you actually need
These three roles get lumped together as finance, but they do different jobs at different altitudes. Knowing the difference saves you from overpaying for a CFO you do not need or underserving the work you do.
Founders often ask for a CFO when what they need is a bookkeeper, or hire a bookkeeper when the real gap is a controller. The titles blur together in everyday talk, and the result is a mismatch: either you pay senior rates for data entry, or you ask someone junior to make calls they are not equipped to make.
The three roles sit at different altitudes. A bookkeeper records what happened. A controller makes sure what was recorded is right and runs the finance machine. A CFO decides what should happen next with money. Same domain, very different work.
Here is the plain difference, what each does on an ordinary day, and which one your company actually needs right now. The short version, which we will defend below, is that most early companies do not need a CFO yet.
The bookkeeper: recording what happened
A bookkeeper keeps the day-to-day records accurate. They categorize transactions, reconcile the bank accounts so the books match reality, enter bills and invoices, and keep the ledger clean and current. Their work answers the question: what actually happened to our money?
On a normal day a bookkeeper is matching transactions, chasing a missing receipt, fixing a miscategorized expense, and making sure the numbers tie out. It is precise, important, and largely backward-looking. Get this wrong and everything built on top of it is wrong too, which is why it matters more than its modest reputation suggests.
Every company needs bookkeeping from day one. You can do it yourself at the very start, but the hours add up fast, and a clean foundation is worth far more than most founders expect.
The controller: making sure it is right and runs on time
A controller owns the integrity of the numbers and the process that produces them. Where the bookkeeper records, the controller verifies, structures, and reports. They own the monthly close, set up internal controls so money cannot quietly go missing, make sure the financial statements are accurate and on time, and handle the trickier accounting judgments.
On a normal day a controller is reviewing the close, deciding how an unusual transaction should be treated, tightening an approval process, and producing reports leadership can trust. Their work answers: are these numbers right, and can we rely on them?
You need controller-level work once your finances get complex enough that accuracy is no longer automatic, typically somewhere between ten and fifty people, or earlier if your business is complicated. This does not have to be a full-time hire. Controller-level oversight is one of the most common things to get on a fractional or outsourced basis, precisely because you need the judgment without needing forty hours of it a week.
The CFO: deciding what happens next
A CFO is forward-looking and strategic. They are not there to close the books; they are there to shape decisions about money. That means financial strategy, fundraising, major capital decisions, pricing and margin strategy, board-level conversations, and modeling the future of the business.
On a normal day a real CFO is in conversations about whether to raise, how to price a new product line, what a big hiring plan does to runway, and how to tell the company's financial story to investors or a board. Their work answers: what should we do next, and what will it do to the business?
Here is the honest part. Most companies under a certain size and complexity do not need a CFO yet, and many that hire one are really buying expensive controller work. A genuine CFO need usually shows up around a real fundraise, a possible sale, complex capital decisions, or scale where strategic financial choices are constant and high-stakes. Before that, a fractional CFO for a few days a month covers the real strategic moments without a six-figure salary sitting idle between them.
Matching the role to your stage
A rough guide, knowing every business is different.
Notice that the same person rarely does all three well, and the rates differ by a lot, so paying CFO rates for bookkeeping is pure waste. Match the work to the altitude. Get the bookkeeping clean first, add controller judgment when accuracy stops being automatic, and bring in CFO thinking when the decisions get genuinely strategic, not a day sooner.
- Just starting, up to a handful of people: you need solid bookkeeping. That is it, and that is fine.
- Growing, roughly ten to fifty people: bookkeeping plus controller-level oversight, often fractional or outsourced rather than a full hire.
- Raising, selling, or scaling fast: add CFO-level strategy, frequently fractional at first, full time when the strategic load justifies it.
A bookkeeper records what happened. A controller makes sure it is right. A CFO decides what happens next.