The calculation
Take open opportunities where the source field is marketing and the close date falls in the period. Divide by the portion of the target marketing is accountable for. The result is a coverage multiple that belongs to one source and can be compared against that source's own conversion history.
Run the same calculation for outbound and partner. Three source-level ratios describe a quarter far better than one blended figure, because they reveal which engine is short while there is still time to react.
Why the blended ratio hides the problem
ORM finds that pipeline coverage of 3x to 5x is the standard range across its customers, with most landing near 3.5x. That range is a useful reference and a poor conclusion. A company can hold 4x total coverage and still miss badly when the pipeline is concentrated in a weak segment, aged past the point of closing, or sourced from channels that convert below plan.
Source-level coverage exposes exactly that. A total of 3.5x built from 5x outbound and 1.8x marketing is a different quarter from one built evenly, and only the split version tells you which team to fund. The argument against treating the blended number as an answer is laid out in why the 3x pipeline coverage rule is wrong, and it applies with more force once you separate sources.
Set the multiple from conversion, not convention
The required multiple for any source is the inverse of the rate at which that source's pipeline converts to closed won. A marketing-sourced pipeline converting at 25% needs 4x. One converting at 33% needs 3x. Applying one company-wide multiple across sources overfunds the efficient channel and lets the weak one hide.
Compute the conversion rate from at least four quarters of closed opportunities carrying the same source value, and recompute it whenever routing or qualification rules change.
Clean the numerator first
Coverage is only as honest as the pipeline inside it. ORM applies a twelve-month rule to opportunity aging and counts a change in stage, close date, or amount as meaningful activity. It also finds stale share varies by customer, with 10% or more of pipeline untouched for twelve months, and that only 20% of the value carrying in-quarter close dates on day one actually closes in the quarter.
Strip out the untouched opportunities before dividing, and check the average deal size in the numerator against what marketing-sourced deals actually close for. Once both corrections are made, source-level pipeline coverage becomes an input the sales forecasting process can use rather than a number that makes the quarter look covered.
Frequently Asked Questions
How do you calculate marketing sourced pipeline coverage?
Divide open marketing-sourced pipeline with close dates in the period by the portion of the revenue target marketing is accountable for sourcing. If marketing owns $4M of a $10M target and holds $12M of open sourced pipeline, coverage is 3x against its own goal.
Why measure coverage by source instead of in total?
Because sources convert at different rates. A total coverage ratio averages a high-converting source with a low-converting one and reports a number that matches neither. Coverage is only actionable when the multiple is set against the conversion rate of the pipeline it describes.
What coverage multiple should marketing sourced pipeline hit?
The inverse of its own historical conversion rate, not a borrowed rule. ORM finds 3x to 5x is the standard range across customers with most landing near 3.5x, but that range describes total coverage. A source converting at 20% needs 5x on its own, regardless of what the blended number says.
How does stale pipeline distort the ratio?
It inflates the numerator with deals that will not close. ORM sees stale share vary by customer, with 10% or more of pipeline sitting untouched for twelve months. Filter for activity before calculating coverage, or the ratio will report capacity that does not exist.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like marketing sourced pipeline coverage into prescriptive action for your team.
Schedule a Demo