B2B pipeline ROAS: forecasts are not sales revenue

Define the outcome before dividing

Choose whether your numerator contains unweighted open opportunities, a probability-weighted forecast, closed-won contract value, or recognized revenue. These measures answer different questions. Write the definition next to the ratio, and use the same acquisition cohort for its advertising cost.

An illustrative pipeline example

Assume $2,000 in advertising generates two distinct opportunities worth $10,000 each. Unweighted pipeline divided by spend is $20,000 / $2,000 = 10×. If you use an illustrative 20% closing probability for each, weighted pipeline is $10,000 × 20% + $10,000 × 20% = $4,000, or 2× spend. That probability is an assumption for this example, not an industry benchmark.

If neither opportunity has closed, the example has no realized sales revenue yet. Do not report the 10× pipeline ratio as realized ROAS. If one closes, remove it from the open-pipeline subtotal before adding a separate closed-won subtotal.

Avoid counting every sales stage as another sale

A lead can become a qualified lead, meeting, opportunity, and customer. Summing a monetary value assigned to every stage can repeatedly count the same underlying deal. Use a stable opportunity identifier, preserve stage history, and choose one reporting rule for the snapshot.

Revisit forecast assumptions

When enough outcomes mature, compare actual wins with the probabilities used. Segment only when there is enough evidence to support the distinction. Keep the original forecast and later outcome visible instead of rewriting the past forecast to match what happened.

Finally, sales revenue does not reveal profitability. Delivery costs, sales commissions, onboarding, and the time to payment can make a high pipeline ratio insufficient for a budget decision.

Examples are illustrative, not client results or benchmarks. The calculations use the inputs shown; real-world decisions depend on your records and assumptions. Report a correction.