Usage-Based Pricing

Design pricing models that developers understand, accept, and can predict.

What This Skill Covers

Usage metrics developers accept - Good vs problematic metrics, selection framework
Pricing page clarity - Essential elements, communication principles
Cost predictability and caps - Dashboards, alerts, cap implementation
Billing transparency - Detailed invoices, usage visibility, API access
Communicating value vs cost - Alternative comparisons, ROI calculators
Competitive pricing research - Landscape mapping, position options, testing

Key Principle

Developers are uniquely sensitive to pricing. They calculate unit economics, compare alternatives, and share horror stories about surprise bills. The best developer pricing is predictable, transparent, and obviously fair. Developers should estimate their bill before they commit.

Quick Reference

Good usage metrics:

API calls/requests
Compute time (GB-seconds)
Storage (GB)
Bandwidth (GB)
Active users (for user-facing tools)

Avoid:

Proprietary "compute units"
Compound metrics
Hidden multipliers
Metrics that punish success

When to Use This Skill

Designing new product pricing
Improving pricing page conversion
Reducing billing complaints
Adding spending caps and alerts
Competitive pricing analysis
Justifying premium pricing