An outbound pipeline plan is credible only when the opportunities required to meet the revenue goal can be produced, worked, and closed within the target period.

Calculate the revenue gap, translate it into required qualified pipeline using the measured in-period yield for new opportunities, then check whether your team can work enough distinct accounts to create that pipeline.

If the required account volume exceeds capacity or the buying cycle extends past the deadline, disclose the gap and change the plan. More activity cannot make a late-stage enterprise deal close sooner by arithmetic alone.

For a Global 2000 motion, capacity includes account research, buying-group coverage, coordination with account owners, and follow-up. A plan based only on email volume or an arbitrary pipeline coverage multiple will miss those constraints.

What is outbound pipeline planning?

Outbound pipeline planning determines which accounts a team can responsibly work, how many qualified opportunities that work can create, and when those opportunities can contribute revenue.

It is a bridge between a revenue target and an executable account motion. It is not the same as a forecast: the plan defines what the team will attempt; the forecast estimates what is likely to close from existing and newly created opportunities.

Define the planning unit before doing any math. Use the same revenue definition throughout, such as new ARR bookings for a quarter. Keep existing pipeline and not-yet-created pipeline separate.

Attribute an opportunity to the correct account entity, source, and owner. For the broader methodology for translating a revenue target into pipeline, see how to calculate the pipeline needed to hit a revenue target.

Which inputs should the plan contain?

A usable plan records both demand and delivery capacity, with the source and period for each assumption.

The table below separates the inputs that are often blended in a single coverage number.

If you do not have a dependable rate, use a range and label it as a scenario. Do not borrow a generic industry conversion rate and present the output as a commitment.

Account selection for outbound prospecting addresses how to define the eligible account set before applying a conversion assumption.

How do you calculate required new pipeline?

Subtract expected revenue from current opportunities, then divide the remaining gap by the measured in-period revenue yield of newly created qualified pipeline.

Use this formula only if newly created opportunities can realistically contribute within the period:

Revenue gap = Period target − expected in-period revenue from existing opportunities

Required new qualified pipeline = Revenue gap ÷ in-period value yield of comparable new opportunities

Suppose the quarterly new ARR target is $2 million. Existing opportunities contribute $1.4 million in expected in-quarter revenue, leaving a $600,000 gap.

If comparable opportunities created at this point in the quarter have historically returned 20% of their qualified value as in-quarter won ARR, the nominal new-pipeline requirement is $3 million ($600,000 ÷ 0.20).

The 20% is a hypothetical value-based, in-period yield, not a vendor benchmark. It must be measured from comparable cohorts. A deal that could eventually win but usually closes in the next quarter cannot be treated as this quarter's 20% contribution.

A stage-weighted forecast of existing deals uses opportunity-specific, in-period probabilities; do not multiply the resulting expected revenue by a second coverage factor.

How do you turn the pipeline requirement into an account workload?

Convert the dollar gap into qualified opportunities, then into distinct accounts using a measured account-level conversion rate.

Round requirements up, and be clear about what an account represents when a parent enterprise has several divisions.

For the hypothetical $3 million requirement, assume $85,000 average qualified opportunity value and a 6% account-to-qualified-opportunity rate:

$3,000,000 ÷ $85,000 = 35.3, rounded up to 36 qualified opportunities

36 ÷ 0.06 = 600 distinct accounts to work

Those 36 opportunities represent $3.06 million at the assumed average value. At the assumed 20% in-period value yield, they imply $612,000 in expected in-quarter revenue, slightly above the $600,000 gap. That is an expectation under the scenario, not a guaranteed outcome.

For enterprise accounts, do not equate 600 accounts with 600 emails. One account may require several stakeholder conversations; another may be excluded because a global account team already owns it.

Validate how many distinct eligible accounts exist and how many the team can work well.

How do you calculate sustainable team capacity?

Calculate how many distinct accounts can pass through active work slots during the planning window, then test whether the necessary research and follow-up are feasible.

A simple steady-state approximation is:

Distinct accounts that can be worked ≈ concurrent active account slots × planning-window length ÷ average active account cycle

Suppose four SDRs can each actively work 75 enterprise accounts, a hypothetical capacity established by their own time study.

That is 300 concurrent account slots across the team. If each account occupies a slot for eight weeks and the team has a 12-week operating window, the steady-state approximation is:

300 × 12 ÷ 8 = 450 distinct accounts

450 × 6% = 27 expected qualified opportunities

27 × $85,000 = $2.295 million nominal qualified pipeline

$2.295 million × 20% = $459,000 expected in-period revenue, if the 20% yield applies to this account mix and timing

The requirement was 600 accounts and approximately 36 opportunities. At these assumptions, the team has a 150-account capacity gap and an approximately $141,000 expected-revenue gap ($600,000 − $459,000). This is a planning scenario, not Rox customer performance data.

The 450-account figure is a steady-state estimate. An initial backlog, holidays, ramping reps, response handling, and unequal account workloads can lower it.

Late-created enterprise opportunities may also have a lower in-quarter yield than early-created ones, making $459,000 optimistic. Use week-of-creation cohorts to refine the plan.

