How much pipeline do you need? The reverse math of revenue targets

To know how much pipeline you need, work backwards from the revenue target: divide the target by your average deal value to get deals needed, divide deals by your win rate to get opportunities, and continue dividing by each conversion rate up the funnel — meetings, replies, prospects contacted. The result is a weekly activity number you can actually manage, instead of a revenue number you can only watch.

Why work the funnel backwards?

Revenue is a lagging indicator: by the time you notice it is short, the pipeline that should have produced it needed to exist months ago. Activity is a leading indicator you control this week.

Reverse math connects the two. It converts "we need $600k in new business" into "we need to put this many qualified prospects into sequences every week" — a number a team can execute, measure and correct. It also exposes, in advance, whether a target is arithmetically achievable with your current team and conversion rates, which is a conversation far better had in January than in November.

The formulas

Six divisions take you from annual target to weekly activity. Definitions matter — agree on what counts as an opportunity and an SQL before plugging in numbers.

1. Deals needed

Deals = Revenue target / Average deal value (ACV)

2. Opportunities needed

Opportunities = Deals / Win rate

Win rate = the fraction of qualified opportunities that become customers.

3. Pipeline value needed (coverage)

Pipeline value = Opportunities × Average deal value

Equivalently: Pipeline = Revenue target / Win rate. This is where coverage rules of thumb like "3–4x pipeline" come from — they are just inverted win rates. Your sales pipeline coverage should reflect your win rate, not a benchmark.

4. Meetings needed

Meetings held = Opportunities / Meeting-to-opportunity rate

Not every first meeting becomes a qualified opportunity; this rate captures the drop.

5. Positive replies needed

Positive replies = Meetings held / (Reply-to-meeting rate × Show-up rate)

Some interested replies never book; some booked meetings never happen. Both leaks are real.

6. Prospects to contact

Prospects contacted = Positive replies / Positive reply rate

Note this uses the positive reply rate — replies that express interest — not the total reply rate, which includes rejections and out-of-office messages.

Finally, divide by working weeks to get the operating number:

Weekly prospecting volume = Prospects contacted / Working weeks

A worked example (hypothetical numbers)

Every figure below is a hypothetical assumption chosen for arithmetic clarity — not a benchmark, not an AVANTAI result, and not a promise of what your funnel will do.

Imagine a B2B services company with:

• Revenue target from outbound: $500,000/year
• Average deal value: $25,000
• Win rate: 25%
• Meeting-to-opportunity rate: 50%
• Reply-to-meeting × show-up: 40%
• Positive reply rate: 2%
• Working weeks: 46

Running the math:

Step	Calculation	Result
Deals	500,000 / 25,000	20 deals
Opportunities	20 / 0.25	80 opportunities
Pipeline value	80 × 25,000	$2,000,000
Meetings held	80 / 0.50	160 meetings
Positive replies	160 / 0.40	400 replies
Prospects contacted	400 / 0.02	20,000 prospects
Weekly volume	20,000 / 46	~435 prospects/week

The punchline is the last row. Under these assumptions, the $500k target is roughly 435 well-targeted prospects entering sequences every week, sustained all year. That number has immediate physical implications: it requires enough verified data, enough warmed mailboxes to send at healthy volumes, and enough capacity to handle around nine positive replies a week without letting any go cold.

Change any assumption and the machine resizes: double the deal size and everything halves; halve the positive reply rate and everything doubles. This is why targeting and messaging quality — the drivers of that 2% — are worth more than any other optimisation in the chain.

What the model tells you when reality diverges

The model's second job starts after launch: it becomes your diagnostic frame. Compare measured rates against assumptions monthly and read the gaps stage by stage:

• Prospects contacted below plan → capacity problem: data supply, mailbox count, or process bottlenecks.
• Positive reply rate below assumption → targeting or messaging problem — usually ICP precision before copy.
• Replies fine, meetings low → speed and process: reply handling is too slow, or booking friction is high. This is where CRM and follow-up discipline pays for itself.
• Meetings fine, opportunities low → qualification problem: the meetings are with the wrong people, pointing back at the ICP.
• Opportunities fine, wins low → a sales problem downstream of prospecting, and no amount of extra volume will fix it.

Also mind the time axis: with a four-month sales cycle, this week's prospecting is next quarter's revenue. A pipeline gap discovered inside one sales cycle of year-end is, arithmetically, already too late — which is the strongest argument for running this model continuously rather than once a year.

One more use for the output: multiply your cost of running the whole machine by the model and you get a grounded view of customer acquisition cost before spending a year finding out.

From spreadsheet to system

The math is the easy part; the hard part is an operation that reliably produces the weekly number with quality high enough to hold the conversion assumptions. That is what we build: the AI Outbound Engine runs the targeting, data and sequencing machinery, with the Outbound Validation Sprint as the first step that replaces assumed rates with measured ones.

Before any of that, find out whether your current setup can sustain your number — the outbound maturity diagnostic takes a few minutes and maps your gaps. If you would rather walk through your own reverse math with us, book a strategy call.