Sit down for a moment, because usage-based pricing looks simple and then quietly rewires a lot of things. The idea: instead of charging a fixed fee per user per month, you charge for what the customer actually consumes. Cloud storage per gigabyte, an SMS gateway per message, a payments platform per transaction, an API per thousand calls.
Why would a vendor do this? Because the price tracks the value the customer gets. A small customer pays little and can start easily. A big one pays more as it grows, without anyone renegotiating a contract. That “start small, grow automatically” shape is attractive.
Three ways to charge
Let us use an invented messaging platform and look at one customer over three months.
Pure pay-as-you-go. The price is ₹4 per 1,000 messages. The customer sends 1.8 crore messages in month one, 2.6 crore in month two and 3.4 crore in month three. The bills are ₹72,000, ₹1,04,000 and ₹1,36,000, a total of ₹3,12,000. Nothing is committed, so the customer can leave any time.
Commit plus overage. The customer commits to 2.5 crore messages a month at a discounted ₹3.6 per 1,000, a fixed ₹90,000, and anything above is charged at ₹4.4 per 1,000. The three bills are ₹90,000 (usage was only 1.8 crore, but the commitment is paid regardless), ₹94,400 (₹90,000 plus 10 lakh extra messages at ₹4.4 per 1,000, which is ₹4,400) and ₹1,29,600 (₹90,000 plus 90 lakh extra messages, which is ₹39,600). Total ₹3,14,000, almost identical to pure usage over the quarter, but shaped differently.
Seat-based, for comparison, would have been a flat number each month regardless of messages, which the customer might find unfair in quiet months and the vendor might find unfair in busy ones.
Why vendors like a commit
Look at month one. The vendor’s revenue is ₹90,000 under commit and ₹72,000 under pure usage. The commit protects a floor. It also lets the vendor plan capacity and commit to its own suppliers, for example cloud infrastructure that is cheaper if reserved. For the customer, the commit buys a lower unit price, and in return it takes on the risk of paying for unused volume. The sweet spot for the commit is a level the customer is very likely to exceed. Set it too high and the customer resents wasted spend and leaves at renewal; too low and the vendor gives away a discount for no real commitment.
What it does to the business
- Forecasting becomes harder. Revenue depends on customer behaviour, including seasonality. An e-commerce customer’s messages spike around festival sales and drop after. Forecasts need usage trends, not just contract values.
- Annual recurring revenue gets fuzzy. Is ARR the commit, the trailing three-month average, or the current month times twelve? Pick a definition, publish it and use it consistently, otherwise investors and your own leaders will be comparing different things.
- Net revenue retention swings. Expansion happens without a sales conversation, which is good, but contraction does too, with no renewal event to warn you.
- Billing surprises cause fights. A customer whose bill doubles because of a bug on their side will be angry with you. Usage alerts, spending caps and clear dashboards are not optional extras.
What it does to the sales team
If a rep is paid on the contract signed, what do they earn when the customer signs a small commit and then grows tenfold by itself? Many companies split the plan: pay on the committed amount at signature and a smaller share on consumption growth, or hand growth to an account manager. The pay plan must match the pricing model, otherwise reps will sell the largest possible commit that customers will not use, and the next year’s churn will show it.
The sales conversation changes as well. Instead of “how many seats do you need”, the question is “what will your volume be, and how will it grow?” Buyers often cannot answer, so good sellers bring ranges and past examples from similar customers and structure ramps and review points.
When it does not fit
Usage pricing needs a unit of consumption that clearly tracks value and that customers can measure and predict. If the unit is something obscure, buyers feel they are being billed for the vendor’s internal metrics. And customers with tight annual budgets, common in Indian public sector and many large enterprises, often want a fixed, approved number, which is why commit structures or capped annual packages are popular there. There is no universally right answer; it depends on the product and the buyer’s finance process.
Figures and names in the examples are illustrative.
Leave a Reply