Never take the 450 team total, calculate nine opportunities from it, and multiply by four again; team capacity is already aggregated across four SDRs.

What should you do when required pipeline exceeds capacity?

Expose the shortfall and choose an operational response before assigning a larger activity target. A shortfall can come from account coverage, conversion quality, deal value, or close timing.

Each has a different remedy.

An agent can reduce parts of research and execution workload, but do not simply add theoretical “AI capacity” to the model.

Measure how many accounts the configured workflow can work at acceptable quality, including reviews and exception handling. Rox's approved position is one revenue agent per account, informed by a warehouse-native system of context across revenue stages.

That may support a broader operating motion; it is not evidence that Rox automatically supplies the capacity calculator or forecasting rules in this article. For the surrounding process, see how to build a revenue operating system.

How should you forecast the opportunities already in the pipeline?

Forecast current opportunities from their likely in-period contribution, not their full nominal value.

For each deal, consider qualified value, stage, the buyer's actual next step, age, segment, and time remaining. A $500,000 opportunity early in discovery and a $500,000 opportunity awaiting final approval should not contribute the same amount to a near-term forecast merely because both are open.

A calibrated estimate uses the probability of winning and closing in the target period. The simple expression is:

Expected current-period revenue = sum of (qualified opportunity value × calibrated in-period close probability)

This is an estimate, not a commitment category. Revisit the probability when the buying group changes or a required review stalls. A large deal may merit an explicit scenario rather than burying its uncertainty in a portfolio average.

The forecasting methods guide explains methods for estimating deal contribution; the sales pipeline analysis guide addresses distribution and aging.

How do you review stalled deals without making arbitrary rules?

Flag a deal when its age or buyer activity differs materially from comparable opportunities, then diagnose it before changing the forecast.

A fixed rule such as “halve probability after two weeks” is not evidence of the actual chance to close. Enterprise procurement and technical review can take longer than an SMB sequence even when a deal is progressing.

In a weekly review, record the date of the last buyer-confirmed action, time in stage relative to comparable deals, the unresolved condition, the owner, and the next step with a date.

If the buyer has no agreed next step and the close date is no longer credible, lower the in-period forecast contribution based on evidence and document the change. Keep the opportunity record and forecast treatment distinct.

Do not automatically mark the deal lost or remove it from the CRM because it exceeded a generic stage-duration threshold.

For workflow design beyond the forecast, sales engagement automation discusses how to route tasks and maintain follow-up discipline.

What belongs in a rolling pipeline review?

Review the next 13 weeks as a sequence of account work, opportunity creation, and expected close dates, while preserving the quarter-level revenue goal.

A weekly view can expose a timing gap earlier, but it does not convert new opportunities into this week's revenue.

Each review should answer:

1. Which current opportunities have a buyer-supported path to close in the period?

2. What qualified pipeline has been created from the target account cohort, and when can it contribute?

3. How many distinct accounts remain eligible, active, or waiting for capacity?

4. Which accounts have an owner or permission conflict that blocks outreach?

5. Which assumption changed, who will correct it, and when will the plan be updated?

Do not distribute a quarterly goal evenly across weeks unless the actual close pattern justifies it. Enterprise contracts may cluster around customer procurement dates. Use the rolling view to understand timing, not to manufacture weekly close targets.

How should enterprise account context affect the plan?

The plan should reflect which account, division, stakeholder group, and owner an outbound action concerns.

A parent-company record is not a substitute for knowing whether a regional business unit has the need, budget, and permission to proceed.

Duplicate sequences to the same buyer can make a capacity model look productive while damaging the account relationship.

Rox describes its approach as a revenue agent for enterprise organizations, with one agent per account drawing on the broader warehouse foundation and external signals.

A system of context can help relate the account's recorded commercial activity to other permitted evidence. An account-level review can then direct research, prospecting, deal work, and expansion with more continuity than an isolated list.

Ask which signals are connected and what the agent may actually do in the proposed deployment.

See account-based selling for coordinating the buying group.

Frequently Asked Questions

Is a high pipeline coverage ratio enough to commit to the revenue target?

No. Coverage is nominal qualified pipeline divided by the target. It does not show whether opportunities are at viable stages, have buyer-supported close dates, or belong to the same period.

Compare the target with calibrated in-period expected revenue and inspect concentration in large deals.

How many active enterprise accounts should each SDR handle?

There is no universal number. Measure the time needed for research, buying-group outreach, responses, qualification, and handoff at the required quality.

Use observed account-cycle length and actual available hours to set concurrent slots, then recheck the result during the pilot.

Can new outbound pipeline fix a current-quarter forecast gap?

Only if comparable newly created opportunities can qualify, win, and close within the remaining time. Use an in-period yield from cohorts created at a similar point in the period.

If that yield is near zero, the new work may support a later quarter; report the current-quarter gap instead of overcommitting.

Does a stalled enterprise deal need to be removed from the CRM?

No. Keep the historical record. Review the reason for the stall, assign an owner and a dated next step, and change its in-period forecast contribution if the evidence no longer supports the close date.

Do not equate an old opportunity with a lost opportunity automatically.