FP&A Maturity Model: Where Does Your Team Stand?
By Newtown Analytics · · 9 min read
For cfos & finance leaders
An FP&A maturity model describes how finance planning capability develops, from ad hoc spreadsheets to an integrated, forward-looking function that shapes decisions. It is useful for two reasons: it helps you see honestly where your team stands, and it shows the next step, which is almost never "buy the most advanced tool". This guide defines five levels across six dimensions (planning, forecasting, analysis, data and tools, people, and governance), provides a self-assessment scorecard with worked scoring, and lays out practical next steps for each level, including what not to attempt too early. It sits within budgeting and forecasting, follows what is FP&A, how to build an FP&A function and FP&A KPIs, and leads to fractional FP&A.
The five levels
| Level | Name | Short description |
|---|---|---|
| 1 | Reactive | Budgets are static; reporting is late; spreadsheets are personal; analysis is ad hoc |
| 2 | Defined | An annual budget and a monthly report exist; a calendar is followed; basic variance explanations |
| 3 | Managed | Rolling forecasts, driver-based models, consistent definitions, KPI reporting, scenario capability |
| 4 | Integrated | Planning linked to operations (sales, supply, HR); finance acts as business partner; forecasts measured and improved |
| 5 | Predictive | Advanced analytics, automated data flow, continuous planning, strategic scenario modeling |
Most small and mid-sized companies sit at levels 1 to 3. Level 5 is rare, and not every company needs it.
The six dimensions
1. Planning (budget and long-range plan)
| Level | Characteristics |
|---|---|
| 1 | Budget prepared by one person, not updated, or none |
| 2 | Annual budget with department inputs; fixed timeline |
| 3 | Driver-based budget; linked to strategic priorities; rolling horizon |
| 4 | Integrated with operational plans; scenario-based; headcount and capacity linked |
| 5 | Continuous planning; dynamic resource allocation |
2. Forecasting
| Level | Characteristics |
|---|---|
| 1 | Forecast equals budget, or none |
| 2 | Occasional reforecast, mostly judgmental |
| 3 | Monthly rolling forecast; statistical baseline; accuracy measured |
| 4 | Bias tracked and managed; forecast value added measured. See forecast bias in financial planning |
| 5 | Machine-assisted forecasts with human overlay; probabilistic ranges |
3. Analysis and decision support
| Level | Characteristics |
|---|---|
| 1 | Totals reported; little explanation |
| 2 | Variance analysis against budget |
| 3 | Driver-based variance (price, volume, mix); profitability by product or customer |
| 4 | Business cases routinely used; finance partners shape decisions |
| 5 | Predictive analytics and optimization support strategy |
4. Data and tools
| Level | Characteristics |
|---|---|
| 1 | Manual exports; multiple versions of numbers |
| 2 | Standard templates; one source for actuals |
| 3 | Structured models with checks; some automation. See financial model structure |
| 4 | Integrated data from ERP, CRM and operations; planning platform where justified |
| 5 | Automated pipelines; self-service analytics |
5. People and organization
| Level | Characteristics |
|---|---|
| 1 | No dedicated FP&A resource |
| 2 | One analyst or part-time responsibility |
| 3 | Defined roles; business partnering emerging. See FP&A roles and responsibilities |
| 4 | Embedded partners; development path; skills in modeling and communication |
| 5 | Strategic advisory capability; data science partnership |
6. Governance and process
| Level | Characteristics |
|---|---|
| 1 | No calendar; unclear ownership |
| 2 | Calendar; named budget owners |
| 3 | Standard definitions; model review; documented assumptions |
| 4 | Integrated with S&OP and strategic reviews; clear decision rights |
| 5 | Continuous performance management; closed loop from decisions to results |
A self-assessment scorecard
For each dimension, pick the level whose description best fits you today (be honest, and when between levels choose the lower). Then compute an average.
Worked example (hypothetical company).
| Dimension | Score (1 to 5) | Evidence |
|---|---|---|
| Planning | 2 | Annual budget with department inputs; no rolling horizon |
| Forecasting | 3 | Monthly forecast; accuracy measured, bias not yet tracked |
| Analysis | 2 | Variance analysis by total; no price-volume-mix |
| Data and tools | 1 | Manual exports; several versions of key numbers |
| People | 2 | One analyst, part-time on FP&A |
| Governance | 3 | Calendar, owners and definitions are in place |
| Total | 13 |
Average = 13 / 6 = 2.17. The company is at about level 2, with strengths in governance and forecasting and a weakness in data and tools. The score is a conversation starter, not a grade. The lowest dimension is the constraint: a forecasting capability at level 3 will struggle if the data come from manual exports at level 1.
Next steps by level
From level 1 to 2: establish the basics
- Create a one-page budget with named owners and a monthly comparison.
- Set a close and reporting calendar.
- Use one source for actuals; end the multiple versions problem.
- Build a basic cash forecast. See cash flow management.
From level 2 to 3: add forecasting and drivers
- Introduce a rolling forecast. See rolling forecast process.
- Build driver-based models for revenue and major costs. See how to forecast revenue.
- Agree on written KPI definitions. See FP&A KPIs.
- Add price-volume-mix variance analysis. See price-volume-mix analysis.
- Document models and add checks.
From level 3 to 4: integrate with the business
- Link the financial plan to the sales, operations and inventory plans through a structured process. See demand planning and inventory optimization.
- Embed finance partners with major departments.
- Track forecast accuracy and bias, and measure forecast value added.
- Introduce business case discipline for investments.
- Consider planning software if complexity requires it. See FP&A software.
From level 4 to 5: automate and extend
- Automate data flows and standard reporting.
- Add statistical or machine-assisted forecasting with a human overlay.
- Run strategic scenarios regularly.
- Use predictive analytics where there is clear value.
Why the profile matters more than the average
Two companies with similar averages can need very different actions.
| Dimension | Company X | Company Y |
|---|---|---|
| Planning | 2 | 4 |
| Forecasting | 2 | 4 |
| Analysis | 2 | 4 |
| Data and tools | 2 | 1 |
| People | 2 | 1 |
| Governance | 2 | 2 |
| Total / average | 12 / 2.00 | 16 / 2.67 |
Company X is evenly basic: it should work on all dimensions together, starting with the calendar and a single source of actuals. Company Y has strong planning, forecasting and analysis skills on top of weak data, thin staffing and loose governance. Its average looks better, but the weak dimensions will limit it: the sophisticated models depend on manual data and one overworked analyst. Its priority is data and people, not another model.
Evidence to ask for in an assessment
For each dimension, ask for evidence, not opinions.
| Dimension | Evidence to look at |
|---|---|
| Planning | The last budget file; the calendar; who contributed and how many versions existed |
| Forecasting | The last four forecasts versus actuals; accuracy and bias measures |
| Analysis | The last three management packs; did the commentary lead to actions? |
| Data and tools | How long it takes to produce the pack; how many manual steps; number of conflicting versions |
| People | Roles and time allocation; turnover; training |
| Governance | Definitions document; model reviews; change logs |
A half-day assessment workshop
- Set the scope (15 minutes): which part of the function is being assessed.
- Individual scoring (30 minutes): each participant scores the six dimensions privately.
- Compare (45 minutes): discuss differences, ask for evidence, agree on scores.
- Identify constraints (30 minutes): which dimension limits the others?
- Choose priorities (45 minutes): two or three actions for the next two quarters, with owners.
- Agree measures (15 minutes): how will you know you have moved?
Invite finance, a sales or operations leader and an executive sponsor. Outside views of finance's usefulness are often the most revealing.
What a rise in level looks like
| From | To | Visible sign |
|---|---|---|
| Manual exports | Single source of actuals | The monthly pack uses one set of numbers and nobody asks which version is right |
| Budget only | Rolling forecast | Leaders talk about where the year will land, not only where it was planned |
| Total variances | Driver-based variances | Commentary states price, volume, mix and cost causes |
| Reports | Decisions | Meetings end with actions and owners |
| One heroic analyst | Documented, reviewed models | Another person can run the model next month |
What not to attempt too early
| Temptation | Why it fails |
|---|---|
| Buying a planning platform at level 1 | Automates a process that does not exist |
| Advanced statistical forecasting without clean data | Garbage in, garbage out |
| Detailed driver models for every line | Maintenance burden outweighs value |
| Embedded business partners without foundations | Partners without reliable data lose credibility |
| Dashboards with 50 KPIs | No focus |
Setting a target level
You do not need level 5. Choose the level that matches the complexity and decisions of your business. A company with a simple model and stable operations may be well served by level 3. A company with many products, volatile demand, tight cash or multiple entities may need level 4. The cost and effort of each step should be justified by the decisions it improves.
| Company profile | Reasonable target |
|---|---|
| Small, simple, stable | Level 2 to 3 |
| Growing, multiple products or channels | Level 3 to 4 |
| Complex, many entities, volatile demand, external financing | Level 4, selected level 5 capabilities |
A 12-month improvement plan (example)
| Quarter | Focus | Measure |
|---|---|---|
| Q1 | Data: single source for actuals; written definitions | Zero conflicting versions in the monthly pack |
| Q2 | Analysis: price-volume-mix and profitability by product | Variance report with drivers |
| Q3 | Forecasting: bias tracking; statistical baseline | Bias within a range you set; accuracy vs. naive |
| Q4 | Process: link to operations planning; review tools | Planning calendar integrated with the monthly sales and operations meeting |
Reassess the scorecard every six to twelve months.
Link to profit
Improved FP&A matters if it improves decisions on pricing, product mix, cost and cash. Make sure each investment in capability is tied to a decision. For product-level economics, see unit economics.
FAQs
What is an FP&A maturity model?
A framework that describes stages of FP&A capability, typically from reactive spreadsheets to integrated, predictive planning, across dimensions such as planning, forecasting, analysis, data, people and governance.
How do I assess my FP&A maturity?
Score each dimension against the level descriptions, compare the lowest and highest scores, and discuss the evidence with your team.
What maturity level do I need?
The level that matches the complexity of your business and the decisions you need to support. Most companies do not need the top level.
Is FP&A software required to reach higher maturity?
No. Software can help at higher levels, but process, data and skills matter more.
How often should I reassess?
Every six to twelve months.
Keep reading
- Complete guide: Budgeting and Forecasting: The Complete Guide for Finance Leaders
- Fractional FP&A: When Outsourcing Finance Planning Makes Sense
- What Is FP&A? A Guide for Growing Companies
- FP&A vs. Accounting: Roles, Outputs, and Where They Overlap
- Related topic: Unit Economics: The Complete Guide to Profitable Growth
This article is for general information. It is not accounting, tax, legal or investment advice, and examples use illustrative numbers rather than client data. Confirm decisions that carry financial or legal consequences with a qualified professional.