Activity-to-pipeline math

Activity to pipeline math works backward from the outcome you need. Start with the target, turn it into deals or opportunities, convert those into qualified accounts, then map accounts to contacts and touches. The output is an activity level you can defend because each step has a rate behind it. The trap is treating reply volume as pipeline input. A reply rate on its own means nothing.¹ Total reply rate can overstate actual pipeline input by more than half.² Build the model around positive replies and downstream conversion instead.

Set the target

The target

If created pipeline

Work toward pipeline value

If closed revenue

Include the conversion

The target

• If created pipeline, work toward pipeline value
• If closed revenue, include the conversion

Write the outcome in a form the rest of the model can use. A target that mixes revenue, pipeline dollars and opportunity count will produce an activity number nobody can inspect.

Start with a waterfall pipeline generation model. It is used to understand how the team will reach a revenue target.³ Start with the revenue goal, then calculate the deals, opportunities and qualified accounts required.⁴

Ask: "How many accounts do you need to hit your target?".⁵ Keep the answer tied to a defined period and a clear outcome. If the target is created pipeline, work toward pipeline value and opportunities. If the target is closed revenue, include the conversion from opportunity to closed deal.

Set activity levels only after the waterfall gives you the required pipeline. Activity levels need to describe a repeatable process capable of producing that pipeline.⁶

Build the waterfall

Use backward math when the target is fixed. Each output becomes the input for the calculation before it, so you can see where the activity requirement comes from.

Start with average deal size and the conversion rates in your motion, then map the account engagement volume required to reach the target.⁷ Use these calculations:

• For a revenue target, divide the target by average deal size to find the required wins, then account for the close rate.
• For a created pipeline target, divide the pipeline value by average deal size to find the opportunity count.
• Convert opportunity count into qualified accounts with this formula: opportunities needed ÷ qualified-account-to-opportunity rate = qualified accounts needed.⁸
• Convert the qualified account requirement into the period you plan to operate against. A backward coverage model gives the monthly number of qualified accounts needed to meet pipeline velocity and revenue targets.⁹

Check every rate before you use it. A stale close rate can make the top of the model look reasonable while inflating the activity requirement below it. If a rate is an assumption, label it as an assumption and replace it when observed results are available.

Use observed rates

The model earns trust when each rate comes from the same motion, audience and qualification standard as the work you are planning. Keep the inputs narrow enough that a change in conversion points to a specific part of the process.

The metric set should reflect the role, product and type of company being measured.¹⁰ Track the handoff from actively worked accounts into pipeline, not only the volume of accounts entered into a sequence. A useful review question is: "How many of those accounts ever turned into pipeline?".¹¹

Separate interested replies from "not interested" responses, out-of-office auto-replies and angry unsubscribes.¹² A 4% total reply rate can become about 1.7% positive replies after those responses are removed, or roughly one genuinely interested person for every 59 emails.¹³ Put the positive reply rate into the waterfall. Keep the total reply rate as a diagnostic for message and list behavior, with no role in the pipeline calculation.

When your own history is thin, use a provisional rate and mark the point where it will be tested. The model should show which assumption needs better information. That gives you a clear correction when the output misses the target.

Convert accounts into touches

This is where the account requirement becomes a work plan. Keep accounts, contacts and touches as separate layers so a large touch count cannot hide weak account coverage.

Start with qualified accounts needed. Divide by the rate at which worked accounts become qualified accounts to get the worked account count. Multiply worked accounts by contacts per account to get the contact count. Multiply contacts by touches per contact to get the planned touch count.

Use the same logic for sequence volume. Conversion rates can determine how many prospects to add to sequences to reach the target.¹⁴ If the plan depends on several contacts inside each account, show that assumption separately from the number of accounts. If it depends on repeated touches, show that volume separately from contact coverage.

Run the calculation in either direction. You can multiply forward from planned activity or divide backward from a pipeline target to get the activity level required.¹⁵ Use the backward view for capacity planning and the forward view for checking what current capacity can produce.

Do not let the final touch count become the only number the team sees. The useful question is which layer is short: qualified accounts, contacts per account, positive replies or opportunity conversion. Fix the short layer before increasing every activity input.

Inspect the handoffs

Review the movement between stages, not only the total activity. A pipeline should tell you where each lead stands, what action comes next and where the process is breaking down.¹⁶ It is an operational tool that keeps attention on the right leads at the right time.¹⁷

At each review, compare planned and actual results for worked accounts, contacts reached, positive replies, qualified accounts, opportunities and created pipeline. Look for the first point where actual conversion falls below the rate used in the waterfall.

If touches rise while qualified accounts stay flat, inspect account selection, contact coverage and the reason for outreach. If qualified accounts rise while opportunities stay flat, inspect qualification and the next action. If opportunities rise while pipeline value misses, inspect deal size and opportunity quality.

Keep the question concrete: "How many of those accounts ever turned into pipeline?".¹¹ Move to the next adjustment only after you can answer it from the same account set and period used in the model.

What not to do

The common errors come from handing off the arithmetic or letting a clean formula hide weak inputs.

• Do not give someone a pipeline target and tell them to "go do this math." Build the calculation with the target owner.¹⁸
• Do not trust an activity forecast simply because its arithmetic is mechanical. That mechanical quality also makes the forecast dangerous.¹⁹
• Do not use pipeline, funnel and process as interchangeable terms. Each describes a different layer of the revenue system.²⁰
• Do not stop at a quota. Sellers need the daily actions that will accomplish the goal.²¹

You can now enter a target, average deal size and conversion rates, then work backward to qualified accounts, contacts and touches. When the result misses, inspect the first broken handoff and change that input instead of raising activity across the whole model.