A national logistics company wants your fleet-tracking software for all 1,000 of its dispatchers. But its rollout plan is realistic: two regions in the first year, most of the country in the second, everyone by the third. Asking it to pay for 1,000 users from day one means charging for 600 licences nobody will use for a year. Selling only 400 users means renegotiating twice more and risking a competitor stepping in. A ramp deal sits between those two options.
What a ramp deal is
A ramp deal is a multi-year contract in which the quantity, the price, or both increase on a pre-agreed schedule. Everything is signed at once, so the customer commits today to the full path, but payments follow adoption rather than front-running it.
For the logistics company, the contract might specify 400 users in year one, 700 in year two and 1,000 in year three, at ₹6,000 per user per year.
| Contract structure | Year 1 | Year 2 | Year 3 | Three-year total |
|---|---|---|---|---|
| Flat, 1,000 users from day one | ₹60 lakh | ₹60 lakh | ₹60 lakh | ₹1.8 crore |
| Ramp: 400 / 700 / 1,000 users | ₹24 lakh | ₹42 lakh | ₹60 lakh | ₹1.26 crore |
| Flat, 400 users, renegotiate later | ₹24 lakh | ₹24 lakh | ₹24 lakh | ₹72 lakh committed |
The flat 1,000-user deal has the biggest headline number but may never get signed, because the customer’s finance team will object to paying for idle licences. The 400-user deal is easy to sign but commits only ₹72 lakh and leaves future growth to chance. The ramp locks in ₹1.26 crore of contracted value while asking the customer to pay only for what they plan to use.
Quantity ramps and price ramps
The example above is a quantity ramp. A price ramp keeps the scope fixed but steps up the price, for instance ₹40 lakh, then ₹50 lakh, then ₹60 lakh for the same product. Price ramps are used when the customer needs time to realise value, such as during a long implementation, or when the buyer has budget constraints in the current financial year but expects more next year. They are sometimes a way to give a first-year concession without permanently lowering the price.
Many real contracts combine both: more users each year, with the per-user rate also rising modestly once the initial discount period ends.
Why sellers like them, and why buyers do
For the seller, a ramp secures future growth contractually. It removes the expansion sale from next year’s to-do list, reduces the risk that a competitor wins the later phases, and gives more predictable revenue. It also makes the opening price conversation easier, because the year-one invoice is smaller.
For the buyer, a ramp aligns cost with rollout, which makes internal approvals easier. It also locks in pricing for later phases at today’s negotiated rate, which protects against list price increases. And it means the project sponsor does not have to fight for budget again in each year of the rollout.
How ramp deals complicate the numbers
Ramp deals create real ambiguity in sales metrics, and companies handle them in different ways. Three numbers matter:
- Total contract value (TCV): ₹1.26 crore, the sum of all committed years.
- Average annual contract value (ACV): ₹42 lakh if calculated as TCV divided by three years.
- Current ARR: ₹24 lakh at signing, because that is what the customer pays in year one.
Which of these counts towards a salesperson’s quota is a policy decision, and it changes behaviour. If reps are credited on TCV, they are pushed towards long, steep ramps whose later years may never materialise. If they are credited only on first-year ARR, they may have no incentive to negotiate a ramp at all. Many companies credit first-year value at signing and the ramp increases as they occur, or they credit the full ramp but cap the number of years counted. Finance teams also need clarity on whether future ramp steps are reported as contracted ARR or only when they start billing, since investors look at these figures closely.
Revenue recognition adds another layer. Under accounting standards such as Ind AS 115 and IFRS 15, revenue is recognised as performance obligations are satisfied, which can differ from the invoicing schedule. A ramp contract’s accounting treatment should be confirmed with finance rather than assumed from the invoice plan.
The risks worth watching
Adoption lag. If the customer’s rollout slows down, they will be contractually paying for users they have not deployed. That is exactly the situation that leads to unhappy renewal conversations. A ramp should match a realistic plan, not an optimistic one the sales team helped write.
Termination clauses. A three-year ramp is only as good as the customer’s ability to exit. If the contract allows termination for convenience after year one, the later steps are much less certain than the TCV suggests.
Back-loaded value. A very steep ramp, with most of the value in the final year, may look impressive on a booking report but carries the most risk. Some companies limit how steep a ramp can be without senior approval.
Disguised discounting. A ramp that starts very low and climbs to list price is sometimes a discount by another name. That is not necessarily wrong, but it should be visible and approved as such.
Used well, a ramp turns a multi-phase rollout into a single decision. Used carelessly, it books revenue the customer was never likely to pay.
Written by the RP Strativa Team. The company and figures in the example are illustrative.
Leave a Reply