Pricing Strategy Lab
Moving a developer API from flat to usage-based pricing
Latest conversation
Updated 5h ago
Context: the API is $49/mo flat, 62% gross margin, 4.1% monthly churn. We're evaluating usage-based pricing.

Usage logs: the top 10% of accounts generate 71% of all calls. Flat pricing is heavily subsidizing power users.

Then a hybrid makes sense — a platform fee plus metered overage. Protects margin without scaring off small teams.

Comparable public pricing pages (Twilio, Resend, Algolia) pair a free allowance with per-unit overage.

Modeling $29 base + $0.80 per 1k requests above 50k. Projected: +18% revenue, margin rises to 71%, ~6% of accounts see a higher bill.

Partly. 40 of them are on annual contracts. I'd grandfather annual accounts for 12 months and give monthly accounts 60 days' notice.

Pair the change with a visible usage dashboard. Customers accept metered pricing when they can see and predict it.