Short version: You need a controller when accuracy stops being the problem and trust becomes the problem, when the books are technically fine but late, unreviewed, or not something you'd bet a decision on. That gap almost always opens before you can justify a full-time hire, which is why most businesses meet the role as a fractional one. The signs below are the real trigger; revenue is a weak proxy.
Nobody wakes up and decides to hire a controller. What happens is a slow accumulation of small frustrations: the numbers come late, they don't quite add up, you make a call on gut because the report wasn't ready, and one day you realize you're running a real business on books you don't fully trust. That's the moment. Here's how to recognize it earlier.
Two different gaps, and people confuse them constantly.
If your books aren't current, aren't reconciled, or live half in a shoebox, you have a bookkeeping gap. Fix that first; nothing above it works without clean data. But if your books are accurate and current and you still can't get a straight answer out of them, more bookkeeping won't help. That's the controller gap: the layer that turns a correct ledger into something closed on time, reviewed, controlled, and framed so you can actually decide from it. For the full picture of how the roles stack, see bookkeeper vs. accountant vs. controller vs. CFO.
If three or more of these sound like your month, you're past the trigger.
The one-line test: if your books are accurate but you still can't make a confident decision from them, you don't need a better bookkeeper or a second CPA. You need the controller layer between them.
People want a revenue number. The honest answer is that it tracks complexity, not size. A simple service business can run clean well into the millions; an inventory, construction, or multi-entity business needs the controller function much earlier, sometimes under a million in revenue, because the accounting is genuinely harder. The signs above are a better trigger than any dollar figure. If you're hitting them at $800k, you're not early; you're right on time.
Here's the trap: the need for the controller function shows up long before the workload justifies a full-time controller salary. Owners feel the gap, price a full-time hire, decide it's too expensive, and do nothing, which is the worst option. The function doesn't require a full seat.
| Full-time controller | Fractional / outsourced | |
|---|---|---|
| Typical cost | Six-figure salary plus benefits | Commonly $1,500–$4,000/mo |
| Best fit | High volume and complexity that fills a full role | Outgrown a bookkeeper, not yet a full seat |
| You get | A dedicated, in-house owner of the function | The close, the review, and the reporting, scaled to you |
| Ramp | Hiring, onboarding, management overhead | Running in days, no headcount |
For most businesses hitting the signs above, fractional is the right first move. You get the review and the reporting without a six-figure commitment, and you can step up to full-time later when the volume genuinely fills the role.
Concretely, in the first couple of months the controller layer puts four things in place: a repeatable month-end close on a calendar, so the numbers land on time; basic controls so the books can't quietly drift and so one person isn't recording and reviewing their own work; management reporting that answers the questions above at a glance; and a review habit over whoever keeps the books. None of it is glamorous. All of it is the difference between numbers you react to and numbers you steer with.
The cost of waiting isn't a line item. It's every decision you made on late or shaky numbers, and you'll never see that bill itemized.
That's the gap The Practical Controller is built to fill, fractional controller support that gives you the close, the review, and the reporting without a full-time hire. See how it works, or read who's behind it.
When accuracy stops being the problem and trust, timeliness, and interpretation become the problem. The common signs: chronically late books, numbers you don't trust, a month-end scramble, nobody reviewing the bookkeeper, and reporting that hasn't kept up with growth. The gap usually opens before you can justify a full-time hire.
If your books aren't current or reconciled, you need bookkeeping. If they're accurate but late, unreviewed, or you still can't decide confidently from them, that's the controller gap. The bookkeeper keeps the record; the controller makes it trustworthy and useful.
Most businesses hit the need for the function well before they can justify a full-time salary. A fractional or outsourced controller delivers the close, review, and reporting at a fraction of the cost. You move to full-time when the volume and complexity fill the role.
There's no clean number; it tracks complexity more than revenue. The function commonly becomes necessary in the low millions, earlier for inventory, construction, or multi-entity businesses. The signs matter more than the size.
Usually not well. A tax CPA works at quarter- and year-end on compliance, not the weekly and monthly operating cadence a controller runs. They're complementary: the controller keeps the books decision-ready all year; the CPA handles tax.
A full-time controller is commonly a six-figure salary plus benefits. A fractional or outsourced controller is commonly $1,500 to $4,000 a month depending on scope and volume, which is what makes the role accessible to a business that needs the function but not a full seat.
General guidance on structuring a finance function, not accounting, tax, or legal advice. Cost ranges are typical US figures and vary by market, industry, and scope.
Practitioner guides on running cleaner books and building the right finance team. One email per guide. Unsubscribe in a click.