Funnel math

Funnel math turns a revenue target into a workload you can inspect. Start with the result, apply the conversion rate at each step, and work backward to activity you control. A close is a lagging expression of what is already in play: a team can close only opportunities already in play.¹ That makes top-of-funnel work a timing decision. Prospecting, qualifying inbound leads, and finding opportunities with existing customers influence whether later quarters feel easy or desperate.²

Set the target

1

Required wins

2

Required pipeline value

3

Required meetings

1. Required wins
2. Required pipeline value
3. Required meetings

Write down the destination before you count touches. Keep the target, deal value, and conversion assumptions separate so you can see which input changes the workload.

Reverse funnel math starts by determining exactly how much pipeline is needed to hit the overall number.³ Use one deal value definition throughout the calculation. Average deal size can mean first-year ACV or average closed-won value.⁴

Write the worksheet in this order:

• Required wins = revenue target divided by average deal size.
• Required pipeline value = revenue target divided by the win rate, when the win rate is measured against pipeline value.
• Required meetings = required wins divided by the meeting-to-close rate, when that rate starts with meetings.

The forecasting method starts with meetings and multiplies them by close rate to estimate closes.⁵ Reverse that operation when you need the meeting requirement. Label every rate by its start and end stage, then use it only for the calculation that reverses that stage.

Ask yourself:

• What result must this motion produce?
• What does the deal value include?
• Which stage does the close rate start from?

Work backward through the conversion points

Turn the required outcome into counts your team can act on. The calculation becomes useful when every transition has its own count and rate.

Every outbound motion follows the same chain.⁶ An outbound funnel model needs a number for each link in that chain.⁷ For email, measure the transition from emails sent to replies with a reply rate.⁸ Then work backward from the reply requirement to the email volume.

For a call motion, work from held meetings back to daily activity. Divide held meetings needed by held rate to get booked meetings, booked meetings by conversation-to-meeting rate to get conversations, conversations by connect-to-conversation rate to get connects, connects by dial-to-connect rate to get dials, and dials by working days to get daily dials.⁹

Working backward through actual conversion rates lets you calculate the monthly emails, leads, and meetings required with useful precision.¹⁰ Keep the calculation in the same period as the target. A monthly target needs monthly inputs, and a daily activity plan needs the working days available to produce it.

At each line, ask:

• What count must this stage produce for the next stage to have enough volume?
• Is the rate based on booked meetings or held meetings?
• Does this count describe the target period or an earlier period?

Move on only when the stage has a count, a rate, and a defined time window. If one is missing, the next division will create a number that looks precise while hiding an assumption.

Inspect the model before adding activity

A finished calculation gives you a workload. The review shows which assumption deserves attention before you ask for more volume.

Use entered inputs to establish baseline conversion rates before modeling changes.¹¹ Track conversion rate with stage tenancy and stage discounting.¹² Then classify the shortfall through the sales levers of volume, value, and velocity.¹³ This shows whether the model needs more activity, a stronger deal value, or faster movement through stages.

Run both views when you review the plan: forecast revenue from the current pipeline, and work backward from the revenue target to the leads required.¹⁴ The gap between those views shows how much new creation the target still demands.

Test a downstream handoff before assuming the answer sits at the top of the funnel. A client audit found that improving the BDR-to-AE handoff by 5% would generate an additional $549,477 in annualized bookings without additional spend to fill the top of the funnel.¹⁵ Compare that lift with the lift from more outreach, then use the change that removes more work from the plan.

Use these review questions:

• Which rate, if improved, removes the most required activity?
• Where does the count fall faster than the surrounding stages?
• Does the current pipeline cover the target, or does the model require fresh creation?

Keep assumptions beside the counts. Before adding activity, change the rate that most reduces the workload.

Protect the planning horizon

The period attached to the target changes the behavior the model rewards. Keep the current result and future creation visible in separate views.

Sales representatives often interpret hitting their number as hitting the current quarter's number.¹⁶ That interpretation can lead them to devise increasingly creative ways to pull deals forward from future quarters.¹⁷ Build the activity plan around the period that the activity can influence, and record pulled-forward deals separately so they do not disguise a later pipeline gap.

What not to do

These mistakes make the calculation look complete while leaving the operating decision vague.

• Do not set outreach volume from a vague instruction such as sending "a lot" of emails, booking "some" meetings, and hoping the pipeline fills.¹⁸
• Do not leave a short quarter unexplained. Teams can finish below target without knowing why.¹⁹
• Do not ask for a Hail Mary deal to rescue the number. Sales leaders have pushed sales representatives to complete unlikely deals and win against the odds.²⁰
• Do not steer from revenue alone. Track the specific metrics that explain why revenue is where it is and what action to take.²¹
• Do not assume more top-of-funnel activity is the only lever, because even a small conversion improvement can have a very large impact on pipeline.²²