Budget season for most PE-backed companies run from late October into December. In house leadership sends over a 2027 plan, the deal team has a week or two to react, and the board approves a number in January that everyone will probably re-forecast by April.

A portfolio company budget review is the window where a sponsor can still change the plan before it becomes the number everyone is measured against. That window usually gets less time than it deserves, because it lands on top of year-end close, add-on activity, and holiday schedules.

We’re going to cover how teams can pressure-test portfolio company budgets before they go to the board: what to ask for, where plans usually break, and how to turn the approved budget into something the company can manage against every month.

Start with how the budget was built

Before looking at a single number, ask leadership how the plan was put together. The answer tells you whether the review should focus on the inputs or outputs.

Most budgets we see were built in one of these ways:

1. Top-down targets. The revenue and EBITDA numbers came from the investment thesis or the last board conversation, and the line items were filled in to reach them.
2. Prior year plus a percentage. Each line is this year’s expected actual with a growth rate applied. It’s fast to produce and hard to manage against, because nobody can explain why a given line should move.
3. Driver-based. Revenue and major costs are built from operating inputs: customers, pricing, headcount, utilization, units, and conversion rates.

A driver-based plan is the easiest to review because every number traces back to an assumption you can test. If a portfolio company is still budgeting the other two ways, the first goal of the review is to name the four-to-six drivers that explain most of the P&L and rebuild the plan around those.

Ask for the bridge before the detail

A budget package with 40 tabs gives the deal team a lot to read and very little to react to. Before the detail, ask for a bridge from 2026 expected actuals to the 2027 plan, for both revenue and EBITDA.

The bridge should show each major movement as its own line: price increases, volume growth, new products, headcount adds, cost savings, and any add-on contribution. Each line should have an owner and a 1-sentence explanation.

A good bridge separates organic growth from everything else, and it shows the sponsor which three or four assumptions carry the plan. Those assumptions are where the rest of the review should spend its time.

Test the revenue drivers

Revenue is where most budgets are weakest, because it depends on the people who sell for a living estimating how much they’ll sell.

Questions worth asking:

1. Coverage. How much of 2027 revenue is already contracted or recurring, and how much depends on new bookings? For the new bookings, what does the current pipeline look like against that number, and what conversion rate does the plan assume compared to the last four quarters?
2. Price and volume. If the plan includes a price increase, has it been tested with customers, and does the churn assumption reflect it?
3. Ramp time. If growth depends on new sales hires, does the plan account for the months it takes a new rep to reach full productivity? A rep hired in March is unlikely to close a full annual quota in 2027.
4. Timing. Is revenue spread evenly across 12 months, or does it follow the company’s actual seasonality?

The annual revenue number is usually defensible. The monthly phasing often isn’t. Phasing affects every board meeting in 2027, since actuals will be compared to budget each month and the early months set the tone for the rest of the year.

Check headcount against the work

Headcount is usually the largest cost line in a services or software business, and one of the easiest to get wrong in either direction.

Ask for a headcount roster by month: every current role, every planned hire, start dates, fully loaded cost, and the reason for each new role. Then check three things.

First, are the hire dates realistic? A plan that adds 12 people in Q1 when the company hired 8 people in all of 2026 will probably slip. That flattens EBITDA early in the year and creates a cost spike later.

Second, is the fully loaded cost complete? Benefits, payroll taxes, recruiting fees, equipment, and software seats often add 20% to 35% on top of base salary. A budget built on base salary alone understates cost.

Third, does the headcount support the revenue plan? If revenue grows 25% and delivery headcount grows 5%, the plan needs a clear explanation of where the extra capacity comes from.

Look at cash separately from EBITDA

A budget can hit its EBITDA target and still put pressure on cash. Sponsors care about both, and many budget packages only show the first.

Ask for a monthly cash flow view next to the P&L that includes:

• Working capital assumptions: days sales outstanding, days payable outstanding, and inventory turns where relevant
• Capital expenditures and capitalized software
• Debt service, including interest and scheduled liquidation
• Covenant calculations by quarter, with headroom shown
• Earnout or deferred consideration payments from prior acquisitions

