← Back to Blog
Pipeline Planning

Sales Pipeline Planning: How to Work Backwards From Your Revenue Target to Monthly Goals

By ARRGuide Team•March 20, 2026•10 min read

Why Most Pipeline Planning Falls Short

Every VP of Sales and CRO gets asked the same question at the start of the year: "Do we have enough pipeline to hit the number?" Most of the time, the honest answer is we're not sure. There's a gut feel, a coverage ratio that someone read in a Gartner report, and a spreadsheet that one person on the team maintains and everyone else quietly distrusts.

The typical pipeline planning process looks something like this: Finance sets an ARR target. Sales leadership adds a buffer. Someone applies a blended coverage ratio to get a pipeline target. That number gets handed down to reps as a quota.

The problem isn't the math — it's that the math stops there. A single pipeline coverage ratio tells you how much pipeline you need in aggregate, but it doesn't tell you:

  • How much pipeline you need each month, not just the full year
  • How different channels contribute differently to that pipeline
  • How long it actually takes deals to move from one stage to the next
  • Whether your current headcount can actually generate that pipeline

The result is a plan that looks precise on paper but leaves the team flying blind month to month. You hit Q2 and realize the pipeline you needed to close Q3 should have been built in Q1 — and it wasn't.

The pipeline you need to close in Q3 needs to be in Stage 1 by early Q2. If you don't model the timing, you'll only find out you're behind when it's too late to do anything about it.

The Right Framework: Reverse-Funnel Modeling

Reverse-funnel modeling starts at the end — your revenue target — and works backwards through each stage of the funnel to calculate required pipeline inputs. The logic is straightforward:

  1. Start with your monthly bookings target — break your annual ARR goal into monthly buckets using your seasonality assumptions.
  2. Divide by average deal size to get required won deals per month.
  3. Divide by win rate — adjusted for timing — to get required SQOs.
  4. Divide by stage conversion rates to get Stage 1s and MQLs.
  5. Repeat for each channel separately — because AE-generated deals, SDR-generated deals, and marketing-sourced deals all have different profiles.

The output is a complete picture: every month of the year, every stage of the funnel, broken down by channel. Not a coverage ratio — actual targets.

Why Timing Distributions Change Everything

The most important — and most overlooked — element of pipeline planning is timing. Deals don't close in the same month they enter the funnel. An SQO created in March might close in April, May, or June depending on your average sales cycle. A Stage 1 opportunity created in January might not become an SQO until March.

This means that to hit a revenue target in month N, you need pipeline created in months N-1, N-2, N-3, and so on. If you model pipeline requirements as a static calculation, you'll consistently generate the right amount of pipeline at the wrong time.

A proper pipeline model uses timing distributions — what percentage of a cohort converts at each stage in each subsequent month. For example:

  • 73% of Stage 1 opportunities become SQOs in the same month they're created
  • 15% convert in month 2
  • 5% in month 3, 3.5% in month 4, 3.5% in month 5

With these distributions, you can calculate exactly how many Stage 1s you need to create in each month to produce the SQOs you need three months from now. Without them, you're guessing.

A common mistake: teams set an annual pipeline coverage ratio of 3x and call it a plan. But 3x coverage in January doesn't help if none of those deals are in the right stage to close in Q1. You need the right pipeline at the right stage at the right time.

Breaking It Down by Channel

Not all pipeline is created equal. An opportunity generated by an outbound SDR has a different average deal size, conversion rate, and sales cycle length than one sourced through a paid search campaign. Treating them the same distorts your model in ways that compound over time.

A channel-level model separates pipeline requirements by source:

  • AE-generated pipeline (outbound, existing relationships)
  • SDR-generated pipeline (inbound and outbound sequences)
  • Paid search / demand generation
  • Events and field marketing

Each channel has its own deal size assumptions, conversion rates, timing distributions, and cost per MQL (for marketing channels). The model calculates what each channel needs to produce independently, then aggregates to verify the total covers the plan.

