FP&A Team Structure: Who Should You Hire and When?

If you’re building an FP&A team, I have one request.

Please don’t start with the org chart.

I know it’s tempting.

CFO at the top.

VP of FP&A underneath.

Director.

Manager.

Senior Analyst.

Analyst.

Look at that. We have a department.

We haven’t figured out what any of these people are doing yet, but the boxes are beautiful.

I’d rather start somewhere considerably less exciting:

What does your company actually need FP&A to do?

Because your first FP&A hire might be an Analyst.

It might be a Director.

It might be someone part-time.

It might be a consultant.

And, depending on where your company is today, you might not need to hire anyone yet.

So before you post a job description copied from another company’s LinkedIn page, let’s figure out what problem you’re actually trying to solve.

What Does an FP&A Team Actually Do?

At its core, FP&A helps management understand where the business is going and make better financial decisions along the way.

That usually includes some combination of:

• budgeting,
• forecasting,
• financial modeling,
• variance analysis,
• management reporting,
• scenario planning,
• headcount planning,
• cash visibility,
• business partnering,
• and decision support.

But your company may not need all of those things at the same level today.

That’s important.

A $25 million company building its first real forecast has a very different FP&A problem from a $300 million company with five business units, international operations and a board that would like next year’s outlook by Thursday.

Same letters.

Different job.

Start With the Work, Not the Titles

If I were sitting with you trying to design your FP&A team, I wouldn’t begin by asking how many analysts you want.

I’d ask you to show me the work.

What does Finance produce every month?

Who builds the forecast?

Who owns the budget?

Who supports department leaders?

Who maintains the financial model?

Who analyzes performance?

Who prepares board materials?

Who handles headcount planning?

Who answers the CFO’s random questions at 4:47 on a Friday?

That last category deserves its own headcount model.

Now tell me where the pain is.

Maybe the CFO is doing all of it.

Maybe the Controller is doing half of it after close.

Maybe you already have an Analyst who spends 80% of the month manually updating reports.

Maybe nobody owns it.

That’s where your FP&A team structure starts.

Not with a title.

With the work that needs an owner.

When Do You Need Your First FP&A Hire?

There’s no magical revenue number.

I know that’s an annoying answer.

It would be much easier if I could tell you:

At $27.4 million in revenue, please hire an FP&A Manager.

Finance would love that kind of precision.

Unfortunately, companies refuse to grow in standardized ways.

Instead, I’d watch for a few things happening at the same time.

Your CFO or Controller is spending significant time forecasting and analyzing the business.

Management wants more forward-looking information.

Budgeting has become painful.

Leadership regularly asks questions Finance can’t answer quickly.

Headcount and spending need more active planning.

Cash or capital allocation requires more attention.

Board or investor expectations are increasing.

The company is becoming more complicated.

If you’re nodding through several of those, you’re probably getting close.

And here’s another test.

Ask your CFO what they would stop doing if somebody competent took FP&A off their plate.

If they answer immediately and then continue talking for 20 minutes, I have some news for you.

Should Your First FP&A Hire Be an Analyst?

Sometimes.

But I think companies default to this too quickly.

An Analyst is less expensive.

The title feels appropriate for a first hire.

There’s plenty of spreadsheet work.

Makes sense.

Except there’s a problem.

If your FP&A function doesn’t exist yet, who is going to design it?

Who decides what the forecast should look like?

Who determines the planning cadence?

Who decides which metrics matter?

Who builds relationships with department leaders?

Who challenges assumptions?

Who decides what Finance should stop doing?

A talented Analyst can do a lot.

But if the company needs someone to create the function, you’re asking for a different level of experience.

You may hire an inexpensive Analyst and discover that your CFO is still designing FP&A.

Now the CFO has an Analyst to manage while continuing to do the work you were trying to remove.

Not quite the victory we were looking for.

When an Analyst Does Make Sense

Let’s say the CFO or another senior finance leader already knows exactly what FP&A needs to look like.

The processes exist.

The models exist.

The cadence is established.

The problem is capacity.

Now an Analyst can make a lot of sense.

They might own:

reporting,

variance analysis,

forecast updates,

data preparation,

model maintenance,

department support,

and recurring analysis.

They’re operating inside an existing system rather than inventing one.

That’s a very different job.

So if you’re considering an Analyst, ask yourself:

Do we need someone to execute FP&A, or someone to design FP&A?

That question will save you from several months of frustration.

Possibly theirs too.

When Should You Hire an FP&A Manager?

A Manager starts making sense when you need someone who can own meaningful processes with less supervision.

Maybe they run the forecast.

Own the annual plan.

Partner with several departments.

Build scenarios.

Improve reporting.

Manage an Analyst.

Help the CFO prepare for executive meetings.

At this level, I’m looking for someone who can do more than produce the analysis.

They should be able to sit with an operating leader and understand what’s actually happening.

That’s harder than it sounds.

You can teach someone the mechanics of a variance bridge.

Teaching them how to sit with a Sales leader who insists every deal is closing this quarter and politely ask, “All of them?” is a different skill.

FP&A starts becoming much more valuable when it can operate in both worlds.