The covenant view is the one we push for most. If the plan shows only 10% headroom against a leverage covenant in Q2, the sponsor should know that in November, when there is still time to adjust the plan.

Run the downside before the board asks

Every board will ask what happens if revenue comes in light, and the meeting goes better when the answer is already prepared.

A useful set of cases for most portfolio companies, all built off the same driver model:

• Base case: the plan as presented
• Downside: the two-or-three least certain revenue drivers moved by a realistic amount, for example new bookings at 80% of plan and a one-quarter delay on the price increase
• Downside with response: the same downside, plus the cost actions leadership would take and the date they would take them

The third case gives the sponsor the most confidence. It shows leadership has thought about which costs are variable, which hires could wait, and how quickly they could act. It also gives the board an agreed trigger point, so a weak Q1 leads to a response everyone already discussed.

Make budgets comparable across the portfolio

For sponsors with several portfolio companies, budget season is also a chance to standardize what comes in. When every company submits a plan in its own format with its own KPI definitions, the deal team spends its first few days reformatting before it can compare anything.

Each company can keep its own internal model and also fill in a short, shared summary that covers:

• A revenue and EBITDA bridge from current year to budget
• Five to eight KPIs with the same definitions across the portfolio
• Monthly P&L, cash flow, and covenant view
• Headcount by function, by month
• The base, downside, and downside-with-response cases

With the same summary from every company, the sponsor can see patterns: which businesses are planning aggressive hiring, which are relying on price, and where the same optimistic assumption shows in three different plans.

Turn the budget into a monthly tool

The review should end with a plan the company can manage against every month. Before approval, agree on:

• Which five-to-eight metrics will be reported monthly against budget
• What variance triggers a written explanation (many use 5% or a fixed dollar amount)
• When the first formal reforecast will happen, usually after Q1 close
• Who owns each major driver

When those decisions are made up front, the first board meeting of 2027 is a review of results against a plan everyone understood. When they’re left open, that meeting tends to be spent debating what the budget meant.

How Chelsea Street helps during budget season

Our team will work with portfolio company finance teams and sponsors year-round and through planning season. Depending on the company, that could mean building a driver-based model from scratch, preparing the bridge and downside cases, setting up monthly reporting against the approved plan, or giving the budget a second review before it goes to the board and so much more. Every engagement is shaped around what the company and its sponsor need.

FAQs

How long should a portfolio company budget review take?

For a single company with a driver-based model, the core review takes one-two weeks: a few days on the bridge and drivers, a working session with management, and a few days for revisions. A company building a driver-based plan for the first time needs 3 to 5 weeks, which is why starting in October helps.

Should the sponsor build the budget or review it?

Management should own it. They’re the ones who will run the business against it, and plans built by the sponsor tend to lose ownership by the second quarter. The sponsor’s role is to set the format, test the assumptions, and agree on targets. When the finance team doesn’t have the capacity to build a solid plan, fractional support adds hands while keeping ownership with management.

What if management pushes back on a detailed review?

Pushback usually comes from capacity, since year-end close and budgeting land at the same time. Asking for the bridge and the 4 to 6 main drivers first, before the full model, keeps the request focused on the assumptions that carry the plan. Most CFOs respond well to that.

How should a planned add-on acquisition show up in the budget?

Keep it separate. Budget the existing business on its own, then show the add-on as its own layer with revenue, cost, and integration expense lines. If the deal hasn’t closed, include it as a scenario with an expected close date. Boards and lenders want to track organic performance, and this keeps it visible.

How often should the budget be reforecast?

Most PE-backed companies reforecast quarterly, with the first formal update after Q1 close. Companies with volatile revenue or an active acquisition program often move to a rolling monthly forecast. The original budget should stay fixed as the board-approved baseline, with the current forecast shown next to it.

What’s the most common budget mistake?

Monthly phasing that doesn’t match how the business performs. The annual total is usually reasonable. When revenue is spread evenly across 12 months in a seasonal business, the company looks like it’s missing plan in its slow months and beating it in its busy ones. Phasing the budget off the last 2 years of monthly actuals fixes most of this.