How do I build a B2B revenue plan or forecast?
Build a B2B revenue plan by working backward from the number: history, pipeline by segment, and the at-bats, close rate, and deal size to hit it.
Nicolas Heath
RevOS™ Director, Swivel
A B2B revenue plan is a bottom-up forecast that ties your revenue target to the specific activity required to hit it. You build it by working backward from the number: start with historical conversion rates and pipeline by segment, layer in team commitments and known opportunities, then model the at-bats, close rate, and average deal size needed to close the gap. Done right, it turns "we need $5M" into a testable plan — how many qualified opportunities, from which segments, through which channels — instead of a target pinned to a spreadsheet and a prayer.
Here's the framework, step by step.
Why most "revenue plans" are just wishes
The common failure is a top-down number handed to the team with no model beneath it: "grow 40% this year." It sounds like a plan, but it's a wish, because nothing connects the target to the activity that would produce it. Without the underlying math — how many opportunities, at what close rate, at what deal size — you can't tell whether the number is achievable, where it will come from, or when it's going off track. A real plan makes the target falsifiable.
Step 1 — Start from history and segment
Ground the plan in what actually happened. Pull your historical numbers and break them out by segment — industry, size, ICP tier, channel — because averages hide the truth. For each segment you want:
Average deal size
Win rate (opportunity → closed-won)
Sales-cycle length
Volume of opportunities produced
Segmenting matters because a plan built on blended averages will over-forecast your weak segments and under-resource your strong ones. Your best-fit ICP tiers convert very differently from the long tail.
Step 2 — Layer in commitments and known opportunities
On top of the historical baseline, add what you already know about the coming period: named opportunities in the pipeline, renewals and expansion you can reasonably count on, and bottoms-up commitments from the team on accounts they're working. This grounds the forecast in reality before you model the gap you still have to fill.
Step 3 — Model the math to close the gap
This is the core of the plan — the funnel equation that connects the target to activity. Work backward:
Start with the revenue target, minus what commitments and known opportunities already cover. What's left is the gap.
Divide the gap by average deal size → the number of new deals you need.
Divide new deals by win rate → the number of qualified opportunities you need.
Divide opportunities by your opportunity-creation rate → the at-bats (meetings, qualified leads) required.
Now the target is expressed as concrete activity: this many qualified opportunities, from these segments, requiring this much top-of-funnel. That's a plan you can staff, fund, and track.
Step 4 — Stress-test against capacity and channels
A model can demand more than the business can deliver. Check it against reality:
Capacity: can your current reps handle that opportunity volume at healthy utilization, or does the plan quietly assume headcount you don't have?
Channel mix: where do those at-bats come from — demand gen, business development, referrals, events — and is each channel realistically sized to produce them?
Gaps: if the math demands more than your engine currently produces, the plan has to include what you'll build or change to close it, not just a bigger number.
Step 5 — Make it a living plan
A revenue plan isn't a January artifact. Track actuals against the model continuously, so you can see early when a segment is underperforming or an at-bat assumption was wrong — and adjust before the quarter is lost. That requires closed-loop reporting tying activity to outcomes; see what closed-loop reporting is and how to set it up. Without it, you're flying on last quarter's instruments.
The bottom line
A B2B revenue plan is only as good as the model beneath the number. Start from segmented history, add what you already know, then work backward through deal size, win rate, and opportunity creation to express the target as activity you can actually resource. Then track it against reality and adjust. That's the difference between forecasting revenue and merely hoping for it.
Build the engine your plan depends on
A revenue plan assumes a system that can produce the pipeline it calls for. The free Must-Haves for B2B Growth guide lays out how to build that engine — demand generation, business development, and the RevOps reporting that keeps the plan honest — so your forecast rests on a machine, not a hope.
Frequently asked questions
How do I build a B2B revenue plan?
Work backward from the target. Start with segmented historical conversion rates and pipeline, add known opportunities and team commitments, then model the at-bats, win rate, and average deal size needed to close the remaining gap. The result expresses your revenue number as concrete, resourceable activity.
What's the difference between a revenue plan and a sales forecast?
A forecast predicts what will likely close from existing pipeline; a revenue plan is the fuller model that also defines the activity and pipeline you must generate to hit a target. The forecast is a subset — the plan includes the gap you still have to fill and how.
What data do I need to build a revenue forecast?
Historical deal size, win rate, sales-cycle length, and opportunity volume — broken out by segment — plus current pipeline, renewals, and bottoms-up commitments from the team. Segmented history is what keeps the model from over- or under-forecasting.
Why should I segment my revenue plan?
Because blended averages hide reality. Your best-fit ICP tiers convert at very different rates and deal sizes than the long tail. A segmented plan resources your strong segments correctly and stops you from over-forecasting weak ones.
How often should I update the plan?
Continuously. Track actuals against the model so you catch an underperforming segment or a wrong assumption early enough to adjust. That requires closed-loop reporting connecting activity to outcomes — without it, you're planning on stale data.
