When Does a Company Need FP&A? 11 Signs You’ve Outgrown Basic Finance
I don’t think a company wakes up one morning and suddenly needs FP&A.
There usually isn’t a ceremony.
Nobody cuts a ribbon.
What happens instead is that the CEO asks a question that used to take ten minutes to answer, and three days later Finance is still working on it.
Someone wants to know what happens if hiring continues at the current pace.
Or why gross margin fell.
Or whether the company can afford a new initiative.
Or where revenue is actually going to land this year.
The Controller has some of the answer.
Sales has another piece.
There’s a spreadsheet involved.
Possibly several.
Eventually everyone gets an answer.
Nobody is entirely sure they’d get the same answer if they asked again next Tuesday.
That’s usually when I start thinking:
You may need FP&A.
Not because the company reached a magical revenue number.
Because the financial questions have become more complicated than the finance function’s ability to answer them.
What Is FP&A Supposed to Do?
FP&A stands for Financial Planning & Analysis.
Technically, FP&A is responsible for things like:
- budgeting,
- forecasting,
- financial modeling,
- management reporting,
- variance analysis,
- scenario planning,
- performance analysis,
- and decision support.
That’s the job description.
The version I care about is simpler.
FP&A helps management answer three questions:
What happened?
What is likely to happen next?
What should we do about it?
Accounting is extraordinarily important, but its primary job is different.
Accounting records and reports what happened.
FP&A takes those actual results and starts looking forward.
That distinction becomes more important as a company grows.
At some point, knowing what happened last month stops being enough.
Management needs help thinking about next month.
And next quarter.
And what happens if the thing everyone confidently put into the budget does not, in fact, happen.
Finance gets invited to some wonderful conversations.
There Isn’t a Revenue Number Where FP&A Suddenly Appears
People sometimes ask:
At what revenue level does a company need FP&A?
I understand the question.
I just don’t think revenue alone answers it.
I’ve seen relatively small businesses with complicated financial decisions that would benefit enormously from FP&A.
I’ve also seen larger businesses with predictable economics where the need develops differently.
A $20 million SaaS company with aggressive hiring, multiple customer segments and changing retention dynamics may need sophisticated planning earlier than a $50 million business with stable revenue, predictable costs and very little operational change.
Complexity matters.
Growth matters.
Cash matters.
Investor expectations matter.
The number of decisions management is making matters.
Revenue is one clue.
I wouldn’t let it make the decision by itself.
Sign #1: The CEO Keeps Asking Questions Finance Can’t Answer Quickly
This is probably one of my favorite signals.
Not because Finance should instantly know everything.
It shouldn’t.
But pay attention to the questions management is asking.
What happens if we hire 20 people?
Can we afford to open another location?
What happens to EBITDA if revenue comes in 10% below plan?
Which customers are actually driving growth?
Why did margins fall?
How much cash will we have six months from now?
What happens if we change pricing?
If every question triggers a small research project, the company may have outgrown basic financial reporting.
I once heard someone describe Finance as the place where you go to find out what happened.
That’s Accounting.
I want FP&A to be the place management goes when it’s trying to decide what happens next.
That’s a much harder job.
It’s also a lot more interesting.
Sign #2: The Controller Has Quietly Become the FP&A Department
This happens all the time.
The company has a Controller.
The Controller owns the close, financial statements, reconciliations, controls, audit, compliance and all the other things required to keep Finance from becoming a crime scene.
Then management asks for a forecast.
So the Controller builds one.
Then a budget.
Then a board analysis.
Then a scenario.
Then somebody wants a headcount model.
Congratulations.
You now have FP&A.
You just haven’t staffed it.
I have enormous respect for good Controllers. The best ones can do an impressive amount.
But there is a practical limit to how much forward-looking planning you can pile onto the person responsible for making sure the past is correct.
At some point something gets squeezed.
Usually it’s the work without the hard deadline.
The close has a deadline.
Payroll has a deadline.
Audit has a deadline.
Forecasting?
We’ll get to it.
That’s how a company can technically have a forecast while still not having much FP&A.
Sign #3: The Budget Has Become the Forecast
I get suspicious when I see this.
The company builds an annual budget.
January happens.
February happens.
March happens.
Customers behave differently than expected.
Hiring changes.
Sales changes.
Costs change.
The economy changes.
And somehow the full-year outlook remains remarkably loyal to the number everybody agreed to last fall.
That isn’t always discipline.
Sometimes nobody is actually forecasting.
A real forecast should change when the business changes.
If management is still making decisions using a nine-month-old view of the company because that’s the only forward-looking financial plan available, FP&A can add a lot of value.
I like commitment.
I also like current information.
Finance should be capable of holding both thoughts at once.
Sign #4: Nobody Can Explain Why the Numbers Changed
This one bothers me more than the miss itself.
Revenue is down $1.2 million.
Okay.
Why?
“Sales were lower.”
I can see that.
We’ve successfully established subtraction.
What happened in the business?
Was volume down?
Pricing?
Timing?
A large customer?
Product mix?
Pipeline?
Conversion?
If management reporting repeatedly stops at describing the variance, the company may need stronger FP&A capability.
Good FP&A connects financial results to operating behavior.
That’s how a number becomes useful.
Otherwise we’re just reading the income statement aloud with more expensive employees.
Sign #5: Every Department Has Its Own Version of the Number
Ask Sales for revenue.
Ask Finance.
Ask Operations.
Ask the CEO.
If you’re feeling adventurous, ask all four in the same meeting.
Sometimes you discover the company has several perfectly reasonable answers to what appears to be one question.
This is usually not because everyone is incompetent.
Definitions developed differently.
Systems don’t connect.
Reports were built for different purposes.
Timing differs.
Someone excludes something someone else includes.
Over time, people learn which number to use in which meeting.
That’s when I start worrying.
FP&A can help establish consistent definitions and a common financial view of the business.
Not because every number everywhere must be identical.
But management should understand why numbers differ.
“Depends which spreadsheet you open” isn’t a financial reporting policy I’d recommend.
Sign #6: The Company Is Growing Faster Than Finance
Growth hides a lot of problems.
Revenue is increasing.
People are getting hired.
Customers are arriving.
Everyone is busy.
It’s exciting.
Finance is holding everything together with the same processes it used when the company was half the size.
For a while, this works.
People compensate.
They stay late.
They build another spreadsheet.
They add another reconciliation.
They create another report.
Someone develops a process involving an email attachment that must be renamed before being dropped into a folder.
Nobody knows why.
Do not touch the naming convention.
Eventually the business gets too complicated for heroics.
That’s usually when people say:
“We need a better system.”
Maybe.
But I want to understand the work first.
Sometimes you need software.
Sometimes you need FP&A.
Sometimes you need to stop doing seven things nobody needs.
My favorite solutions tend to involve fewer things.
Sign #7: Leadership Is Getting Surprised
I don’t expect FP&A to eliminate surprises.
If anyone has figured out how to do that, please don’t waste your time in corporate Finance.
There are considerably more profitable applications.
But repeated financial surprises deserve attention.
Cash came in lower than expected.
Hiring was much higher.
A customer churned and Finance learned after the fact.
Margins deteriorated for three months before anyone investigated.
An expense category quietly grew 40%.
The forecast missed for a reason people inside the business already knew.
That last one gets me.
The information existed.
It just didn’t reach the financial plan.
Good FP&A builds channels between what’s happening operationally and what Finance expects financially.
The forecast should not be the last place in the company where reality arrives.
Sign #8: Cash Has Become a Topic Everyone Suddenly Cares About
Cash has an amazing ability to create cross-functional interest in Finance.
A company can ignore a mediocre planning process for years.
Then liquidity gets tight.
Suddenly everyone would like a cash forecast.
Immediately.
Preferably with several scenarios.
This is one reason companies often discover FP&A during a difficult period.
Maybe growth is consuming working capital.
Collections slowed.
The company is raising capital.
Debt payments increased.
Hiring got ahead of revenue.
Whatever the reason, management needs visibility.
How much cash do we have?
What’s coming in?
What’s going out?
Where is the low point?
What happens if collections slip?
When cash becomes an important management variable, stronger FP&A capability usually becomes more valuable.
I’d rather build that capability before the bank balance starts sending meeting invitations.
Sign #9: Planning Takes Forever
I pay attention when everyone hates the budget.
Not normal hates-the-budget.
Finance people are allowed a reasonable amount of seasonal complaining.
I mean the process has become absurd.
Eight weeks.
Twelve versions.
Templates emailed everywhere.
Numbers manually consolidated.
Headcount doesn’t tie.
Departments are working from different assumptions.
Finance spends most of the process checking whether someone inserted a row.
By the time the budget is approved, everyone is exhausted and the first month is already wrong.
That’s not a budgeting problem.
That’s a planning-process problem.
FP&A should make planning more useful, not turn November into an endurance sport.
Sign #10: The CFO Is Spending Too Much Time Building Things
There is a difference between a CFO reviewing a model and a CFO being the only person who can build it.
I pay attention when the CFO is personally:
updating forecasts,
building board schedules,
consolidating department budgets,
maintaining headcount files,
pulling recurring reports,
or answering every analytical question themselves.
Some involvement is healthy.
All of it isn’t.
The CFO should be using financial information to help run the business.
If they’re spending Sunday afternoon fixing formulas because nobody else can update the forecast, that’s a capacity signal.
And yes, I know there are CFOs reading this thinking:
Sunday afternoon isn’t that bad.
It is.
We’ve simply been in Finance too long.
Sign #11: Management Has Data but Still Can’t Make a Decision
This is becoming more common.
Companies have dashboards.
Lots of dashboards.
Revenue dashboards.
Sales dashboards.
Marketing dashboards.
Operations dashboards.
There are charts everywhere.
I enjoy a good chart as much as the next finance person.
But eventually somebody has to decide something.
Should we hire?
Should we invest?
Should we cut spending?
Should we change pricing?
Should we enter the market?
Should we delay the project?
Data doesn’t automatically produce a decision.
FP&A sits in the uncomfortable middle between information and action.
That requires more than reporting.
It requires judgment.
And occasionally the willingness to say:
“We have enough information. Pick one.”
As someone who can personally spend 45 minutes reading reviews before ordering a $17 item online, I appreciate the irony here.
Apparently professional judgment has boundaries.
Do You Need a Full FP&A Team?
Not necessarily.
This is where I think companies sometimes jump too quickly.
They identify an FP&A problem and immediately start drawing an org chart.
VP.
Director.
Manager.
Analyst.
We haven’t even figured out what these people are supposed to do yet.
Start with the work.
What decisions need support?
What planning processes are missing?
What analysis does management need?
How complicated is the business?
How frequently does the work recur?
Then decide what capability you need.
For one company, that may be a single strong FP&A hire.
For another, it might be a small team.
Another may need an experienced consultant to build the function before hiring permanent employees.
Another may simply need its existing Finance team organized differently.
I would rather design the work and then hire the people than hire the people and hope useful work appears.
When Should You Make Your First FP&A Hire?
There’s no universal revenue threshold, but I’d start seriously considering dedicated FP&A capability when several of these things are happening at once:
- leadership needs regular forecasts,
- planning has become complex,
- the CFO or Controller is overloaded,
- management needs scenario analysis,
- cash visibility matters more,
- multiple departments need financial support,
- the company is scaling quickly,
- investors or a board expect stronger financial analysis,
- or important decisions require analysis nobody currently owns.
Notice that I said capability, not necessarily employee.
That’s intentional.
The question is:
What does the business need Finance to do that Finance cannot reliably do today?
Answer that first.
The org chart can wait.
What Should FP&A Build First?
If a company is establishing FP&A for the first time, I wouldn’t begin by producing more reports.
You probably already have reports.
I’d start with the recurring management questions.
What does leadership need to know every month?
What decisions keep coming up?
Where does management lack visibility?
Then build backward.
Usually that leads toward some combination of:
a reliable forecast,
management reporting,
variance and driver analysis,
headcount planning,
cash visibility,
scenario modeling,
and regular conversations between Finance and the business.
Not everything needs to arrive on Day 1.
I’ve seen finance teams try to build the entire FP&A function at once.
New model.
New dashboards.
New planning system.
New KPIs.
New meeting cadence.
New reporting package.
Six weeks later everyone has 14 new passwords and Finance is still copying numbers into Excel.
Build the important things first.
What FP&A Should Not Become
This matters to me.
FP&A should not become the department that produces increasingly sophisticated reports nobody acts on.
It shouldn’t own every number simply because the number contains a dollar sign.
It shouldn’t become a substitute for business leaders understanding their own economics.
And it shouldn’t spend its entire existence explaining last month.
If FP&A is working well, Finance gets pulled earlier into decisions.
Before the hire.
Before the investment.
Before the pricing change.
Before the problem becomes a variance.
That’s when the function starts becoming valuable.
The Test I Would Use
If you’re wondering whether your company needs FP&A, I wouldn’t start with revenue.
I’d sit with the leadership team and listen to the questions they’re asking.
Then I’d watch what happens next.
Can Finance answer them?
How long does it take?
Does everyone trust the answer?
Can Finance explain what’s driving the result?
Can it show what happens under different assumptions?
Can management make a decision from it?
And can somebody tell us where we’re likely to land three or six months from now without the room becoming strangely quiet?
That tells me much more than company size.
The need for FP&A usually appears in the gap between having financial information and being able to use it to run the business.
Sometimes that gap is obvious.
Sometimes everything looks fine until the CFO asks one slightly different question.
Then four people start opening spreadsheets.
That’s usually my clue.
