Pipeline Math Calculator
from a revenue target back to the sends it actually needs

Most go to market plans are not wrong about strategy. They are wrong about a division nobody performed. The revenue number implies a pipeline number, the pipeline number implies a meeting count, the meeting count implies a send volume, and somewhere in that chain sits a figure larger than the addressable market or larger than what the team can physically send. That is discoverable in about twenty minutes. It usually gets discovered in month four instead, with a quarter of budget gone and an argument about copy underway.

This tool is those twenty minutes. It is deliberately unsophisticated, and the sophistication was never where the value sat. What it does that most planning calculators do not is refuse to hand you a conversion rate we have not measured, run every answer at a pessimistic and an optimistic rate rather than quietly picking one for you, and name the ceiling your answer breaks.

How do you use it?

Four steps, and the third one is the one people skip.

Step 1. The target and the deal economics

Revenue target for the period, average deal size, opportunity to close win rate, slip rate. Use your segmented closed won average rather than a blended company figure that mixes a pilot with an enterprise renewal, because a blended average produces a plan for a customer you do not have. If you have no win rate from real history, stop here. A model built on an assumed win rate inherits the error and then multiplies it by your entire revenue target. The honest next step in that situation is to create fifteen to twenty opportunities by hand and measure what happens to them.

Step 2. The funnel rates

Meeting held to opportunity rate, and show rate. The show rate field defaults to 50%, which is our measured figure for teams where calendar discipline is broken, and it is the division most models omit entirely. If your calendar discipline is genuinely good, raise it and use your own number. If you do not record show rate at all, leave it and treat the fact that you cannot fill the field in as the most useful thing this page has told you.

Step 3. The ceilings

Addressable companies, mailboxes, sends per mailbox per day, weeks available before you need the pipeline. This is the step everyone skips and it is the only step that can tell you the plan is impossible rather than merely ambitious. Without it you get an activity number and no idea whether that number exists inside your market or inside your infrastructure. The verdict says so out loud when no physical ceiling has been checked, because a calculator that returns a large number and no constraint check has done the easy half of the job.

Step 4. Read both columns, then the stress test

The left column is the fleet baseline. The right column is the working benchmark. If the plan only survives in the right column, the plan does not work, because a channel with no history has no reason to land at the top of the distribution on its first attempt. Then open the stress test panel, which changes one assumption at a time and shows which single change flips the verdict. That assumption is the thing to go and measure this week.

What do these numbers actually mean?

Meetings booked and meetings held are two different numbers and the gap between them is the show rate. At 50% it doubles every activity figure downstream, which means a team can book exactly the number of meetings the plan called for and still miss by a factor of two, with the miss having happened in the calendar rather than in the pipeline. It is also the cheapest correction available on this page.

Positive replies needed are positive replies, not replies. A reply includes an out of office and a request to be removed. Emails to send is total emails including follow ups, because the rate this tool uses divides positives by emails sent rather than by contacts reached. Those two distinctions are the reason two people can describe the same campaign with numbers a hundred times apart and both believe they are being accurate.

Sessions needed for the inbound leg appears only once you supply your own two conversion rates, because we have not measured them and will not invent them. The LinkedIn leg behaves the same way and stays uncalculated until you provide a positive share of DM replies from your own reporting.

How many cold emails does it take to book ten meetings a month?

At our derived fleet baseline of roughly 0.05% positive replies on sends, ten booked meetings a month needs on the order of 20,000 emails if every positive reply converts to a booking, and roughly double that at a 50% positive reply to booking rate. At the 0.5% floor of the working benchmark, the same ten meetings need roughly 2,000 to 4,000 emails. That spread is a factor of ten and it separates a plan that needs one sender from a plan that needs a fleet.

The honest way to use those two figures is to plan on the low one and treat the high one as upside. The fleet baseline describes every sequence running at a given moment, including the ones still in warm up and the ones days away from being killed, which is exactly the population a new channel joins. The 0.5% figure describes a sequence that has already survived iteration. They measure different things and the difference is the whole reason this tool has two columns.

How many meetings does an SDR need to book to pay for themselves?

Use the same model with one substitution. Set the revenue target to the gross profit that seat has to produce rather than to your company target: fully loaded annual cost of the seat divided by your gross margin gives the revenue it needs to source. Enter that as the target with the period set to year, keep your real deal size, win rate and funnel rates, and read the meetings and sends it returns.

The step that surprises people is the show rate division, which doubles the required booking count at 50%. We publish no cost figures on this site in any form, so the seat cost is yours to supply. Anyone quoting you a cost per meeting before knowing your deal size, your market and your cycle length is quoting a number for a different company.

