Here is the shortest honest answer: if your problem is that you don't trust your numbers, you need a controller. If you trust your numbers but they don't tell you what to do next, you need a CFO. A controller makes the financials right. A CFO makes them useful. And in most growing businesses I sit down with, the controller problem has to be fixed first, because you cannot forecast off books you don't believe.
Owners search for these two titles interchangeably, and I understand why. Both are "the finance person you hire when the bookkeeper isn't enough." But they are different jobs, they solve different problems, and they cost different money. Hiring the wrong one wastes both.
The three jobs owners lump together
Most businesses climb the same ladder, whether they know it or not.
The bookkeeper records. Transactions get entered, bills get paid, invoices go out, the bank account gets reconciled. This is essential work and it is entirely about capturing what happened. A good bookkeeper keeps the record accurate day to day.
The controller makes the record trustworthy and on time. A controller owns the monthly close, so your financials show up by a fixed date every month instead of whenever the dust settles. They build the processes and controls around the books: who can approve a payment, how job costs get coded, why the balance sheet actually reconciles instead of carrying mystery balances for three years. When a controller is doing the job, the P&L you read on the 10th of the month is a document you can bet on.
The CFO uses the trustworthy record to make decisions about the future. Cash forecasting, pricing, whether the next hire pays for itself, how to structure debt, what the business needs to look like to be sellable someday. I've said this before and it stays true: an accountant works on the past, and your CFO works on the future. The controller sits in the middle, turning raw bookkeeping into something the future can actually be built on.
The confusion comes from small-business reality: at most companies under a few million in revenue, nobody holds either title. The bookkeeper does a bit of everything, the CPA sees the books once a year, and the owner is the de facto CFO on gut feel. The question is not which title to add to the org chart. It's which gap is costing you money right now.
A simple test: which of these sounds like you?
You have a controller problem if:
- Your financials arrive late, or not at all, and you run the business off the bank balance.
- You don't fully believe your P&L. Margins jump around month to month in ways nobody can explain.
- Your CPA spends the first chunk of tax season fixing the books before they can file anything.
- You can't tell which jobs, products, or service lines made money until long after the fact.
You have a CFO problem if:
- The books are clean and on time, but you're still making six-figure decisions on instinct.
- You can say what cash is today but not what it will be in 60 or 90 days.
- You're facing a bank negotiation, a big equipment purchase, a pricing change, or a possible sale, and nobody is modeling it.
- Growth is up and profit isn't, and you can't see why. That pattern usually means profit is fine on paper while cash disappears, and someone needs to trace where.
Notice the pattern. Controller problems are about whether the numbers are right. CFO problems are about what the numbers mean for what you should do next. If you checked boxes in both lists, start with the controller work. Forecasts built on unreliable books aren't forecasts. They're guesses with spreadsheets.
Why trades and specialty contractors usually need the controller first
This distinction matters most in the industries where the books are hardest to keep right, and construction and the specialty trades top that list. Job costing, work-in-progress, retainage, progress billing, equipment costs spread across projects: this is exactly the bookkeeping that drifts out of true without controller-level discipline. A contractor's P&L can look healthy while three jobs quietly run over budget, because nobody closed the books job by job.
That's why, for a lot of the trades and construction businesses we work with, the first months of an engagement look like controller work even when the owner came in asking about CFO strategy. Get the monthly close reliable, get job costing real, get the WIP tying to the financials. Then the forward-looking work has something to stand on. The strategy conversation you actually want is only possible after the numbers deserve your trust.
What each one costs
Titles aside, this is the practical fork in the road, so here is the honest math. Hiring internally, a full-time controller runs roughly $145K to $195K a year fully burdened, once you count payroll taxes, benefits, PTO, and the overhead of managing the role. An internal CFO runs roughly $235K to $315K. Very few businesses under $10M in revenue can justify either as a full-time seat, and most don't need forty hours a week of it anyway.
That is the entire case for the fractional model. You buy the level of judgment you need, at the hours the business actually requires. At DAT Finance, controller-level engagements start around $36K per year and fractional CFO partnerships start around $60K, with most partnerships falling between $2,500 and $10,000 per month depending on scope, cadence, and complexity. The full breakdown, including how we price against an internal hire, is on our FAQ and pricing page.
One more honest note: in a fractional engagement, the line between the two roles is a dial, not a wall. Plenty of our partnerships blend both, heavier on controller discipline early, shifting toward CFO work as the books earn trust.
The decision in one paragraph
Don't hire for the title. Hire for the gap. If the financials are late, messy, or unbelievable, buy controller discipline first, because everything else depends on it. If the financials are solid and the decisions are still foggy, buy CFO judgment. And if you're not sure which gap you're looking at, that diagnosis is a 30-minute conversation, not a commitment. Our process page shows how we figure that out with owners.
FAQ
What's the difference between a controller and a CFO? A controller is responsible for the accuracy, timeliness, and controls of your financial records: the monthly close, reconciliations, and processes. A CFO uses those records to lead forward-looking decisions: cash forecasting, pricing, capital, and strategy. Accuracy versus direction.
Can one person do both jobs? In a fractional engagement, often yes, and many of ours blend the two. The caution is with full-time hires: a great controller isn't automatically a CFO, and a strategy-minded CFO often has no patience for close discipline. Buy the skill you need, not the title.
When is a bookkeeper enough? When transactions are simple, volume is low, and you personally have a handle on margins and cash. A bookkeeper plus a once-a-year CPA works for a lot of small operations. It stops working when the books start driving decisions they aren't sturdy enough to carry.
How much does a fractional controller cost compared to a fractional CFO? Our controller-level engagements start around $36K per year; fractional CFO partnerships start around $60K. Both are a fraction of the fully-burdened cost of the internal hire, which runs $145K to $195K for a controller and $235K to $315K for a CFO. Details on our FAQ and pricing page.
Which one does my business need first? If you don't trust your monthly financials, controller first, no exceptions. Forward-looking CFO work built on unreliable books is guesswork. If the books are already tight, go straight to the CFO conversation. Here's how to know when that time has come.
If your financials are always late, or always right but never useful, that's not a character flaw in your bookkeeper. It's a missing role. Talk to us and we'll tell you plainly which one you're missing.