In this article

Eight people process 40,000 pages a month. Twenty people process 2,500. Which team should pay more?

There is no answer until you decide what the product charges for. A seat price favors the small, high-volume team. A processing price favors the larger team with lighter demand. Neither choice is merely a different way to display the same offer. It changes who finds the product economical and which behavior customers try to avoid.

The pricing metric is the billable unit: a seat, a transaction, a completed job, or another defined quantity. Choose it before getting absorbed in whether the price should end in a nine. A discount can lower an uncomfortable bill; it cannot explain why the customer is being charged for the wrong thing.

Compare the unit with the work customers value

List a few serious candidates using concrete workflows. For a hypothetical document-processing service, customers may care about usable records delivered to their accounting system. The service incurs costs through processing, storage, exceptions, and support. Those quantities overlap imperfectly.

Seats are easy to explain, but occasional reviewers may avoid joining if each invitation increases the bill. Pages processed may track part of the operating cost, while charging more for long or badly scanned documents. Completed records are closer to the desired output, but “completed” requires a definition both sides can defend.

Stripe’s guide to usage-based SaaS pricing recommends a metric connected to customer value that is understandable and measurable. Apply that as a starting test, not as a reason every product must adopt consumption pricing. Predictable access to a service can itself be part of what customers buy.

Use real workload distributions when available. An average account can conceal the customers for whom the model breaks: a tiny team running heavy automation, a large group that only reviews occasionally, or a seasonal business with a short burst of demand.

Illustrative workloadSeatsPages processed per monthUsable records per month
Small operations team32,0001,500
Broad review group202,5001,800
High-volume team840,00030,000

These invented workloads show how differently units distribute the bill. They do not establish which metric buyers prefer or which price covers the service’s costs.

Define the edge cases before promising a simple unit

“Per completed record” sounds clear until an invoice is corrected, duplicated, or split into several records. The commercial definition needs to survive these ordinary events.

Decide what creates a billable record, when the count becomes final, and how corrections affect it. Does a failed processing attempt count? Does reprocessing the same document after a product error create another charge? If a customer deletes and uploads an item again, is it the same job?

Avoid making the user discover these rules through an invoice dispute. Put a concise explanation beside the usage count and provide enough detail to reconcile a bill. The wording in the product, contract, and billing system should describe the same event.

Outcome-based units need particular care. A delivered record can be verified within the service. “Hours saved” depends on a counterfactual: how long would this customer have spent without the product? “Revenue generated” may involve several systems and influences. The closer the unit gets to a broad business result, the more agreement and measurement it may require.

A proxy that everyone understands can be commercially better than a theoretically perfect outcome that neither party can audit.

Watch what a budget-conscious customer would stop doing

For each candidate, imagine a reasonable customer trying to reduce the bill. This reveals the incentives more quickly than a pricing survey asking which model sounds fair.

A seat charge may encourage shared logins or exporting work for external review. A storage charge may encourage deleting useful history. A per-run charge may lead people to delay an automated check until the end of the week. Some restraint is sensible cost management. It becomes a product problem when saving money undermines the workflow the service was designed to support.

Stripe’s pay-per-use pricing discussion addresses the importance of choosing a metric and pricing structure that do not discourage valuable use. In practice, changing the structure may solve a problem without abandoning the unit. Included quantities, volume tiers, or a base subscription can change the tradeoff.

Each addition has a comprehension cost. A model with seats, records, storage credits, and separate automation allowances may cover the internal cost ledger beautifully while leaving buyers unable to predict the bill. Keep internal cost accounting more detailed than the customer-facing offer where possible.

Give customers control over variable consumption

Predictability depends partly on who creates usage. A customer pressing “Process file” can see a discrete decision. An integration receiving documents overnight can create demand while nobody is watching. A third party may trigger much of it.

Design the controls with that distinction in mind. Show current usage and what remains included. Explain what happens at a limit: work pauses, an administrator approves more capacity, or overage charges begin. A spending alert is not a spending cap, and the product should not blur the two.

Account for delayed metering. If usage is not reflected immediately, a displayed estimate should not imply it is a final bill. Define which period receives late events and how adjustments appear. Billing reliability becomes part of the product’s usefulness when customers are deciding whether to trust automation with a budget.

Ask buyers to calculate a bill

A useful comprehension test gives a buyer the proposed rules and a recent representative workload. Ask them to estimate the charge and explain which actions increase it. Their mistakes reveal ambiguities that a favorable reaction to the pricing page may miss.

Then simulate the proposed model across existing workload profiles. Inspect both customer bills and service costs, including unusually expensive cases. A metric can be easy to understand and still be uneconomic at the offered rate. It can also produce attractive revenue while creating unacceptable volatility for buyers.

If changing an existing model, examine who experiences the biggest change and why. A team whose bill rises because more colleagues review the same output will need a different explanation from one processing substantially more work. Transition terms are part of the offer, not an afterthought to a new pricing page.

Before approval, have product, billing, and a customer-facing colleague independently calculate the same sample invoice. If they produce different answers, the unit is not ready to sell.

Sources

Something we should clarify?

Suggest a correction