Why we nearly stopped billing by the token (and why we kept it)

Last spring we ran an experiment that most of our pricing team expected to fail. We took every customer who billed their own users by raw consumption — tokens, API calls, compute seconds — and asked a simple question: did the invoice line their customers saw match the reason those customers were paying?

For three out of four, it did not.

The meter is not the product

Metering is infrastructure. It is how you know what happened. Pricing is a promise about what something is worth. When the two collapse into one line item, customers start auditing your costs instead of evaluating your value.

"Nobody wakes up wanting four million tokens. They want the contract reviewed by Friday." — a finance lead at one of the platforms we interviewed

What we changed

We kept usage metering exactly as it was and added a second layer that maps raw events to outcomes a buyer recognises:

• Outcome units. A reviewed document, a resolved ticket, a reconciled account.

• Committed bundles. A predictable monthly amount with overage at a published rate.

• Credit ledgers. Prepaid balances that draw down in units the customer chose.

What it did to churn

Accounts that moved to outcome units cancelled 31% less often in their first two quarters. Support tickets about invoices fell by more than half. The metering pipeline did not change at all — which was the point.