This matters for budgeting as much as planning. If you know Paid Search drives 25% of your MQL target at $150 per MQL, you can calculate your demand generation budget directly from your revenue goal — not from last year's spend plus a growth percentage.

The Headcount Question

Once you know what pipeline you need by channel and by month, you can answer the question that actually drives hiring decisions: do we have enough capacity to generate it?

For SDRs, capacity is measured in Stage 1s or SQOs per rep per month. For AEs, it's bookings per rep per year. With a pipeline model in place, you can calculate:

  • How many SDRs you need to hit your Stage 1 targets in each month
  • Whether your current AE team can close the deals the pipeline model requires
  • Where the gaps are, and how far in advance you need to start hiring to cover them

This turns the annual headcount debate from a negotiation into a math problem. You don't need 6 SDRs because it feels right — you need 6 SDRs because the model shows that 5 can only generate 83% of the Stage 1s required to hit Q3 bookings.

A Practical Example

Say your company has a $5.7M new bookings target for the year, with 75% sales-generated and 25% marketing-generated. Your AEs close deals at an average of $35,000, and SDRs at $35,000 as well. Paid search drives MQLs at $20,000 average deal size.

Working backwards from the bookings target:

  • $5.7M ÷ weighted avg deal size → roughly 182 won deals needed for the year
  • At a 22% win rate → approximately 392 SQOs needed
  • At 88% Stage 1-to-SQO conversion → approximately 445 Stage 1s needed from sales channels
  • Plus 1,363 MQLs needed from marketing channels to generate the remaining pipeline

Now spread that across 12 months with seasonality — say 20/30/50 within each quarter — and you have a monthly target for every stage of the funnel. That's the plan.

The model also shows you that to close $1.87M in Q4, you need SQOs created in Q2 and Q3 to be in the right stage by October. Which means your SDR team needs to be generating Stage 1s in June that won't close until November. If you don't see this now, you'll see it in October when it's too late.

Building This Without a Spreadsheet

Historically, this kind of model lived in a complex Excel workbook — dozens of tabs, lookup formulas connecting stages across months, and one person on the RevOps or finance team who understood how it worked. When they left, the model broke.

We built ARRGuide Pipeline Planner to make this model accessible without the spreadsheet overhead. You set your quarterly targets, define your channel assumptions (deal sizes, conversion rates, timing distributions), and the model calculates every stage target for every month across two years — instantly, with no formulas to maintain.

The planner handles:

  • Two-year reverse-funnel modeling across all channels
  • Month-by-month targets for MQLs, Stage 1s, SQOs, and won deals
  • Capacity planning — SDR and AE headcount vs. calculated targets
  • Marketing spend requirements by channel based on MQL targets and cost per MQL
  • Export to Excel for sharing with stakeholders who prefer a spreadsheet

It's the model most RevOps teams are building from scratch every January — minus the 40-tab spreadsheet and the single point of failure. Start your free trial →

Getting Started

If you're building your pipeline plan for the year, here's the order of operations:

  1. Define your channel mix. What percentage of your target comes from AE-generated, SDR-generated, and marketing-generated pipeline? Get alignment on this before you model anything else.
  2. Set your conversion assumptions. Use actuals from last year if you have them. If not, industry benchmarks are a reasonable starting point — just document your assumptions so you can revisit them.
  3. Model the timing. How long does it actually take deals to move between stages? Look at historical data, or start with a reasonable estimate and refine over time.
  4. Run the model. Calculate required pipeline inputs for each stage and each month. Stress-test the plan by changing key assumptions and seeing how the outputs shift.
  5. Sanity-check against capacity. Can your current headcount actually hit the targets the model produces? If not, you have a hiring problem or a target problem — and it's better to know now.

The goal isn't a perfect model — no model is perfect. The goal is a shared, explicit set of assumptions that the whole team is working from, and a clear line from monthly activity targets back to the annual revenue goal. That's the difference between a plan and a hope.