A price waterfall is a stepped chart running from list price down to pocket price, with one bar for each thing that reduced it. The pocket price is what you actually keep. The method comes from pricing consulting, where the recurring finding is that executives can state their list price precisely and cannot state their pocket price at all.
The two halves, and why only one is visible
| Deduction | Where it lives | Visible on an invoice |
|---|---|---|
| List to invoice discount | The quote and the order. | Yes. This is the number everyone argues about. |
| Volume and tier breaks | The price book. | Usually. |
| Payment terms | The contract. Thirty days against ninety is a real cost of capital. | No. |
| Rebates and co-op | Paid later, often from a different budget. | No. |
| Service and support concessions | Given during the deal, delivered by another team. | No. |
| Returns, credits and write-offs | After the fact, in finance. | No. |
Everything below the second row is off-invoice, which means it is granted by one person and paid for by a budget that person does not hold. That is precisely why it accumulates: the cost is real and lands somewhere else.
Why the invisible half is usually the larger one
On-invoice discounting is policed. It appears in the quote, somebody approves it, and it shows up in reporting as a percentage that leadership watches.
Off-invoice concessions have none of that. Extending payment terms to win a quarter does not look like a discount to anyone in the room, and nothing in the deal record marks it as one. Promising extra onboarding is a commitment of somebody else's capacity. Each is defensible on its own and none is counted, so the only way to see the total is to build the waterfall and go looking.
Building one when the data is incomplete
The data will be incomplete. Build it anyway, on a sample, and mark the estimates as estimates.
- Take twenty to thirty closed deals across segments rather than the whole book. The shape appears quickly and the full reconstruction does not pay for itself at this stage.
- For each deal, work down the list and record every deduction with its source. Where a number has to be estimated, record that it was.
- Keep the estimates visibly separate. A waterfall that mixes measured and guessed values, with no way to tell which is which, will be argued with rather than acted on.
- Compare deals against each other, not against a target. The useful output is the spread. Two similar customers with very different pocket prices is a finding; an average pocket price is a statistic.
What it changes once you have it
The first change is which deals look good. Ranking by revenue and ranking by pocket margin produce different lists, and the gap between them is the reason some teams grow revenue and not profit.
The second is what gets rewarded. If sellers are paid on revenue or on invoice discount, every off-invoice concession is free to the person granting it. That is a specification problem rather than a discipline problem, and the waterfall is what makes it visible enough to fix.
The third is approval design. Once you know which concessions actually cost the most, approval thresholds can sit on those rather than on the invoice discount alone, which is what a deal desk is for.
Where it sits against revenue leakage
They are adjacent and not the same. Leakage is money you were entitled to and did not collect, which is a failure of execution. The waterfall measures money you agreed to give away, which is a pricing decision. The waterfall is how you find out whether you meant to.
When not to build one
With a single list price and no negotiation. Pocket price equals list price, and the chart is one bar.
When nobody can change the answer. This produces findings about pricing policy, contract terms and compensation. If none of those are movable this year, you have commissioned a document.
Before the off-invoice items are recorded anywhere. You can still build a sample by hand, and you cannot monitor it. Know which of those you are buying before promising anyone a dashboard.
Questions people ask
What is a price waterfall?
A stepped view from list price down to pocket price, one bar for each deduction. Pocket price is what the business actually keeps.
What is pocket price?
What remains after every deduction, on-invoice and off. Most companies can state list price exactly and pocket price not at all.
Why does the waterfall usually surprise people?
Because the off-invoice half is larger than expected. Payment terms, rebates, concessions and credits are granted by one person and paid for by a budget somebody else holds.
How do I build one without complete data?
Sample twenty to thirty deals, record every deduction with its source, and mark estimates as estimates. The spread between similar customers is the finding, not the average.
Is a price waterfall the same as revenue leakage?
No. Leakage is money you were owed and failed to collect. The waterfall measures money you agreed to give away, and shows whether you meant to.
Or skip the search
Want the person who owns it after it ships?
If the work is a standing obligation rather than a bounded project, tell me which system you want built first. You get example profiles and a call with your pick before anything starts.
Placement runs through AYTalent. Engineers are employed and trained on the bench before they start with you.