4of 6
Does your pricing unit match what customers value?
The easiest thing to measure isn’t always what customers want to pay for. Test whether your billing unit reflects meaningful value, produces predictable costs and supports sustainable delivery.
By the EWOR Team2 min read
API calls, pages and storage are easy to measure, but buyers may struggle to connect them to meaningful outcomes. When a billing unit feels arbitrary, using the product more can start to feel like a penalty.
The decision here is which unit to charge for, not how much to charge or when payment is due.
Ask what the buyer thinks they are paying for
Describe the event, workflow or ongoing capability the customer values. Then ask both the user and the budget owner how they recognise progress. Their answers may differ. The user may want to reduce repetitive work, while the budget owner needs a predictable expense linked to a clear operational benefit.
Consider a hypothetical invoice-processing product. Charging per page reflects a technical input. Charging per processed invoice may be easier for the buyer to connect to a business task. Charging per employee may feel familiar, but could discourage customers from giving occasional users access when they need it.
None of these units is automatically the right choice. An invoice is a useful candidate only if both sides agree on what counts as processed, including exceptions, retries and duplicates. A recognisable billing unit is a proxy for value, not proof that every billed event delivers a valuable outcome.
Calculate the bill on representative workloads
With permission to use the relevant records, calculate what each proposed billing unit would charge across representative customer workloads. Include quiet periods, typical activity and spikes. Label the results clearly as simulations, not actual invoices.
Ask buyers to explain how they interpret each bill. Can they predict the cost before using the product? Does doing more useful work lead to a proportionate increase in cost? Could a technical failure or repeated attempt generate charges without delivering additional value?
Record objections to the billing unit separately from objections to the price. Otherwise, a discount may disguise an unclear pricing model without fixing it.
A simple unit that buyers can audit may work better than a theoretically precise one they struggle to understand. However, predictable bills alone do not justify charging for capacity customers neither need nor understand.
Check what the meter encourages
Consider the behaviours the billing unit might encourage. Would users avoid collaboration, stop experimenting or move work outside the product to control costs? Would the business earn more when the customer's process becomes less efficient? If so, reconsider the unit or define its boundaries differently.
Next, compare the charges generated by different workloads with the resources required to deliver them. Even a customer-friendly billing unit can conceal costly exceptions.
Choose a candidate billing unit and document its counting rules in plain language. Test it with a limited group of customers, assessing whether buyers understand the charges, how they use the product and what it costs to deliver. A familiar-looking pricing page cannot answer these questions on its own.





No comments yet.
Be the first to comment on this signal.