Revenue Metrics for Sales Leaders
Bookings, cARR, ARR, MRR, run rate. Used interchangeably, they distort the forecast and reporting. Here is how the KPIs map to seat-based, usage-based, and pay-per-results pricing, and where the misuse usually starts.
You hear bookings, cARR, ARR, MRR, and run rate used as if they meant the same thing. They do not. Using them incorrectly does not just confuse a board or investor deck. It distorts the forecast, the quota, the commission plan, and the story leadership tells to stakeholders.
The biggest misuse is calling non-recurring revenue "ARR" or "cARR" because it sounds better. Pressure to show progress and compete with other companies boasting with their numbers collides with the complexity of pricing models, and definitions blur. The rep, the CRO, and the CFO end up running on different numbers.
This piece is a quick reference for sales leadership managing revenue reporting across three pricing schemes: traditional seat-based SaaS, transactional or usage-based consumption, and emerging pay-per-results business models. The metrics are the same. The pricing model decides which of them applies.
MRR = monthly recurring revenue.
ARR = the same, annualised.
cARR = contracted ARR, signed recurring revenue, whether or not it has started billing.
Bookings = total new business closed in a period.
Run rate = monthly volume projected forward.
Pricing Model Sets the Metrics
Start here. The pricing model decides which metrics are valid in the first place.
Seat-based SaaS: cARR, ARR, and MRR all apply. The customer signs a contract that specifies what they pay each year. Predictable.
Usage-based, with a committed minimum: cARR and ARR apply only to the minimum. Overages are recognised revenue, not ARR.
Pure usage-based or pay-per-results, no minimum: No cARR. No ARR. Track recognised revenue and run rate.
If there is no contractual floor, there is no ARR.
The frequent misuse is treating expected results as if they were committed. They are not.
Today, a notable part of deals are hybrids: a platform fee plus usage overages, a seat-based subscription with consumption above a floor, a base licence with AI-powered pay-per-result modules. The rule does not change. Each component maps to its own metric. The recurring part counts as ARR. The variable portion is recognised as revenue when consumed or results delivered.
Getting the definitions right is the first move. The next ones, from sales forecasting and pipeline reviews to quota design and revenue management, sit in the GTM Club Newsletter. Monthly, practical, no hype.
Bookings vs cARR
These two get easily confused. They measure different things.
An example to anchor it.
Seat-based SaaS: A 50k€ deal for ten seats at 5 000€ per seat per year, one-year term. Bookings = 50k€. cARR = 50k€. Same number, different reasons.
Transactional with minimum: A customer commits to a 60k€ per year floor and pays per consumption above it (think of sending on SMS or paying per call minutes). Bookings count the floor. cARR = 60K€. Overages are not in either.
Transactional without minimum: Same product. The customer signs a contract with no volume commitment (and pays per message or minute). cARR = 0€. Bookings = 0€ unless there is a one-off fee. Your forecast is based on customers' indicated usage and what usage trends indicate, not on any signed commitments.
Pay-per-results: A customer service AI agent priced at 1€ per solved ticket, no minimum. The customer expects 4 000 tickets per month. That 48K€ is a forecast. Not a booking. Not cARR.
Expected results are not contracted revenue.
A note on pilots. Rolling pilot revenue into cARR makes the number look stronger than it is. Even when a pilot has a fixed fee, flag it separately as the churn risk is high. Better to say: 100K€ cARR, 60K€ from full contracts, 40K€ from pilots.
ARR and MRR
Where bookings and cARR look forward, ARR and MRR look at the present.
It is not money invoiced. It is not money collected. It is not cash. It is not revenue from overages or one-off events. If the underlying revenue is not contractually recurring, it is not ARR.
Seat-based SaaS: A ten-seat contract live, billing 4 167€ a month, equals 50K€ ARR. The customer pays for what they signed. Predictable.
Transactional with a 60K€ minimum: ARR = 60K€, the recurring committed floor. Last month's actual: 1.2M messages = 72k€ invoiced. The 12K€ overage is recognised revenue, not ARR or MRR. Do not add overages to either. Do not annualise this month's invoice and call it ARR.
Transactional without minimum: ARR = 0€. Last month: 600K messages at 0.06€ each = 36k€ recognised revenue. Track separately as usage revenue.
Pay-per-results, no minimum: ARR = 0€. Last month: 3 200 solved tickets = 3 200€ recognised. Revenue is recognised as results are delivered. There is no recurring base.
The money you invoiced this month is not automatically ARR. Annualising the current month's invoice (i.e., multiplying by 12 and calling it ARR) is the classic mistake. On the other hand, you can have signed, contracted recurring revenue that has not yet been invoiced. Think of a 12-month contract that bills monthly: 50K€ ARR exists from day one, but only 4 167€ shows on the first invoice.
Invoiced is not recurring. Recurring is not always invoiced. Track both.
Revenue is recognised when the so-called performance obligation is satisfied. For usage-based or outcome-based pricing, that means payment occurs as usage or results occur. For an annual contract in traditional SaaS, you recognise revenue each month when access to your service is "delivered", not when the invoice is sent.
Run Rate for Non-Recurring
Even without a recurring base, leadership still needs a forward number. Run rate earns its keep here.
Transactional, no minimum: Last month, 600k messages at 0.06€ = 36k€ recognised. This month, 900k expected (YoY growth plus a new customer) = 54k€ forecast. Next month, holiday spike, 1.5M messages = 90k€ forecast. The number moves with the customer's business.
Pay-per-results: 3 200 tickets last month, 4 000 expected this month, 4 500 next month. Forecast confidence is low because the customer's volume drives the metric, not your contract.
A run rate is based on a moment in time. Do not dress it up as a commitment. Forecast it using YoY trends, customer ramp, and seasonality.
Quotas and Sales Commission
This part is not governed by an accounting standard. Practice varies widely. The patterns below are common, not rules. A bit of over-simplification here too. Don't treat these as any standard.
Seat-based SaaS: Quota = cARR. Commission paid on the signed contract. A 50k€ ten-seat deal credits 50k€. Companies can pay commissions upfront, as customers are contractually obligated to pay the contracted price for the service. Commission models may have clawback terms if contracts are not fulfilled.
Transactional with minimum: Quota credit equals the committed minimum. Commission can be paid on the floor at signature, with overages added when realised. A 60k€ minimum plus 15k€ overages in year one equals 60k€ commission upfront, plus 15k€ commission as an overages bill.
Transactional without minimum or pay-per-results: No floor to credit upfront. Two common models:
- Pay commission on actual recognised revenue. Payment can be monthly, quarterly, or even annually. (More common.)
- Pay on the annualised expected value, with a clawback if usage falls short.
If a rep expected 4,000 tickets a month and usage actually lands at 3,000, model 1 pays based on 3 000€ a month. Model 2 pays a commission of 48K€ annually, and claws back the gap. Clawbacks are not ideal for motivating the sales team, so use them with caution.
Using Terms Correctly Favours You
Use the right term, and the forecast tightens. Use the wrong one, and you are selling a number nobody can hit. Hybrids do not break the framework. They just force you to apply it twice.
| Metric | Seat-Based SaaS | Transactional with 60K€ minimum | Pure Transactional / Pay-Per-Results |
|---|---|---|---|
| Bookings | 50K€ | 60K€ minimum (services and overages excluded) | 0€ (or one-off fees only) |
| cARR | 50K€ | 60K€ (floor only) | N/A. No recurring commitment |
| ARR / MRR | 50K€ ARR / 4.2K€ MRR | 60K€ ARR (the floor) | N/A. Track as recognised revenue |
| Recognised revenue | 4.2K€ per month as delivered | 5K€ per month minimum, plus overages as used | Variable, as usage or results occur |
| Run rate | Equals ARR | ARR plus trended overages | Trend-based forecast only |
| Forecast confidence | High | Medium (floor solid, overage variable) | Low |
| Commission base | cARR upfront | Floor upfront, overages on actual | Actual revenue or forecast with clawback |
Adding a minimum commitment to a usage-based deal makes the contract more forecastable. The floor is what the seller can build a business on. Once the floor is right, the next question is what happens to that revenue after the customer is on board: how it expands, how it leaks, what stays. Net Revenue Retention covers the first. Churn covers the second.
Get the definitions clean. The results follow.
