Pricing design
Packaging Metered Add-Ons Without Making the Base Plan Confusing
By the Orvlin team · · 2 min read
Metered add on pricing: what to decide
Add-ons can let customers buy advanced capabilities without making every account pay for them. The offer becomes difficult when a buyer cannot tell which ordinary action triggers an extra charge. Activation and visibility matter.
Define who can enable the add-on, when billing begins and whether usage has its own allowance. If the add-on changes the cost of an existing action, disclose the difference before the customer performs it.
A concrete scenario
A basic search is included, while an enriched search costs additional units because it returns external data. The interface can show the enriched option and its usage consequence. Silently routing a basic search through enrichment would violate the buyer’s understanding.
A detail teams often miss
A collection of tiny add-ons can turn a simple product into a negotiation spreadsheet. Use packaging when customers recognize meaningful differences, not merely because the billing engine can express more line items.
Before you put this into production
- Give each add-on a plain-language unit.
- Require appropriate approval for paid activation.
- Show a sample invoice with base and add-on usage.
- Define deactivation and in-flight work behavior.
Frequently asked questions
- Should add-ons share the main usage allowance?
- They can, but shared allowances must define conversion or eligibility rules. Separate meters are often clearer when the actions have very different economics.