Subscription, Usage, and Hybrid
Subscription, usage-based, and hybrid pricing are not just billing switches. They allocate risk differently.
- Subscription gives budget certainty to the customer and leaves usage risk with the vendor.
- Usage-based pricing passes cost risk to the customer, along with bill uncertainty.
- Hybrid pricing fixes normal usage while charging separately for exceptional or high-value usage.
Customer View
| Dimension | Subscription | Usage-based | Hybrid |
|---|---|---|---|
| Budget certainty | High | Low | Medium to high |
| Entry friction | Medium | Low | Medium |
| Reconciliation complexity | Low | High | Medium |
| Perceived fairness | Light users may feel overcharged | Pay for what you use | Depends on overage transparency |
| Usage psychology | Already paid, so use more | Every use has visible cost | Normal use feels easy; heavy use gets surfaced |
Customers usually do not object to usage-based pricing itself. They object to bills they cannot anticipate or explain. With clear usage, thresholds, and forecasts, usage-based or hybrid pricing can work.
Vendor View
| Dimension | Subscription | Usage-based | Hybrid |
|---|---|---|---|
| Revenue predictability | High | Low | Medium |
| Margin stability | Depends on caps and user distribution | Higher | Higher |
| Sales complexity | Low | Medium to high | Medium |
| Product complexity | Medium, requires budget controls | Medium, requires bill transparency | High, explains two logics |
| Good stage | Early application, simple procurement | API / infrastructure, mature buyer | Most enterprise agent applications |
The most common vendor mistake is using subscription for sales simplicity without designing usage caps and overage behavior. The opposite mistake is moving to pure usage too early and blocking non-engineering buyers.
When Subscription Fits
Subscription works when:
- Task boundaries are clear and cost distribution is stable.
- Customers need fixed budgets and simple procurement.
- Value comes from repeat usage and team penetration.
- The product can enforce task caps, concurrency caps, and model routing.
Subscription should not mean unlimited use. It should mean the customer buys an understandable amount of work capacity.
When Usage-Based Fits
Usage-based pricing works when:
- Task complexity varies widely.
- Customers are engineering teams, platform teams, or mature enterprise buyers.
- Cost and value can both be explained by usage.
- Customers need to allocate cost by team, project, or business line.
The core UX is bill predictability: real-time usage, month-end forecast, anomaly alerts, budget thresholds, and exportable line items.
When Hybrid Fits
Hybrid pricing works when:
- You need a simple starting price but must support high-intensity customers.
- Most tasks are light, but some are very heavy.
- Customers want budget certainty but accept clear overage.
- The vendor needs to protect margin without blocking high-value usage too early.
Hybrid pricing must explain three things upfront:
- What normal capacity is included.
- When overage begins.
- Whether overage degrades, pauses, upgrades, or bills by usage.
Successful Tasks vs Started Tasks
Agent products should be careful with charging for started tasks. If customers pay for failed tasks, short-term billings may rise, but long-term trust falls.
More durable billing levels:
| Level | Good fit |
|---|---|
| Started task | Internal cost accounting; rarely a customer value unit |
| Successful task | Workflows with clear success criteria |
| Verified outcome | High-value, high-trust workflows, with higher review cost |
| Budget pool | Enterprise procurement across many task types |
Migration Strategy
Pricing models can change, but migration needs a path:
- Subscription to hybrid: notify early, grandfather existing users, and frame overage as added capacity rather than a price increase.
- Usage-based to subscription: use historical usage to recommend a monthly package and reduce budget uncertainty.
- Hybrid to enterprise contract: write usage, success criteria, overage, and review boundaries into the contract.
The earlier the product introduces overage and budget concepts, the easier later migration becomes.
Cross-section Connections
- Cost and budgets: economics
- Unit economics: metrics/unit-economics
- Tier packaging: tier-design