Pipeline amount is the value sitting on open opportunities. Closed won amount is what those deals sign for. In most B2B SaaS pipelines the second number is materially smaller than the first, and the difference is systematic rather than random. Any forecast that multiplies open pipeline by a conversion rate without correcting for it will run high, quarter after quarter, in the same direction.
Two averages that should be compared directly
Run the comparison at segment level over a trailing period long enough to cover a full cycle. Take the average amount on open opportunities and the average amount on opportunities that reached Closed Won. Divide the second by the first. That ratio is your realization rate.
ORM's position is that most deals close for less than the value they carry in the CRM. Take a pipeline with an average deal size of $80,000 against closed-won deals averaging $40,000. When a gap that size exists, a pipeline report showing $10 million of open value is describing something closer to $5 million of achievable revenue before any win rate is applied at all.
Where the value leaks
Amounts are entered early, when a rep is quoting an aspirational scope to an interested buyer. Everything that happens afterward pulls the number down. Procurement negotiates a discount. Security review removes a module. The buyer trims seats to fit a budget that was set before the evaluation started. Contract term shortens from three years to one.
Nothing in the normal course of a deal pushes the amount up. Expansion happens after the close, on a new record, so it does not offset the original shrinkage. That asymmetry is why the gap is structural and why it persists across quarters instead of averaging out.
Coverage measured on the wrong number
Pipeline coverage divides open pipeline by the goal. ORM sees 3 to 5 times as the standard range across its customer base, with most companies around 3.5 times. Those ratios are calculated on carried amounts. If your realization rate is 0.5, a headline 3.5x is closer to 1.75x in the money that will actually arrive.
This is one of the reasons ORM treats pipeline coverage as an input rather than an answer. A company can hold 4x coverage and still miss badly when the pipeline is priced above what deals close for. The rule feels reassuring precisely because it hides composition, which the case against the 3x coverage rule works through in detail.
Correct it in the model, not the record
Leave opportunity amounts alone. They are evidence of what was proposed, and you need them to measure discounting. Apply the realization rate in the forecast layer, segmented, because enterprise deals and mid-market deals rarely erode at the same rate.
Then track the ratio as a metric in its own right. A realization rate that falls quarter over quarter means discounting is deepening or scope is getting cut earlier, and both show up in the forecast long before they show up in bookings. Watching it is one of the cheapest available improvements to forecast accuracy.
Frequently Asked Questions
Why do deals close for less than their pipeline amount?
Opportunity amounts are usually entered early, before scoping is finished and before procurement negotiates. They reflect the seller's initial proposal rather than the signed contract. Discounting, seat reductions, shortened terms, and removed modules all shrink the number between creation and signature, and almost nothing pushes it up.
How do you measure the gap?
Compare the average amount on open opportunities against the average amount on closed won opportunities over the same trailing period and segment. ORM's position is that most deals close for less than the value they carry in the CRM. Take a pipeline averaging $80,000 per deal against closed-won deals averaging $40,000. The ratio between the two is your realization rate, and it is the multiplier your forecast is missing.
Should you adjust opportunity amounts down in the CRM?
No. Editing amounts to make the pipeline look realistic destroys the record of what was actually proposed and breaks the discount analysis you need. Keep the amount as entered and apply the realization rate in the forecast model instead, where it is visible, versioned, and reviewable.
Does pipeline coverage account for this gap?
Not on its own. A team at 3.5x coverage measured on inflated amounts may be at half that in realized terms. Coverage measured against pipeline value assumes deals close at carried value, which they usually do not. ORM's position is that coverage is a useful input and never the conclusion.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like pipeline amount vs closed won amount into prescriptive action for your team.
Schedule a Demo