Let's connect
Oops! Something went wrong while submitting the form.
Finance hires at growing companies usually only happen under pressure. The close slips 3 weeks, an investor asks for a forecast nobody has, a bank wants covenant reporting by Friday, and suddenly there's a job posting up for whichever title sounds closest to the problem. Sometimes that lands. More often you end up with an expensive hire doing work 2 levels below their pay grade, or a capable person who's in over their head through no fault of their own.
Accountant, controller, and CFO are 3 separate jobs that solve 3 separate problems. They stack well together, and a strong finance organization eventually has all of them in some form. But they're not interchangeable, and hiring the wrong one at the wrong moment costs you time you don't have. Start with the problem you're actually trying to solve. The right title becomes obvious after that.
In a company of 40 people, one person usually does all of it. They enter the bills, run payroll, close the books, build the board deck, and answer the auditor's questions. That's resource math, and it works right up until the volume gets away from you. By then the responsibilities have blurred so completely that nobody can say which part of the job is the bottleneck, and the title on the org chart has stopped describing the work. That's what makes these hires go wrong. A CEO decides it's time to hire a controller, but what they're picturing is shaped by a title they've seen somewhere else rather than the work actually sitting on their own desk. You're better off writing down the 5 things that keep breaking and hiring against that list.
An accountant keeps the record straight. They're in the details of what is happening: the invoice that got coded to the wrong account, the bank feed that stopped syncing, the customer payment that came in $412 short. When the underlying transactions are correct, the output is a clean, complete set of books, and everything the rest of your finance function does depends on that being right. If the underlying data is bad, no amount of reporting or forecasting on top of it will save you. This work is transactional and compliance-oriented by design, and that's a feature. You want someone who cares that the reconciliation ties out and who'll chase down a variance nobody else noticed.
Day to day, that work looks like:
A controller owns the system that produces your numbers. They run the close, set the calendar, decide who does what and by when, and put controls in place so the same error doesn't show up 4 months in a row. Where an accountant makes sure a transaction is recorded correctly, a controller makes sure the whole process is repeatable and defensible, including when an audit firm starts asking questions.
This is usually the layer companies feel the absence of most sharply. Your books can be technically accurate and your reporting still be useless if the close takes 30 days, the numbers move every time someone asks about them, and the same monthly package looks different in March than it did in February. A controller makes the reporting something you can hand to a lender or a board without caveats.
In practice, that means:
A CFO is looking out the windshield. Their job is what the numbers mean and what you should do about them. They spend a lot of time outside of accounting, with your board and your lenders, and inside the business with the sales and operations leaders who control the drivers behind the forecast.
A good CFO also changes how leadership makes decisions. The monthly numbers become the starting point for a real conversation about tradeoffs, with a model behind it. That's worth a great deal at the right stage. It's worth almost nothing if your close isn't reliable, because a CFO working from questionable data will just produce confident answers built on sand. This is why the sequencing matters so much, and why the controller layer tends to be the one companies regret skipping.
The work usually includes:
The cleanest way to separate these roles is by what they're looking at and how far ahead they're looking. Here's how they compare:
Ignore the titles for a minute and write down what's actually going wrong this month. Is the data wrong, so you don't trust what you're looking at? Is the data fine but you can't get it out on a predictable schedule, in the same format, without 3 rounds of questions? Or is the reporting solid and you still can't answer what the board asked you last week? Those symptoms point to different hires, and they're rarely ambiguous once you've named them out loud.
Be specific about the pain that's costing you now. Reconciliations 6 weeks behind is a live problem. A Series B you haven't started raising is a plan. And if more than one symptom is real at the same time, work bottom up. Reporting you can't trust undermines every decision made on top of it, so the foundation goes first even when the strategic gap feels more urgent.
The expensive version of this mistake is hiring a CFO too early, where a company brings on a strategist and then hands them a chart of accounts to rebuild because there's nobody else to do it. You've paid CFO money for controller work, and the CFO is usually gone within a year. Expecting an accountant to provide strategy produces the opposite failure: a forecast nobody should be making decisions on, and frustration on both sides of the conversation. Skipping the controller layer causes quieter damage. The close stays slow, audit fees creep up every year, errors get caught by customers instead of by you, and your outside CPA bills for cleanup that should have gone toward decisions. Companies can carry that last one for years without ever putting a number on it.
You don't always know the shape of the role until someone's in the seat. That's the argument for bringing in interim support: you get the level of expertise the problem calls for, right now, without a full-time commitment made on incomplete information. A 4-month interim controller engagement to rebuild your close will teach you more about what you need permanently than 4 months of interviewing will.
Interim support also fits the reality that finance needs come in bursts. An acquisition, a first audit, a system implementation, a controller who leaves 3 weeks before year-end. Those are real problems with a defined end date, and they call for someone who can start in days rather than the 3 to 5 months a senior search typically takes. The level can flex too. Bring in a senior accountant for the reconciliation backlog, add controller-level oversight for the close, pull in CFO-level help for the forecast, and adjust as the work changes.
At CX, we embed senior finance and accounting professionals on an interim, temporary, and part-time basis, from senior accountant through controller and CFO. Part of our job is helping you figure out which one you actually need, since the title in the job description and the work on the desk often don't match. Our people come out of public accounting and industry, they're used to walking into unfamiliar systems and making progress in the first week, and they bring the full Connor Group network with them when a technical question comes up. If you're weighing a finance hire and want a second opinion on the level, we're glad to talk it through.
