A windfall clause is a compensation plan provision that reduces the commission rate on the portion of a deal above a stated size. It exists so that one contract several times larger than anything the plan modeled does not absorb a quarter of the variable compensation budget.
How the clause is written
The clean version names a dollar threshold and a reduced rate above it. A deal is paid at the standard rate up to the threshold, and the excess is paid at a lower rate. Total earnings still rise with deal size, which matters, because a hard stop turns a large opportunity into a reason to stop selling.
Two details make the difference between a provision reps accept and one they resent. The threshold has to be published before the plan year starts, and it has to apply automatically. A clause that is invoked case by case after a rep books the deal is a renegotiation, and reps respond by concealing large opportunities until they are nearly closed. That behavior removes the biggest deals in the business from pipeline review at exactly the point where visibility matters most.
Set the threshold off closed-won data
The most common mistake is setting the threshold against pipeline values. ORM finds that deals routinely close for less than the amount carried in the CRM. A pipeline carrying an 80,000 dollar average deal size against 40,000 dollars on closed-won business is the shape of the problem. A threshold calibrated to inflated pipeline figures sits far above where it needs to be and never protects anything.
Use the closed-won distribution instead. Look at the top few percent of deals actually booked over the past several years and place the threshold above that range. The clause should fire rarely. If it triggers on multiple deals a quarter, it is no longer a windfall provision, it is a cap, and reps will read it that way.
Watch what it does to forecasting
Any provision that changes a rep's economics on large deals changes how those deals appear in the system. A rep facing a reduced rate above a threshold has an incentive to split a large deal across periods or across accounts, which shows up as close date movement. ORM identifies a rep changing the close date as the strongest single signal of deal slippage, and a windfall threshold quietly manufactures that behavior when it is set too low.
Review the clause against your own booking history each planning cycle. If the threshold now sits below the size of a normal enterprise deal, it is distorting behavior rather than protecting the budget, and the effect will surface in your forecast accuracy before it surfaces in the compensation line.
Frequently Asked Questions
What is a windfall clause in a sales compensation plan?
It is a provision that applies a reduced commission rate to the portion of a deal above a stated threshold, so one unusually large contract does not consume the compensation budget. The rep still earns more on a bigger deal, but the marginal rate drops past the threshold.
Where should the windfall threshold be set?
Off your closed-won deal size distribution, not off pipeline values or off the largest deal anyone remembers. Set it high enough that it triggers rarely, because a threshold that catches ordinary large deals reads as a cap on good performance.
Does a windfall clause hurt seller motivation?
It does when the threshold is set too low or invoked after the fact. A published threshold that almost never triggers is accepted. A clause applied retroactively to a deal the rep already booked destroys trust in the whole plan and drives reps to hide large opportunities until late in the cycle.
What is the alternative to a windfall clause?
A decelerator that lowers the rate gradually above a high attainment level, or a deal desk review that sets bespoke terms before the deal is worked. Both keep the budget protected without the appearance of a cap applied at the moment of success.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like windfall clause into prescriptive action for your team.
Schedule a Demo