Activity-to-pipeline math

Activity-to-pipeline math is a backward plan. Start with the revenue target, turn it into deals and opportunities, then into qualified accounts and the activity that produces them. Total replies and positive replies measure different things. Counting total replies can overstate actual pipeline input by more than half.¹ Build the model around the conversion that creates the next stage, then inspect where actual movement falls short.

Build the model

Set the destination before counting touches. This keeps activity tied to pipeline creation instead of turning it into a standalone quota.

Use a waterfall pipeline-generation model to show how the target will be reached.² Start with the revenue goal, then calculate the deals, opportunities, and qualified accounts required.³ Average deal size and conversion rates provide the inputs for the account-engagement volume you need to create ahead of the period you want to fill.⁴

Use these lines in your worksheet:

• Deals needed = revenue target / average deal size
• Opportunities needed = deals needed / opportunity close rate
• Qualified accounts needed = opportunities needed / qualified-account-to-opportunity rate⁵

Keep each rate attached to a defined event. A deal should mean the same thing every time it enters the calculation, and an opportunity should have a clear qualification point. If those definitions move during the period, the activity target loses its meaning.

Convert accounts into activities

This stage turns the account requirement into work your team can schedule. First use the rate at which worked accounts create pipeline. Then use the rate at which planned activity creates a worked account or engagement.

Track how many actively worked accounts turn into pipeline.⁶ Then extend the worksheet:

• Actively worked accounts needed = qualified accounts needed / active-account-to-pipeline rate
• Activities needed = actively worked accounts needed / activity-to-active-account rate

Define what counts as an activity before calculating the total. A call, email, social touch, or research action belongs in the activity column only when it has a consistent counting rule. Use conversion rates to calculate how many prospects belong in sequences to reach the target.⁷

Ask yourself:

• What event makes an account actively worked?
• What event moves an account into pipeline?
• Which activity can the team repeat and measure without changing the definition?

Before you continue, give each denominator an owner, a clear event, and a rate you can compare with actual results. If your qualified-account definition already means pipeline entry, remove the active-account step and keep the rest of the chain intact.

Choose rates that match the motion

The model is useful when its rates describe the motion you actually run. A rate borrowed from another role or offer can create a precise activity target that produces the wrong output.

Set the metrics according to the role, product, and type of company.⁸ Use the same logic for reply, meeting, qualified-account, opportunity, and close rates. A waterfall model can multiply forward from planned activity or divide backward from a pipeline target to produce the required activity level.⁹

Keep reply rate below the pipeline stages it feeds. A benchmark example turns a 4 percent total reply rate into about 1.7 percent positive replies, roughly one genuinely interested person for every 59 emails sent.¹⁰ Use the positive reply or meeting rate when estimating pipeline creation, and keep uninterested replies, automatic out-of-office responses, and unsubscribes out of that denominator.

For each rate, ask what event the percentage predicts. If the answer is vague, define the event before setting the activity target.

Set the period and capacity

An activity requirement becomes operational when you assign it to the available time and the accounts the team can work. Run the calculation before launch so the required list size is visible before outreach begins.

The backward coverage model gives you the monthly qualified-account requirement for pipeline-velocity and revenue targets.¹¹ Running the arithmetic before launch shows the list size your revenue target requires and supports capacity planning.¹²

Use this sequence for planning:

• Set the revenue target for the period.
• Calculate deals, opportunities, and qualified accounts.
• Convert qualified accounts into actively worked accounts.
• Convert worked accounts into activities.
• Divide the activity requirement across the available work periods.
• Check that the resulting account and activity load fits the team capacity.

If the required list exceeds the accounts you can work well, change the model input causing the gap. That may be deal size, a conversion rate, the target, or the period. Raising the activity count alone hides the constraint.

Read the model after launch

Use the worksheet for the expected result. Use the pipeline to see where the live process departs from that expectation, and review the conversion points instead of looking only at total activity.

A pipeline shows where each lead stands, what action comes next, and where the process breaks down.¹³ Each stage should reflect a specific action already taken or an action that needs to happen next.¹⁴ Compare planned activity with movement through every stage, then replace the assumed rate with the observed rate when the pattern is stable enough to use.

Track activity needs by week against the goals for the end of the period.¹⁵ Review the gap in this order:

• Activity completed versus activity planned
• Activities that created an engaged account
• Engaged accounts that became qualified accounts
• Qualified accounts that became opportunities
• Opportunities that became deals

Work on the first gap in that chain. A shortfall at the account-engagement step needs a different diagnosis from a shortfall between opportunities and deals. Keep the activity target unchanged while you locate the failing conversion, then update the relevant rate in the next planning cycle.

What not to do

These mistakes make the arithmetic look complete while separating it from the pipeline it is meant to create.

• Use metrics that fit each selling role, product, and company. There is no one-size-fits-all approach.¹⁶
• Calculate the list size required by the revenue target before outreach begins.¹²
• Use the pipeline as an operational view of the leads and actions in motion.¹⁷
• Keep pipeline, funnel, and process as separate labels because they describe different layers of the revenue system.¹⁸