When do you need a controller?

Almost nobody wakes up and decides to hire a controller. What happens instead is a slow accumulation of small frustrations — the close is late again, a number looked wrong and took two days to explain, the bank asked for something that took a week to produce — until someone says out loud that this isn't working.

The gap between when a business needs a controller and when it gets one is usually about a year. That year is expensive in ways that don't show up anywhere.

What a controller actually does

A bookkeeper records what happened. A controller is responsible for whether it's right, whether it's on time, and whether the structure it's recorded in is useful.

• Owns the close. A defined process with a defined finish date, rather than a task that ends when it ends.
• Sets accounting policy. Revenue recognition, accruals, prepaids, capitalisation — applied consistently so periods are comparable.
• Designs the chart of accounts. So it reflects how the business operates rather than how the tax return is organised.
• Reviews rather than records. Someone checking the work who didn't do the work.
• Builds internal controls. Approval thresholds, segregation of duties, reconciliation discipline.
• Handles external requests. Lenders, auditors, insurers, diligence.

The short version: a bookkeeper produces the numbers, a controller makes them trustworthy and timely.

Six signals

1. Your close is later than the 20th

The clearest single indicator. It usually means the process is undefined rather than that the person is slow.

2. You've found errors yourself

If the owner is the review layer, there isn't one. Every hour you spend checking the books is an hour not spent running the business, and you're the least efficient person to do it.

3. The structure no longer fits

Multiple entities, multiple locations, several service lines, deferred revenue, inventory, or a new state to register in. Complexity is what controllers exist for.

4. Someone external is about to look

A loan, a lease guarantee, an insurance review, a buyer, an investor. All of them want reconciled, consistent, timely statements — and the scramble to produce those under deadline is where mistakes get made.

5. You can't answer basic questions without a project

"What did we make on the Henderson job?" or "what's our margin on maintenance work?" should take minutes. If it takes a day of spreadsheet work, the underlying structure is wrong.

6. Headcount past about fifteen

Not a hard rule, but around this point payroll complexity, expense approvals and departmental cost tracking usually outgrow what a bookkeeper can hold.

Full-time, fractional, or neither

A full-time controller runs roughly $80,000–$120,000 plus benefits — call it $100,000–$145,000 all in. That's justifiable for most businesses somewhere north of $10M in revenue, sooner if the operation is complex.

Below that, the honest answer is that most companies need controller function without controller headcount. The work is real but it isn't forty hours a week, and hiring full-time means paying for capacity you can't use.

The third option is worth naming: sometimes what you need isn't a controller at all, it's a one-off cleanup. If your chart of accounts is wrong and your close has no process, a project to fix both may buy you another eighteen months with the bookkeeper you already have.

Don't hire a controller to compensate for a broken system. Fix the system, then decide whether you still need the role.

What changes when you get it right

The visible change is timing — numbers on the 15th instead of the 23rd. The more valuable change is that you stop wondering whether they're right.

That sounds soft, and it isn't. An owner who trusts their financials makes decisions faster, commits with more confidence, and stops holding a private mental buffer against the possibility that the numbers are wrong. That buffer is expensive, and most owners don't notice they're carrying it until it's gone.