The FP&A Gap in Middle Market PE
When a private equity firm acquires a $100-300M revenue company, the financial reporting infrastructure is almost always inadequate for institutional ownership. The company may have a competent controller who closes the books accurately, but accuracy is not the same as insight.
The typical middle market company produces financial statements 20-30 days after month-end, has no variance analysis process, does not maintain a rolling forecast, and cannot answer the question "what will next quarter look like?" with any precision.
This is not a criticism of the existing team. Pre-acquisition, there was no audience for forward-looking financial analysis. The founder or previous owner made decisions based on intuition and experience. Post-acquisition, the PE sponsor needs data-driven forecasting, variance analysis, and scenario modeling — and needs it fast.
What FP&A Actually Means for a Portco
In a PE context, FP&A is not a department. It is a capability. That capability has four components:
1. Monthly Financial Close and Reporting (Days 1-30)
The first priority is compressing the monthly close cycle from 20-30 days to 10-15 days. Speed matters because stale data drives stale decisions.
The close acceleration playbook is straightforward: identify the three longest close tasks (typically revenue recognition, inventory valuation, and intercompany eliminations), establish hard deadlines for each, and enforce them. Most close delays are caused by waiting — waiting for data, waiting for approvals, waiting for reconciliations. Eliminate the waiting by establishing a close calendar with hour-level deadlines for the first five business days.
Deliverable: A monthly financial package delivered by business day 10 that includes the income statement, balance sheet, and cash flow statement with trailing 12-month actuals and budget variance.
2. Variance Analysis (Days 30-60)
The monthly financial package is useless without variance analysis. A P&L that shows $1.2M EBITDA against a $1.5M budget tells you something is wrong. It does not tell you what, why, or whether it is fixable.
Build a three-layer variance framework:
Layer 1 — Volume vs. Price: Revenue variance decomposed into volume (units, customers, projects) and price (ASP, rate, mix). This alone answers 60% of the "what happened" question.
Layer 2 — Fixed vs. Variable: Cost variance decomposed into fixed cost overruns (headcount, facilities, contracts) and variable cost variances (materials, commissions, freight). Fixed cost variances are management decisions. Variable cost variances are operational issues.
Layer 3 — Timing vs. Permanent: Is the variance a timing difference (revenue that slipped to next month) or a permanent miss (lost customer, pricing concession)? This determines the forecast impact.
3. Rolling Forecast (Days 45-75)
Replace the annual budget with a rolling 6-quarter forecast updated monthly. The annual budget is a political document created in October and obsolete by February. The rolling forecast is an operating tool that reflects current reality.
Start simple: take the current month's actuals, apply known changes (signed contracts, headcount additions, price increases, lost customers), and project forward. Do not build a complex driver-based model in the first iteration. Build a model that is directionally correct and fast to update. Sophistication comes later.
The rolling forecast should take no more than 3 business days to update each month. If it takes longer, the model is too complex.
4. Scenario Modeling (Days 60-90)
The PE sponsor will ask: "What happens if revenue grows 5% instead of 12%?" and "What is the EBITDA impact of a 200bps gross margin compression?" FP&A needs to answer these questions in hours, not weeks.
Build three standing scenarios: base case (current forecast), downside (revenue miss + margin compression + working capital deterioration), and upside (revenue beat + operational improvement). Update them monthly alongside the rolling forecast.
Who Does This Work?
In a $100-200M revenue company, you do not need a 5-person FP&A team. You need one strong FP&A hire — typically a senior financial analyst with 5-8 years of experience, ideally with PE or consulting background — and a reporting tool that automates the data aggregation.
The controller continues to own the close and the accuracy of the books. The FP&A hire owns the analysis, the forecast, and the story the numbers tell.
If the company cannot hire immediately, engage a fractional CFO or FP&A consultant for 90 days to build the infrastructure and train the team.
The Tech Stack
Do not over-engineer the technology. For a $100-300M revenue company, the FP&A tech stack should be: the existing ERP (QuickBooks, NetSuite, Sage — whatever they have), Excel for modeling (the FP&A analyst must be an expert), and one reporting/dashboarding tool for automated monthly packages.
R8 Labs Vantage serves as the dashboarding and benchmarking layer — it ingests the financial data, computes KPIs automatically, benchmarks against peers, and surfaces alerts. This replaces the manual Excel dashboard that most FP&A teams spend 40% of their time maintaining.
Common Mistakes
Mistake 1: Building the model before fixing the data. If the chart of accounts is a mess, the general ledger has miscategorized expenses, and revenue recognition is inconsistent, the model will produce precise nonsense. Fix the data first.
Mistake 2: Over-engineering the forecast model. A 50-tab Excel model with 200 input drivers is not better than a 5-tab model with 15 drivers. It is slower, harder to maintain, more error-prone, and no more accurate.
Mistake 3: Skipping the narrative. Numbers without context are noise. Every monthly package should include a one-page narrative that answers: What happened? Why? What are we going to do about it? This is the CFO's most important deliverable.
Want automated KPI computation and peer benchmarking for your portfolio? R8 Labs Vantage computes every metric your FP&A team needs, benchmarks against industry peers, and generates alerts when something moves. Start your free trial today.