Do you actually need a CFO?
'We need a CFO' is usually one of four different problems. Three of them have cheaper, faster answers — and one of those three is the most expensive mistake in the sequence.
Who owns finance, and does the close land?
Can anyone explain the business?
What is actually happening?
Complexity and constraints
None of this is a standard and there is no authority behind it, only a pattern — stated plainly so you can disagree with it. The one exception is the public company principal financial officer requirement, which is a real constraint and is marked as one.
Four problems wearing the same sentence
“We need a CFO” is almost always one of four different statements, and three of them have cheaper, faster and more effective answers. The numbers are late or wrong — that is a controller. Nobody can explain what is happening in the business — that is FP&A, which is analytical capacity rather than seniority. Something transactional is in flight — genuinely senior work, and episodic, which is the worst possible shape for a permanent hire. And fourth: nobody is making capital allocation decisions. Only the fourth is a problem that a CFO is the answer to.
The test for the fourth one is whether the decisions exist yet. A company with one product, one market, one source of funding and no board has very few choices about where the next dollar goes that anyone would seriously argue about. A good CFO hired into that discovers it around month three. They then do the close because the close is there, or build a model nobody asked for, and within eighteen months they are taking calls from recruiters. The decisions should arrive before the hire does.
The most expensive version of getting this wrong is the sequencing one. A CFO hired on top of a broken close inherits the close. Not sometimes — every time, regardless of what the job description said or what both sides intended, because it is urgent and visible and nobody else will pick it up. What has been purchased is a controller at roughly three times the price, doing work they are not especially good at, in a role that is not the one they accepted. Hiring the controller first costs less, works sooner, and makes the eventual CFO hire a better one, because that person will be doing the job they were hired for from their first week.
None of this is a rule, and it is worth saying so directly: there is no standard, no regulation and no professional guidance on when a company should hire a CFO. There is one genuine constraint in the area, which is that a public company must have a named principal financial officer, and that the certifications accompanying its periodic reports are signed personally by that person — who is accepting personal exposure for the accuracy of the reporting and the effectiveness of the controls behind it. That role cannot sit vacant, be shared informally, or be filled at arm’s length. Everything else here is an argument you are free to lose.
What this tool does not do
This is judgment, not a standard, and it says so on screen. There is no rule, regulation or professional guidance on when a company should hire a CFO - only a pattern, stated plainly enough that you can disagree with it, which is the point. The one genuine constraint is the public company principal financial officer requirement, and that is marked differently from everything else. The tool routes to a controller, to an analyst, to a full-time hire and to 'not yet' - the last of which is reachable and is a real answer.
- What to pay, in salary or equity - that is a market question and it moves
- Finding, interviewing or assessing a candidate, and whether a particular person is any good
- The difference between a CFO, a VP Finance and a Chief Accounting Officer at your stage, which is mostly a titles-and-market question
- Your specific org design, reporting lines, or who the role should report to
- Whether your close is fixable with the people you already have
- Anything about employment law, notice periods, or the mechanics of hiring
- The board's own view, which in a venture-backed company is frequently the actual driver of this decision
- Whether the CEO wants a CFO for reasons that have nothing to do with any of the four problems
Frequently asked questions
At what revenue does a company need a CFO?
There isn't one, and revenue is the worst available trigger for this decision despite being the most commonly used. The rules of thumb — a CFO at ten million, at twenty, at fifty — describe a correlation with the things that actually create the need: the number of legal entities, the number and type of funding sources, whether a board with its own view exists, whether reporting obligations attach, and whether real capital allocation decisions exist. A simple business at high revenue may need one far less than a complex business at a fraction of it.
Our month-end close is a mess. Will a CFO fix it?
They will do it, which is not the same thing. A CFO hired on top of a broken close inherits the close — every time, whatever the job description said, because it is there and it is urgent and nobody else will. You have then bought a controller at roughly three times the price, doing work they are not especially good at, in a job that is not the one they accepted. Hire the controller first; the CFO you hire eighteen months later will be better and cheaper because they will do the job you hired them for from week one.
We can't answer basic questions about the business. Is that a CFO problem?
Usually not. Not being able to say why margin moved, or not having a model anyone trusts, is an FP&A problem — analytical capacity rather than seniority. One competent analyst, sometimes two days a week of an experienced one, and a model that is maintained rather than rebuilt whenever it is needed. It costs a fraction of a CFO, it is available immediately, and it removes most of what a founder actually feels when they say they need a CFO.
We're raising. Should we hire a CFO first?
A raise is real work that genuinely needs senior finance, and it is episodic — which is the worst possible shape to solve with a permanent hire. The transaction ends and the salary does not, and the person hired for transaction skills is frequently not the person you want running finance afterwards. Part-time senior help for the duration keeps the decision reversible and lets the permanent question be answered later on its own merits. Going public is the exception: it creates a permanent obligation rather than an event.
What actually is the CFO job?
Deciding where the next dollar goes, what the capital structure should be, what to stop doing, and holding a position with a board that has its own view. If those decisions do not yet exist — one product, one market, one funding source, no board — then a CFO hired into that discovers it in month three, does the close because it is there, and starts taking calls. The decisions should arrive before the hire, not the other way round.
Is any of this an actual rule?
No, and the tool says so. There is no standard, regulation or professional guidance on when to hire a CFO — only a pattern, stated plainly so you can disagree with it. The single exception is that a public company must have a named principal financial officer who personally signs the certifications, accepting personal exposure for the accuracy of the reporting and the controls behind it. That is a genuine constraint and the tool marks it differently from everything else.