Finance and the business.

When Do You Need a Director or Head of FP&A?

Now we’re talking about leadership.

A Director or Head of FP&A makes sense when the company needs someone to own the planning function, not merely participate in it.

This person may be responsible for:

the overall forecasting process,

annual planning,

long-range planning,

management reporting,

business partnering,

scenario analysis,

board support,

team development,

and improving the FP&A operating model itself.

They should also be capable of walking into a room with senior leadership and having an opinion.

I care about that.

If the model says one thing and the business conversation suggests another, I want an FP&A leader willing to investigate the difference.

Not just refresh the workbook.

If your CFO needs someone who can take FP&A and say, “I’ve got this,” you’re probably moving into Director or Head-of-FP&A territory.

What About a VP of FP&A?

As the company becomes larger and more complex, FP&A often starts splitting into multiple layers.

Corporate FP&A.

Business-unit FP&A.

Commercial Finance.

Strategic Finance.

Regional teams.

Specialized planning groups.

Now you may need a VP of FP&A who is designing how the entire planning organization works.

At that point, the job becomes less about personally building every model and more about creating consistency across the company.

How does forecasting work?

What gets standardized?

What stays local?

How do business units communicate with Corporate?

How are assumptions challenged?

What does leadership see?

How are FP&A people developed?

And perhaps most importantly:

How do we prevent 14 different teams from inventing 14 slightly different versions of the truth?

Growth is exciting.

It also produces folders.

Corporate FP&A vs. Business-Unit FP&A

Once your company becomes large enough, this distinction becomes important.

Corporate FP&A usually focuses on the consolidated company view.

That might include:

company-wide forecasting,

long-range planning,

executive reporting,

board reporting,

capital allocation,

consolidated scenarios,

and overall performance.

Business-unit FP&A sits closer to individual functions, products, regions or operating units.

Those teams understand the details.

They know why a particular customer changed.

Why hiring is behind.

Why a product margin moved.

Why Operations needs another $2 million.

Ideally, these groups work together.

Corporate sees across the company.

Business-unit FP&A sees deeper into individual areas.

When they don’t work together, you get one of my favorite corporate activities:

reconciling Finance with Finance.

If you’ve ever spent a meeting figuring out why two FP&A teams have different revenue numbers, you know exactly what I mean.

Nobody leaves that meeting feeling like we’ve advanced civilization.

Where Should FP&A Report?

Usually to the CFO or another senior finance leader.

But I care less about the box on the org chart than FP&A’s access to the business.

You can put FP&A directly under the CFO and still have a team that rarely talks to anyone outside Finance.

That’s not much of a win.

Good FP&A needs relationships with:

Sales,

Marketing,

Operations,

HR,

Product,

Customer Success,

and whoever else actually drives the economics of the company.

If your FP&A team only sees information after Accounting closes the month, they’re operating too late.

I want them hearing what’s changing before it becomes a variance.

That requires relationships.

And yes, occasionally meetings.

I’m sorry.

I couldn’t eliminate all of them.

Should Accounting and FP&A Be Separate?

Eventually, usually yes.

But early on, they often overlap.

That’s normal.

A smaller company may have a CFO and Controller handling both historical reporting and forward-looking planning.

As complexity increases, specialization starts making sense.

Accounting asks:

What happened, and is it recorded correctly?

FP&A asks:

What does it mean, what happens next, and what should we do?

You need both.

And neither works particularly well when the underlying Accounting is unreliable.

If actuals aren’t trustworthy, FP&A spends its time arguing with the starting point.

You don’t want highly sophisticated scenario planning built on numbers everyone quietly suspects are wrong.

That’s a very expensive way to become confused.

How Big Should an FP&A Team Be?

I wouldn’t use a universal ratio.

Revenue matters.

Employee count matters.

Industry matters.

Business complexity matters.

Number of entities matters.

Geographic footprint matters.

Systems matter.

Reporting requirements matter.

How much support business leaders expect matters.

A highly automated $200 million company might need fewer FP&A resources than a messy $80 million company operating across several business models.

So instead of asking:

How many FP&A people should a $100 million company have?

I’d ask:

What recurring FP&A work exists, how complicated is it, and what level of support does management expect?

Then calculate capacity.

This is less satisfying than a benchmark.

It’s also more likely to give you the right answer.

A Simple FP&A Team Structure as You Grow

I don’t want you treating this as a mandatory progression, but here’s a useful way to think about it.

Stage 1: CFO + Accounting

Early in the company’s life, the CFO and Controller may handle planning and forecasting themselves.

That’s perfectly reasonable if the work is manageable.

Don’t create an FP&A department because you feel like a grown-up company should have one.

There are easier ways to buy matching shirts.

Stage 2: First Dedicated FP&A Capability

As forward-looking work grows, add dedicated FP&A support.

This could be:

an Analyst,

a Manager,

a senior FP&A leader,

or outside FP&A support.

The right choice depends on whether you primarily need execution, design or both.

Stage 3: FP&A Leader + Analyst Support

As complexity increases, you may need someone owning the function with one or more people supporting recurring analysis and planning.

