How to Build an Annual Revenue Plan That Finance and Sales Both Trust

Annual revenue plans fail for a predictable reason. Finance presents a number the board wants. Sales presents a number the team can hit. Neither side shows their math, so the two models never actually meet. The result is a negotiation based on position rather than inputs, and a plan that one side does not believe.

A plan both sides trust requires a visible reconciliation of the top-down target with the bottoms-up capacity reality. The gap between those two numbers is the actual decision the leadership team needs to make.

Step 1: Build the Top-Down Model First

Start with what the board or investors expect. Frame it as a target, not a constraint. Document the inputs that produced the number: prior year ending ARR, implied growth rate, and any external commitments that influenced the figure.

The top-down model is usually a single equation:

``` Target New ARR = (Target Total ARR at Year End) - (Prior Year Ending ARR) + (Projected Churn) ```

Make churn explicit. Plans that omit projected churn overstate how much new business is required to hit a net ARR target. Finance and RevOps should agree on the churn assumption before the bottoms-up model starts.

Step 2: Build the Bottoms-Up Capacity Model

Work from the rep roster outward. For each territory or segment, calculate what the current team can realistically produce.

Input	Notes
Quota per fully-ramped rep	Use prior year actuals, not plan quota
Expected quota attainment	Based on historical attainment rate, not 100%
Ramp schedule for new hires	Months to full productivity from hire date
Planned headcount additions	Include realistic hiring timeline, not plan date
Churn and attrition	Account for expected rep turnover

Sum the capacity across the team after accounting for ramp time and realistic attainment. This is the realistic production ceiling. It is almost always lower than the sum of quotas.

Add the planned contribution from existing and expected expansion revenue separately. New logo ARR and expansion ARR should be modeled independently because the motion, cost, and lead time are different.

Step 3: Run the Reconciliation

Put both models in the same table. This is the step most teams skip.

	Amount
Top-down new ARR target	$X
Bottoms-up new logo capacity	$Y
Planned expansion contribution	$Z
Total bottoms-up production	$Y + $Z
Gap	$X - ($Y + $Z)

If the gap is small and explainable by pipeline that is not yet visible, the plan is credible. If the gap is large, it represents a real decision: add headcount, increase win rate assumptions, improve expansion coverage, or reduce the target.

Do not paper over the gap. Document it explicitly and force the conversation about which lever closes it.

Step 4: Stress-Test the Assumptions

The plan is only as good as the weakest assumption inside it. Walk through each key input and ask what happens to the output if the assumption is wrong by a defined amount.

Inputs worth stress-testing:

Win rate. If win rate drops by a meaningful amount from the plan assumption, how many additional pipeline dollars are required to compensate? Average deal size. If deal sizes compress under competitive pressure, how many more deals are needed to hold the number? Ramp time. If new hires ramp slower than modeled, when does the team reach full capacity and how does that shift quarterly distribution? Pipeline coverage. What coverage ratio is assumed to deliver the target new logo number? Is that ratio actually achievable given current generation rates?

Document the answers. A plan with explicit stress tests enables faster mid-year adjustments because the decision branches are already mapped.

Step 5: Produce a Single Negotiated Number

After the reconciliation and stress-test, the output is not two numbers. It is one number with documented assumptions and an explicit record of what was negotiated away.

Write down the assumptions that were accepted, the ones that were challenged, and the risks that were acknowledged but not resolved. This document becomes the reference point for any mid-year variance conversation.

The plan earns trust from both finance and sales by making the logic transparent, not by satisfying everyone. When the number is missed, the team can point to a specific assumption rather than arguing about who built the wrong model.

Common Mistakes

Averaging the top-down and bottoms-up numbers. Averaging produces a number that neither model supports. It eliminates the information value of the gap. Treating quota as capacity. Quota is a target, not a production model. Capacity is what the team will realistically produce given attainment history, ramp schedules, and turnover. Plans built on quota sum overstate production. Leaving churn as a footnote. Churn is a direct input to new logo requirement. Teams that exclude it or use a rough estimate undermine the precision of every other input in the model. Building the plan once and freezing it. Annual plans should have explicit quarterly reviews where assumptions are revisited against actual performance. A plan built in October that is not updated until the following October is a historical record, not a planning tool.

Frequently Asked Questions

Why do sales and finance so often end up with different revenue numbers?

Finance builds from a target the board sets, typically derived from growth expectations or investor commitments. Sales builds from what the current team can realistically close given capacity and pipeline. Neither model is wrong. The problem is that neither team shows the other their work, so the gap never gets negotiated explicitly.

What is the difference between a revenue plan and a sales forecast?

A revenue plan is an annual document that sets targets, allocates headcount, and defines the assumptions underlying the number. A sales forecast is a rolling projection of near-term closes. The plan sets the target. The forecast tracks progress against it.

How do I handle the gap between top-down and bottoms-up?

Name it. Do not average the two numbers or let either side win by default. Bring both models into the same document, calculate the gap in dollars, and force a decision: either adjust the target, add capacity, improve conversion rate assumptions, or accept the risk explicitly.

How detailed should assumptions be in the annual revenue plan?

Detailed enough that if the plan misses, you can determine which assumption was wrong. Average deal size, win rate, ramp schedule, and pipeline coverage ratio should all be explicit inputs. If they are buried or unstated, accountability disappears when the number is missed.

For the frameworks underlying each model, see revenue forecasting, sales capacity planning, and top-down forecasting.