Annual Operating Plan: How to Build One That Survives the Year

An annual operating plan (AOP) is a company's plan for the next twelve months. It turns strategy into targets, a budget, a hiring plan and a cash forecast, month by month, and it sets the numbers that performance is measured against. A good AOP answers three questions before the year starts: what the company will achieve, what it will spend to get there, and how much cash will be left.

For most companies, the AOP is also the one document the board, the leadership team and the finance function all agree on. It's the reference point for every budget-versus-actual review, hiring decision and reforecast during the year.

Building one takes time. In the Association for Financial Professionals' 2026 benchmarking survey of 332 finance professionals, the average budgeting cycle took nearly nine weeks, unchanged over three years.

What is an annual operating plan?

An annual operating plan sits between long-term strategy and day-to-day management. It's more detailed than a strategic plan and broader than a budget.

The budget is part of the AOP, not a substitute for it. A budget says what each team can spend. An AOP says what that spending is supposed to produce, and what happens to cash if it doesn't.

In finance and FP&A, "AOP" almost always means annual operating plan.

What goes into an annual operating plan

A complete AOP has seven parts:

1. Targets. The few numbers the year is judged on, such as ending ARR or revenue, gross margin, EBITDA or burn, and cash at year end.
2. A revenue plan built from drivers. New customers or new ARR by month, churn, pricing and expansion, rather than a single growth percentage.
3. A headcount plan. Every planned hire, by role, team and start month, with fully loaded cost.
4. An operating budget. Planned revenue and all operating expenses by department, including payroll, plus non-headcount lines such as software, marketing programs, rent and professional fees.
5. Capital spending and major initiatives, each with an owner and an expected return. Larger projects should clear the company's hurdle rate.
6. A cash forecast and runway. Monthly cash, the lowest point in the year, and months of runway at year end.
7. Scenarios and triggers. A downside case, and the specific actions the company will take if it starts to happen.

The first six are standard. The seventh is where most plans are weakest, and the worked example below shows why it matters.

These parts should all come from one driver-based 3-statement model, so that a change to hiring or pricing flows through to the income statement, balance sheet and cash automatically.

Worked example: an annual operating plan for a $4M ARR company

A B2B software company starts the year with $4.0 million of ARR, $6.0 million of cash and 30 employees. Its plan:

• New ARR: $450k in Q1, rising by $50k a quarter to $600k in Q4 ($2.1 million for the year)
• Churn: 2.5% of opening ARR per quarter
• Gross margin: 78%
• Hiring: 10 hires across the year, 3, 3, 2 and 2 by quarter, ending at 40 people, at an average fully loaded cost of $150k a year per employee, existing and new
• Other operating costs: $250k a quarter

Illustrative. Revenue is average ARR for the quarter ÷ 4. Burn is approximated by EBITDA, ignoring working capital, capital spending and interest. Hires are assumed to start at the beginning of each quarter. Figures may not add or subtract exactly due to rounding.

The plan ends the year at $5.64 million of ARR, up 41%, with $3.21 million of cash. At the Q4 burn rate of about $232k a month, that's 13.8 months of runway going into the next year.

Those three numbers (ending ARR, ending cash and runway) are the headline figures the board approves. Everything else in the table is how the company intends to get there.

The downside scenario, and why it needs a trigger

Now suppose new ARR comes in 25% below plan every quarter, and the company hires as planned anyway.

In the downside, the company ends the year with less revenue, the same payroll and 11.6 months of runway, under a year. Ending cash is only about $190k below plan, so the problem doesn't look urgent in any single month. It shows up as a weaker position going into a fundraise.

The fix is to decide the response in advance and write it into the plan as a trigger:

If new ARR is more than 20% below plan for two consecutive months, the four second-half hires are paused (owner: CEO and CFO) until new ARR is back within 10% of plan for a full quarter.

With that trigger, the downside ends at 15.4 months of runway, longer than the original plan. Ending ARR is still about $500k lower, but the company protects its cash and doesn't have to make the decision in a crisis.

Triggers work because they are agreed while everyone is calm. Two or three are enough, and each needs a measurable condition, a named action and an owner.

Top-down vs. bottom-up planning

There are two ways to set the targets, and good plans use both:

• Top-down: leadership or the board sets the targets, for example "we need $6.0 million of ending ARR to raise the next round."
• Bottom-up: each team builds its number from capacity. Sales says how much new business its current and planned reps can close. Customer success says what churn looks like. Each department costs its own plan.

The gap between the two is the most useful number in the process. In the example, a $6.0 million top-down target against a $5.64 million bottom-up plan leaves a gap of about $360k. There are only three honest ways to close it:

1. Add capacity early enough to matter, such as more sales hires in Q1, with a realistic ramp time.
2. Change the drivers, for example a price increase, better conversion or lower churn, each with a named plan behind it.
3. Lower the target and explain why.

The dishonest fourth option is to raise the sales number without changing anything that produces it. That's how plans end up missed by the second quarter.

How to build an annual operating plan

1. Start from actuals. Close the books for the year to date and project the rest of the year. The plan starts from where the company will really land, not from last year's budget.
2. Set the targets. Agree on three to five top-down targets with leadership or the board.
3. Build the driver model. Revenue from pipeline and conversion, churn and pricing, and costs from headcount and a few non-headcount lines. A driver-based financial model lets you change an assumption once and see the effect everywhere.
4. Collect bottom-up plans. Each department submits its headcount, programs and spending, tied to what it will deliver.
5. Reconcile the gap. Compare bottom-up with top-down, and close the difference with the three options above.
6. Run the scenarios. Build at least a downside case, find the lowest cash point in the year, and set triggers.
7. Approve and lock. The board approves the plan before the year starts, and it becomes the fixed baseline.
8. Hand it to the operating rhythm. Every month, compare actuals with the plan, explain the variances and update the forecast.

When to start: the average budgeting cycle in the AFP survey is nearly nine weeks, and many companies take longer. A company on a calendar year should start in September, or early October at the latest, to leave time for board approval in December. The FP&A Trends Survey 2024 found that 57% of organizations take one to three months to prepare their annual budget. Only 15% manage it in under a month.

Tracking the plan: budget vs. actual and reforecasts

The AOP stays fixed for the year. Two things change around it:

• Budget vs. actual: each month, actual results are compared with the plan, line by line, and the significant variances are explained. The goal is a decision, not a report. What caused the variance, and does anything need to change?
• The reforecast: monthly or quarterly, the forecast for the rest of the year is updated with the latest information. The plan says what the company intended. The forecast says where it will land. The gap between them is the conversation the board wants.

Keep both, and don't overwrite the plan with the forecast. Once the original plan disappears, nobody can tell whether the company is executing well or has just lowered the bar.

For the cash side, a rolling 13-week cash flow forecast sits underneath the AOP and catches problems weeks before the monthly numbers do.

Common mistakes

1. A growth percentage instead of drivers. "Revenue grows 40%" can't be tested or managed. "Six reps closing $90k a quarter each after a four-month ramp" can.
2. Hiring on the plan, revenue on hope. Costs are committed and revenue isn't. Plans that hire ahead of revenue need a trigger for when revenue lags.
3. No downside case. A plan with one scenario usually turns out to be the best case.
4. Plans not built on drivers. In FP&A Trends' 2025 research, 77% of companies using driver-based models rated their forecasts good or great. In our experience, driver-based plans are also easier to explain, update and defend.
5. Starting too late. Planning that runs into January leaves the company operating for weeks without an agreed baseline.
6. Planning disconnected from cash. A plan that shows EBITDA but not the lowest cash point of the year misses the number that matters most for a company that isn't yet profitable.