Now FP&A starts becoming a real operating capability rather than an extra responsibility.

Stage 4: Corporate + Business Partnering

As the company grows further, FP&A may split between central planning and people embedded closer to business units or functions.

Now specialization becomes useful.

Stage 5: Scaled FP&A Organization

Large organizations may have multiple layers, specialized teams, regional FP&A, commercial finance and centers of excellence.

At this point, your problem is no longer whether you need FP&A.

Your problem may be getting all of FP&A to use the same definition of EBITDA.

Every stage has its joys.

When Does Consulting or Fractional FP&A Make More Sense?

Let’s say you know you need FP&A.

But you’re not sure what the permanent team should look like yet.

This is where consulting or fractional FP&A can make sense.

Maybe you need to:

build the first forecast,

design the planning process,

create financial models,

establish management reporting,

build a 13-week cash flow forecast,

clean up the annual planning process,

or determine what permanent roles you actually need.

In that situation, hiring immediately can be backwards.

You may not yet know what you’re hiring for.

An experienced FP&A consultant can help build the function, establish the processes and identify the ongoing workload.

Then you hire around something real.

I like that sequence because it reduces the odds of hiring a person into a job everyone plans to define later.

I’ve had jobs like that.

“There’s a lot to do. You’ll figure it out.”

Very exciting sentence during an interview.

Don’t Hire Around Bad Processes

This is one of the biggest mistakes I see.

Finance is overwhelmed.

The forecast takes forever.

Reporting is manual.

Planning is painful.

So the answer becomes:

We need another person.

Maybe.

But before adding headcount, I’d look at why the work requires so much time.

Are people manually moving data between systems?

Are there duplicate reports?

Are processes unnecessarily detailed?

Does Finance maintain work nobody uses?

Are there five versions of the same analysis?

Is someone spending eight hours doing something that could take 20 minutes?

If you hire into a bad process, you’ve made the bad process more expensive.

Sometimes headcount is absolutely the answer.

Sometimes the answer is deleting a report.

Personally, I enjoy the second option more.

Nobody has to onboard a report.

Hire for Curiosity, Not Just Excel

Technical skills matter in FP&A.

You need people who understand financial statements.

Forecasting.

Modeling.

Analysis.

Excel.

Planning systems.

But when I think about the best FP&A people I’ve worked with, technical skill isn’t the first thing I remember.

They were curious.

Something didn’t make sense and they couldn’t leave it alone.

Revenue moved.

Why?

Margins changed.

Why?

Hiring slowed.

Why?

A business leader gave them an explanation.

Maybe.

But why?

You know the person.

They’re slightly annoying in the most useful possible way.

Those people tend to learn the business quickly because they aren’t satisfied with knowing what happened.

They want to understand what caused it.

Software can make FP&A faster.

AI will automate more of the mechanics.

I’m still hiring the person who notices something strange and asks another question.

Don’t Build a Team That Only Produces Finance

Here’s another thing I’d watch.

Your FP&A team can become technically excellent and still be too far away from the business.

Beautiful models.

Accurate reports.

Clean decks.

Nobody in Operations calls them.

Sales doesn’t involve them.

Department leaders see Finance once a month.

That’s not the FP&A function I’d want.

I want FP&A people who know the business well enough that operating leaders call them before making a decision.

Not afterward when Finance asks why the variance is $600,000.

That relationship takes time.

It also requires FP&A people who can communicate without turning every conversation into a finance lecture.

If you’re reading this as an FP&A person, please know that I say that with affection.

We can be a lot.

What I’d Do Before Hiring Anyone

If you’re considering your first or next FP&A hire, here’s the exercise I’d do.

Get a blank page.

Not an org chart.

Write down every recurring piece of FP&A work you need done.

Forecasting.

Budgeting.

Reporting.

Analysis.

Business partnering.

Headcount planning.

Cash.

Scenarios.

Board support.

Whatever belongs on your list.

Now put the current owner beside each one.

Then estimate how much time it takes.

Then ask:

Which work isn’t getting done?

Which work is being done by someone too senior?

Which work shouldn’t exist at all?

Which work needs more experienced ownership?

Which work could be automated?

Which work requires a permanent employee?

Now you’re designing a team.

And you’ll probably find the answer isn’t quite the org chart you originally had in mind.

That’s a good thing.

The Best FP&A Team Is Not Necessarily the Biggest

I don’t get particularly excited by large Finance teams.

I get excited when a Finance team can answer important questions quickly.

When the forecast works.

When management trusts the numbers.

When Finance understands the business.

When department leaders involve FP&A early.

When the CFO isn’t rebuilding models at night.

When an Analyst has time to investigate something instead of spending Tuesday moving numbers between files.

That’s what I want.

If five people can do that, great.

If you need fifteen, hire fifteen.

If you can do it with three and good systems, I am not going to recommend twelve because a benchmark says you should.

The org chart is not the product.

Better decisions are.

So if you’re trying to figure out your FP&A team structure, don’t begin with how many people companies your size usually employ.

Start with the work.

Then the decisions.

Then the capability.

Then the people.

In that order.

The boxes can wait.

They’ve never seemed particularly impatient to me.