Which Product Actions Should Become Billable Events?

Mapping actions to billable events: what to decide

Operational logs are full of useful signals, but not every signal belongs on an invoice. A workflow can generate a request, a retry, a cache hit and a result. Billing all four would charge for implementation details rather than the promised service.

Define the boundary in the offer first. If customers buy completed exports, the billing owner should observe completion and emit one authoritative event. Keep internal steps as cost or debugging telemetry unless the contract explicitly prices them.

An example with the numbers exposed

A video export takes three attempts before producing a usable file. Under completion-based pricing, one export is billed. Under compute-based pricing, all consumed compute might be billable. Both can be defensible, but the pricing page must make the distinction clear.

The mistake worth avoiding

Be careful with asynchronous completion. A queue accepting work does not prove that the customer received a result. If billing starts at acceptance, refunds or cancellations need a defined path.

A practical checklist

• Draw the workflow and mark its charging boundary.
• Assign one service ownership of the billing event.
• Define failed, cancelled and retried outcomes.
• Compare event totals with completed work during a pilot.