Choosing a billable unit that customers can explain

A startup may price by token, task, document or completed transaction. These units can produce very different incentives. The most technically convenient measure is not necessarily the one that matches customer value.

Start with the purchasing conversation

Ask the buyer to explain the unit to a colleague who has not seen the product. If that requires a long technical lesson, the package may create friction before implementation begins.

Stripe’s usage-billing documentation describes charging according to consumption. It does not determine which consumption measure makes sense for a particular business. That remains a product and commercial decision.

For an illustrative document-processing startup, charging per uploaded file could penalise customers who must resubmit unreadable documents. Charging per accepted record might be easier to connect to value, but the supplier must define acceptance and account for failed processing costs.

Define disputed events before launch

Specify how duplicates, retries, cancellations and partial results affect the count. Give customers a way to inspect recorded usage. A monthly total without an explanation can turn a small invoice into a difficult support case.

Test whether the unit behaves consistently across customer sizes. A measure that suits a single-site company may become unpredictable when many branches share an account.

Keep the explanation aligned with the actual meter. Sales should not promise “successful tasks only” while engineering counts every attempt. Reconciliation requires a common definition, not better invoice wording.

Stress the unit with realistic behaviour

Replay authorised example workloads and calculate what customers would pay. Include unusually busy periods, failed transactions and changes in workflow. These are sensitivity tests, not forecasts of guaranteed revenue.

Ask whether customers can control consumption without undermining the product’s purpose. If ordinary use creates unexpected charges, consider allowances, alerts or a different unit.

Write a sample invoice using a realistic, clearly illustrative workload and ask the customer to reconstruct the charge. If their calculation differs, investigate the definition before negotiating the rate. A price that requires repeated supplier intervention to explain is unlikely to become easier to manage as usage grows.

GAT’s SaaS go-to-market guide connects packaging to the customer. A billable unit is part of that connection: it should make the relationship between use, value and payment understandable before the first invoice arrives.