What is Sticky Stairstep Pricing?
Written by Arnon Shimoni
✓ Expert
Last updated on:
What is sticky stairstep pricing?
Sticky stairstep pricing is stairstep pricing with a ratchet. Customers pay a flat fee per usage band, and once usage pushes them into a higher band, they stay at that price even if usage later drops. The steps only go up.
The "sticky" part is the whole difference from regular stairstep pricing, and it changes the economics for both sides more than it first appears.
How does it work? A worked example
A platform prices by monthly orders processed:
Step | Orders per month | Flat fee |
|---|---|---|
1 | Up to 1,000 | $200 |
2 | 1,001 to 5,000 | $600 |
3 | 5,001 to 20,000 | $1,500 |
Now follow one customer through 6 months:
Month | Orders | Regular stairstep | Sticky stairstep |
|---|---|---|---|
Jan | 800 | $200 | $200 |
Feb | 1,400 | $600 | $600 |
Mar | 4,900 | $600 | $600 |
Apr | 6,200 | $1,500 | $1,500 |
May | 3,800 | $600 | $1,500 |
Jun | 4,100 | $600 | $1,500 |
Total | $4,100 | $5,800 |
One month above 5,000 orders and the sticky customer is repriced permanently. Over this half year they pay 41% more than under regular stairstep, for identical usage.
Why would a vendor use it?
The honest answer: revenue stability without a negotiation. A minimum commit achieves the same thing contractually, but commits are sold and negotiated deal by deal. The ratchet is self-executing. Every customer's floor rises automatically as they grow, and seasonal dips stop showing up as revenue dips.
There's also an operational argument. Downgrade logic is where stairstep billing gets messy: bounce protection, trailing averages, retroactive adjustments. Sticky pricing deletes all of it. The current step is a single monotonic value per customer.
And it mirrors how vendor costs sometimes behave. If serving a customer's peak forced you to provision capacity, the argument goes, the peak is what you should price on.
When does it backfire?
The ratchet transfers all usage risk to the customer, and customers who understand the model respond to it:
Customer response | Effect |
|---|---|
Throttling below the boundary | Growth you priced for never happens |
Disputing the peak month | "That was a migration, a spike, a mistake" becomes a recurring support ticket |
Churning at renewal | The price reflects January's peak, the usage reflects June's reality |
Sticky stairstep works when usage genuinely trends upward (companies rarely process fewer orders every year) and fails when usage is cyclical or spiky. Pricing a seasonal business on its peak month is a churn plan with extra steps.
The softer variants are worth knowing: reset the ratchet annually at renewal, or require 2-3 consecutive months above a boundary before repricing. Both keep most of the revenue stability while removing the single-spike injustice.
What does it require from billing?
The billing system has to track each customer's high-water mark as durable state instead of recomputing the band from current usage. It also needs an override path: sales will make exceptions (a spike forgiven, a ratchet reset as a save play), and if exceptions live in spreadsheets, the invoice and the promise drift apart. That's how revenue leakage starts in ratchet models, in both directions.
Solvimon models stairstep and sticky stairstep as native price structures with the high-water logic in the ledger, so exceptions are configuration changes with an audit trail. See flexible pricing.
FAQ
Is sticky stairstep pricing the same as a ratchet clause?
Same mechanism, different layer. A ratchet clause lives in a contract and gets enforced by humans. Sticky stairstep pricing builds the ratchet into the price structure itself.
Do customers accept it?
When it's disclosed clearly and the steps are generous, yes, because the flat fee is still predictable. When they discover it from an invoice after a one-month spike, no.
How is it different from a minimum commit?
A minimum commit is agreed up front for a term. The sticky step is discovered through usage and permanent by default. Commits are also usually paired with better rates. The ratchet gives nothing back.
Can the ratchet reset?
Only if you design it in: annual resets at renewal are the common compromise. Decide before launch, because retrofitting a reset policy means repricing existing customers.
Related
Stairstep pricing: the base model, without the ratchet
Minimum commit: the contractual route to the same floor
Usage-based pricing: the hub term
Revenue leakage: what unmanaged exceptions turn into
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
