Ramp deal

A ramp deal steps up over the term: $60,000 in year one, $90,000 in year two, $120,000 in year three. The customer commits to the whole schedule at signature.

Ramps exist because they resolve a real tension. The customer cannot justify full spend before rollout is complete; the vendor does not want to reprice annually and risk the renewal. A ramp locks in the growth path at signature and gives both sides a three-year plan.

What ramps do to your metrics

This is where ramps cause trouble, and it is not a billing problem — it is a reporting one:

• ARR has no single value for a ramped contract. Convention is to report the current contract year, which means the number changes at each step without any new sales activity.
• CARR is often quoted at the year-three rate, which overstates the present position considerably.
• Bookings capture total contract value at signature, so a ramp inflates the quarter it was signed in relative to the revenue it produces.
• Revenue recognition may not follow the billing schedule at all. Under ASC 606, where the same service is delivered throughout, revenue is generally recognised evenly across the term rather than in the stepped pattern — creating a contract asset in early years that unwinds later.

What they demand from the billing system

A ramp is a single subscription with scheduled future changes to price or quantity. Systems that cannot express that force one of two workarounds: three separate subscriptions (which destroys the continuity of the customer record and corrupts retention analysis), or a calendar reminder to edit the subscription manually each year (which gets missed).

Neither is acceptable at scale, and ramps are common enough in enterprise B2B that the ability to model them is effectively a requirement for moving upmarket.