Key takeaways
- The AOP should be built bottom-up (from operational drivers) and reconciled top-down (against strategic targets); plans built top-down only produce targets without credibility; plans built bottom-up only may understate what the business is capable of.
- Revenue build is the most important and most frequently underdeveloped AOP component, a credible revenue plan accounts for existing customer growth, new customer acquisition (by sales rep and pipeline), and churn, not just a percentage applied to prior year revenue.
- The AOP process should begin 10-12 weeks before fiscal year-end and involve department heads, not just finance; plans built by finance in isolation are not owned by operators and will not be executed.
- A good AOP becomes irrelevant without a monthly review cadence that compares actuals to plan and updates the forward forecast; the AOP is the baseline, not the destination.
In this article
- What makes an operating plan useful vs. performative
- The revenue build: the most important and most underdeveloped section
- Headcount plan: the AOP component that most affects EBITDA
- AOP build sequence: from strategic objectives to board approval
- Variance framework: designing the AOP for automatic variance analysis
- The AOP as a management accountability tool
- Common AOP design mistakes that produce plans nobody uses
Operating diagnosis
What makes an operating plan useful vs. performative
Operator Checklist
- Name the metric, process, or decision this issue affects.
- Assign a single owner with authority to change the process.
- Pull the last 12-24 months of data and identify the pattern, not just the latest month.
- Choose one corrective action that can be tested in the next 30 days.
- Review the result in the next management cadence and document the decision.
Most middle market companies produce an annual budget. Far fewer produce a genuine operating plan. The difference: a budget is a financial forecast; an operating plan is a financial forecast tied to specific operational decisions about headcount, capital deployment, sales coverage, and operational investments. The monthly management reporting package guide explains how the AOP baseline feeds into the monthly actual vs. plan variance reporting that PE sponsors expect.
The AOP process can feel like busywork for founders who have run their business on intuition for years, and they already know what they are going to do next year. A budget built in November without connecting it to specific operational decisions faces a structural problem: a plan not owned by the operators who must execute it rarely survives contact with February. By then, it's a number in a spreadsheet that nobody references.
A budget answers: "What will our P&L look like next year?" An operating plan answers: "What decisions are we making about headcount, spending, and growth investment, and what financial outcome do those decisions produce?"
10-12 weeks
recommended AOP process start time before fiscal year-end
3-5 iterations
typical number of AOP revisions between first draft and board approval
Q3
when most PE-backed companies begin their next-year AOP process (September-October)
The revenue build: the most important and most underdeveloped section
Revenue forecasting is where most AOPs fail. The typical approach, take last year's revenue, add a growth percentage, and call it a plan, produces a number without a mechanism. If you cannot explain where every dollar of planned revenue is coming from, the forecast is not a plan. The revenue forecasting accuracy guide covers the methodology for building a bottoms-up revenue forecast that holds up to buyer scrutiny.
A credible revenue build has four components: existing customer retention and growth (what is your renewal rate, what are average expansion rates per customer, what customers are at-risk), new customer acquisition (how many new customers will the sales team close, at what average contract value, from what pipeline), pricing changes (are you implementing any price increases, and what is the assumed impact), and product mix shifts (are any products or services growing faster or slower than average).
Start with existing revenue
Map every current customer's renewal date, renewal probability, and expected contract value at renewal. Sum to get the retained revenue base.
Add expansion
For customers with multi-product or multi-site potential, model the expansion opportunities. Use historical expansion rates as a baseline.
Model new customer acquisition
Work with the sales leader to build a bottoms-up new logo forecast by sales rep, based on pipeline and historical close rates.
Apply pricing assumptions
Overlay any planned price increases on the retained base.
Stress-test the result
Apply a 10-15% downside to the new logo forecast, this is almost always the highest-variance component.
Headcount plan: the AOP component that most affects EBITDA
In most middle market service, software, and professional services businesses, headcount is 40-65% of total costs. The headcount plan, who is hired, when, in what role, and at what cost, is therefore the most impactful cost decision in the AOP.
A credible headcount plan includes: current headcount by department, planned new hires by role (with start dates and annualized cost), planned departures (voluntary attrition assumption), and a reconciliation showing how headcount changes drive cost changes in the P&L.
The most common headcount plan error: planning all new hires for Q1 when they realistically will not be hired until Q2 or Q3. This overstates costs in Q1 and understates them later, producing variance that has nothing to do with business performance. Plan new hires conservatively by timing, and variance analysis will be cleaner throughout the year.
Companies with integrated headcount plans (linked HR and finance data, updated monthly) achieve 30-40% higher accuracy on total cost forecasts vs. companies that plan headcount and costs separately.
PE-backed companies with a formal AOP process approved by the board before fiscal year-start have 25% higher on-plan achievement rates than companies operating without a formally approved plan.
10–12 weeks
recommended start time before fiscal year-end
25% higher
on-plan achievement with a formally approved AOP vs. none
Q1 hires
the most common timing error that produces artificial budget variance throughout the year
40–65%
of total costs that headcount represents in most middle market service businesses
The AOP is not a finance exercise. It is a management alignment exercise that happens to produce financial outputs. If department heads did not own their portion of the build, they will not feel accountable to the outputs. The CFO can build a technically perfect plan in isolation, but if operations does not own the headcount assumptions and sales does not own the revenue build, the plan will be ignored by February.
Build the revenue line by naming every customer and every dollar.
A revenue plan that cannot identify where specific growth is coming from is not a plan.
It is a target. Targets without mechanisms are wishes.
Operating workflow scan
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →AOP build sequence: from strategic objectives to board approval
Step 1: Set strategic objectives
Start with 3–5 strategic objectives for the year, and these are qualitative directional statements (e.g., "expand into the Southeast market," "improve gross margin by 200 bps," "reduce customer churn to below 5%"). Every financial target in the AOP should trace to one of these.
Step 2: Translate to financial targets
Convert each strategic objective into measurable financial targets: revenue growth rate, EBITDA margin, cash conversion, capital expenditure. These are the top-down guardrails.
Step 3: Build departmental plans bottom-up
Each department head submits a resource request (headcount, spending) and output commitments (revenue, cost savings, KPIs). This is the bottom-up input. It will not match the top-down targets, and that tension is intentional.
Step 4: Reconcile top-down with bottom-up
The CFO and CEO work through the gap between what the strategy requires and what departments say they can deliver. Prioritization decisions happen here. This is the most important conversation in the AOP process.
Step 5: Board approval by December 15
Submit the final AOP for board approval no later than December 15 for a January 1 fiscal year start. The board ratification creates accountability, the management team is now committed to a board-approved plan, not just an internal target.
The tension between top-down targets and bottom-up requests is not a problem to be eliminated, and it is the mechanism by which prioritization happens. If the bottom-up requests sum to $3M in spending for $2M in revenue growth, and the top-down target is $500K in EBITDA improvement, the reconciliation conversation forces management to choose which investments deliver the best return. That conversation is the real value of the AOP process.
Variance framework: designing the AOP for automatic variance analysis
The most powerful feature of a well-designed AOP is automatic variance decomposition, the ability to explain, at month-end, exactly why results differed from plan without rebuilding the analysis from scratch.
The key design principle: budget every line item with its driver assumption explicit. Do not budget "revenue: $2,880,000." Budget "revenue: 240 units × $12,000 ASP." When actuals come in, the variance decomposes automatically: if you sold 220 units at $13,000, you have a volume variance of −$240,000 (−20 units × $12,000) and a price variance of +$220,000 (+$1,000 ASP × 220 units). The net variance is −$20,000, but now you know it came from volume, not price.
Variance Decomposition Example
Scroll to see more →
The variance framework forces a different conversation at the monthly board meeting.
Instead of "we missed revenue by $20,000 because the market was soft," you have "we missed volume by 20 units (8%) but held ASP $1,000 above budget.
The volume miss was concentrated in the Northeast territory. Here is what we are doing about it." That is a management team running a business, not explaining results.
The AOP as a management accountability tool
An AOP that is not linked to individual accountability is a planning exercise, not a management system. The link between AOP targets and individual compensation is what converts planning rigor into execution discipline.
AOP-to-Compensation Linkage Framework
Mid-Year AOP Review: Reforecast vs. Reset
When the AOP becomes disconnected from reality by Q3, operators face a choice: continue managing to a plan that everyone knows is wrong (which destroys credibility and decision quality), or formally reset with board approval (which is uncomfortable but maintains planning discipline). The right answer is always the reset. A management team that manages to a known-wrong plan while privately running a parallel forecast is the worst outcome, and it tells the board nothing useful and signals that planning is performative rather than functional.
Common AOP design mistakes that produce plans nobody uses
Common AOP Mistakes
A PE sponsor who does not see a board-approved AOP by the start of the fiscal year will begin underwriting management credibility risk. At 7x EBITDA, the sponsor paid $X for a management team that can execute a disciplined plan. An AOP that does not exist, or is not board-ratified, or is not referenced in monthly reporting, signals that management's planning discipline does not match the price the sponsor paid. Build the plan. Get it approved. Report against it. Every month.
What PE sponsors actually use the AOP for: sponsors compare your actual results to the AOP to assess management's ability to forecast accurately. A management team that consistently comes within 5–10% of plan, even in months where it misses, which is demonstrating planning rigor. A management team that is 30% off plan every quarter signals either dishonest planning or lack of business visibility. Both are management credibility concerns that affect add-on approval speed and exit timing.
Frequently asked questions
What is the first practical step?
Start by defining the metric or process owner and pulling the last 12-24 months of evidence. Most operating issues look different once the pattern is visible over time instead of judged from the most recent month.
How does this affect valuation or buyer confidence?
Buyers value repeatable management discipline because it reduces post-close uncertainty. A documented process, named owner, and consistent review cadence make the result transferable rather than founder-dependent.
What is the most common mistake?
The common mistake is treating the issue as a one-time cleanup project. The value comes when the fix becomes part of the recurring operating cadence and management reviews it consistently.
Work with Glacier Lake Partners
Build an annual operating planning process for your business
We help management teams design AOP processes that connect strategy to financial targets and produce plans that management actually uses to run the business.
Start a Conversation →Operating workflow scan
Find the reporting or execution workflow worth automating first.
Turn the issue in this article into a ranked AI workflow roadmap with readiness gaps and estimated time savings.
Find the first workflow →Research sources
Disclaimer: Financial figures and case-study details in this article are anonymized, composite, or representative examples based on middle market operating situations, and are not guarantees of outcome. Statistical references are drawn from cited third-party research; individual transaction and operational results vary based on business characteristics, market conditions, and deal structure. This content is for informational purposes only and does not constitute legal, financial, or investment advice. Consult qualified advisors for guidance specific to your situation.
Explore adjacent topics