The methodology, in the order it runs

Six divisions and one multiplication, in a fixed sequence, from revenue backwards to activity. Target divided by deal size gives deals. Deals divided by win rate gives opportunities. Opportunities multiplied by deal size, then divided by one minus your slip rate, gives required pipeline. Existing open pipeline comes off that to give the gap. The gap divided by deal size gives opportunities to create. Those divided by your meeting to opportunity rate give meetings held. Meetings held divided by show rate gives meetings booked. Meetings booked divided by the positive reply to booking rate gives positive replies needed. Positive replies divided by the positive reply rate on sends gives the send volume, computed twice, once per rate column.

Then four ceiling checks run, all of them on the conservative column rather than the flattering one: market size, sending capacity, LinkedIn capacity, and the ramp against the window. Each returns clears, tight, breaks or not checked, and the verdict takes the worst of them. Onboarding and warm up are deducted from the window in series before any per week figure is calculated, which is why the required weekly send rate is higher than dividing by your total weeks would suggest.

All internal arithmetic runs on unrounded numbers and rounding happens once, at print. A rounded intermediate is never fed back into the chain. That is the bug that makes most spreadsheet versions of this model disagree with themselves by a few percent, and it matters more than it sounds when a reader is checking your work.

Every default in the interface carries a source class, visible next to the field. Measured means a figure read off campaign reporting inside the Outbound Pros group with its denominator stated. Derived means calculated from other published figures, inheriting their assumptions. Cited means owned by another property in the group and credited to it. Policy means a decision rule we act on rather than a measurement of anything. Illustrative means a round number chosen so the mechanics are visible, which is not a benchmark. Assumption means a conservative planning value we chose and you should replace. Needed means no default exists, so the dependent output is suppressed. If a number in the tool has no label, that is a bug and we would like to hear about it.

Where this model stops

Seven limits, stated because a model whose boundaries are hidden is a model that gets misused, usually by being quoted with more confidence than it earned.

• It is not a forecast. It returns the volume implied by your rates. It takes no view on whether any particular deal closes, and it cannot, because it has never seen your pipeline.
• It assumes your rates are stable. Real rates move with segment, season, offer and list quality. One positive reply rate across a whole quarter is an average hiding a distribution, and the distribution is where the decisions live.
• It does not model the inbound compounding curve. Inbound produces at a declining marginal cost over time, which is a different shape from the roughly linear one outbound follows. The inbound leg here converts sessions to meetings on a flat basis at rates you supply, which understates inbound in month twelve and overstates it in month one.
• It treats the ramp as sequential. Onboarding and warm up overlap in practice and the tool deducts them in series, which makes the effective sending window slightly short and the required weekly rate slightly high. We would rather be pessimistic about the window than optimistic about it.
• It prints no platform sending ceiling. We have not re-verified the published Google Workspace or Microsoft 365 limits against the providers' own documentation, so rather than reprint a number of unknown age the sends per mailbox per day field ships with a deliberately low planning assumption for you to replace.
• It ignores everything outside the funnel. Brand, timing, competitive displacement, a lead who was already warm because they read something you published. The chain is a floor on the activity required, not a description of how revenue actually arrives.
• It cannot fix an input you did not measure. If your win rate is a guess, the output is a guess with false precision attached, and false precision is more dangerous than an honest range because it is the version that gets quoted in a board meeting. The illustrative counter at the top of the result exists to keep that visible.

One field deserves its own note. Positive reply to meeting booked defaults to 100%, which is not a claim that every positive reply becomes a meeting. It is a deliberate floor. We hold no measured figure for that step that survives our own denominator rule, so rather than invent one we set the field where it cannot flatter the result. Every activity number below it is therefore a minimum, and your real requirement is higher.

Why you can check this number

Checkable is a higher standard than trustworthy, and it is the one worth aiming at. Four things make this result checkable. Every rate names what it divides by. Every default carries a source class before you touch it. The rates we do not have are blank rather than plausible. And the arithmetic is published in the order it runs, on this page, so you can reproduce it in a spreadsheet and walk away from the widget entirely. The tool will also export the chain as live formulas rather than as values, for the same reason.

What do you do with the answer?

The number that broke is the number to go and measure. Every input badged Illustrative is a place this plan can quietly fail, and the stress test panel tells you which one carries the verdict. If the answer is that the plan does not fit inside your market, no channel change rescues it and the target or the segment has to move. If the answer is that it fits only at the optimistic rate, you are looking at a hope rather than a plan.