First Principles: Price Waterfall Optimization

Your invoice price is what you agreed to charge. Your pocket price is what you actually collect. Most SaaS companies have never calculated the second number and are making revenue decisions based entirely on the first.

What It Actually Costs

The McKinsey work on price waterfalls from the 1990s showed that for industrial companies, the gap between invoice price and pocket price averaged 11-15%. Three decades later, in B2B SaaS, the same range holds. The mechanisms are different, the product is different, but the human behavior of granting concessions and not tracking their aggregate impact is unchanged.

For a $45M annual recurring revenue (ARR) SaaS business with a 13% pocket price gap, that is $5.85M in annual revenue that was priced, sold, and then quietly returned to customers through a dozen different adjustment mechanisms. At a standard ARR multiple of 6-8x, the equity value destruction is between $35M and $47M. Not from the business failing to grow. From the business growing while quietly giving back a predictable fraction of what it earns.

The Approach

Deconstruct assumption one: our pricing is what it says on the order form. The order form shows contracted value. It does not show payment timing adjustments, the early-pay discount you offered to accelerate a Q4 close, the three months of free implementation you bundled to neutralize a competitor, or the support credit from six months ago sitting as a line item in billing. Each of those is a price reduction. Together they constitute your real waterfall.

Deconstruct assumption two: concessions are a sales problem, not a pricing problem. Revenue Operations leaders often treat discounts as a sales behavior and price waterfall as a finance behavior. They are the same problem viewed from different functions. A payment term discount is a price reduction. A service credit is a price reduction. A free renewal month is a price reduction. When these are managed by different teams with no shared visibility, the total picture is invisible.

Deconstruct assumption three: the waterfall we have is a business necessity. Most deduction types were introduced for a specific reason at a specific point in the company's history. Pilot pricing was introduced to close a segment. Payment term discounts were introduced to accelerate a Q4. Service credits were introduced after a support incident two years ago. The question is not whether the deduction type was ever justified. It is whether it is still justified at its current scale and scope, and whether anyone is checking.

Where This Breaks

A $31M ARR data integration company had run a payment term discount program for three years. It offered a 3.5% discount for annual prepayment. The original intent was to improve cash flow predictability during a tight capital period. That capital constraint was resolved after a Series B eighteen months ago.

The program was still running. Nobody had reviewed it. By the time a new CFO pulled the numbers, 71% of customers were taking the early-pay option and the 3.5% discount had cost $2.2M in the prior fiscal year. The cash flow benefit of prepayment was worth roughly $160,000 in avoided credit facility interest. The company had been paying $2.2M to receive $160,000 in financial benefit, for three years, because nobody revisited the original decision.

The program was closed in one board meeting.

Next Actions This Week

List every discount, credit, or adjustment type that appears in your billing system. For each one, write down the original reason it was introduced, the date it was introduced, and whether anyone has formally reviewed it since. If any of your deduction types are more than 12 months old with no documented review, schedule that review this week.

Assess Your Pricing Health

Related: The Hidden Costs of Bad Price Waterfall Optimization | How to Measure the ROI of Price Waterfall Optimization