The Operating View

What a Controller Isn’t Built to Answer

A common piece of advice in the finance world holds that most small businesses do not need a CFO. What they need, the argument goes, is a strong controller or a capable director of finance: someone operationally sound who can keep the books clean, close the month on time, and produce reports that make sense. Leave the CFO for later, once the company is large enough to need strategy at the executive level.

The argument has merit. A good controller adds real value, and a business with one is better run than a business without. But the argument answers a question most owner-operators are not asking, and it rests on an assumption that rarely fits them.

What the argument assumes

The case for a controller assumes the financial foundation already exists. It pictures a business with reliable books, consistent monthly reporting, and an owner comfortable reading the results, which simply needs someone to maintain and refine what is already there.

Most owner-operated businesses between sub-$1M and $10M in revenue do not look like that. They have a bookkeeper recording transactions and an accountant filing what is due. They have reports the owner is not always sure how to interpret. And they have decisions piling up that none of that work can resolve. A controller placed into that environment will make the output cleaner. It will not make the business any better equipped to answer the questions keeping the owner up at night.

What a controller is built to do

A controller is oriented inward. The role centers on accuracy, compliance, internal controls, and reporting. Done well, it answers one question with precision: what happened? How much revenue came in, where the money went, whether the books tie out, and whether the business met its obligations.

That work matters, and a growing business usually has some of it covered already. The same holds for a director of finance. The role is operationally strong and effective inside the finance function, but it stays focused on recording and reporting results.

Neither role is designed to tell the owner what to do next.

The question they cannot answer

Should I hire? Can I expand? What is this business worth, and what would make it worth more? These are decision questions, and decision questions belong to the CFO function.

In businesses that do have a controller, that person ends up fielding them anyway. With no one else in the role, the controller becomes the de facto CFO: the person the owner turns to when a lender asks for projections, when a large contract needs pricing, or when a buyer calls. Many handle those moments admirably. But the role was never scoped or built for them. The controller can report what the last year looked like. Weighing the capital, risk, and long-term consequences of a major decision, and standing behind a recommendation on it, sits outside what the position was designed to do.

A business can operate on that partial coverage for a while. It works as long as the decisions stay small. Eventually a decision arrives that needs the full scope: a sizeable loan, a second location, an acquisition offer, an exit. At that point the gap between what the controller can do and what the decision requires is no longer theoretical.

Stratovus works alongside the controller. It supplies the full CFO scope when the business needs it, with oversight of the books, so the owner does not have to stretch a limited role past what it can carry.

Having the function or having none of it

The debate between hiring a controller or a CFO assumes the owner is choosing between two defined roles at a particular point on a growth curve. Most owner-operators are choosing between having the financial function and having none of it.

A fractional model changes that equation. Instead of hiring one role and leaving the rest uncovered, the business gets the oversight a controller provides, tax readiness recommendations, and the forward-looking leadership of a CFO, through a single relationship scaled to its needs.

A good fractional CFO builds systems the business can eventually run on its own: consistent monthly reporting, a working cash forecast, disciplined decision-making habits. The goal is a business that grows into its own finance function, with the right roles hired at the right time, because someone helped it get there. When the business eventually does need a full-time controller, it will know why, and it will be ready to hire one well.

Where the controller’s scope ends

A strong controller is an asset. The books close on schedule and the reports are dependable. None of that changes the scope of the role. A controller makes sure the numbers are accurate. The question in front of you asks what the numbers mean for a decision that has not been made yet.

Most owners find out where the controller’s scope ends when a decision is already on the table and the person they trust with the numbers says, reasonably, that it is outside what they do.

Related Reading

Share this post
← All Posts

Have a question your reports can’t answer?

Book a Free Consultation