usage-based-pricing
installsforks
How to install usage-based-pricing?
jonathimer/devmarketing-skills/usage-based-pricing
$npx -y skills add jonathimer/devmarketing-skills --skill usage-based-pricingDesign pricing models that developers understand, accept, and can predict. Trigger phrases: usage-based pricing, API pricing, metered billing, developer pricing, pricing page, cost calculator, pay as you go, pricing transparency, competitive pricing, developer billing
SKILL.md
| 1 | # Usage-Based Pricing |
| 2 | |
| 3 | Design pricing models that developers understand, accept, and can predict—without surprise bills or confusing metrics. |
| 4 | |
| 5 | ## Overview |
| 6 | |
| 7 | Developers are uniquely sensitive to pricing. They'll calculate unit economics, compare alternatives, and write blog posts about surprise bills. Usage-based pricing works well for developer tools because it aligns cost with value, but it can also create anxiety about unpredictable costs. |
| 8 | |
| 9 | The best developer pricing is predictable, transparent, and obviously fair. Developers should be able to estimate their bill before they commit. |
| 10 | |
| 11 | ## Before You Start |
| 12 | |
| 13 | Review the `/devmarketing-skills/skills/free-tier-strategy` skill to understand how free tiers connect to paid pricing. Your pricing model should feel like a natural extension of the free tier, not a completely different experience. |
| 14 | |
| 15 | ## Usage Metrics Developers Accept |
| 16 | |
| 17 | ### Good Metrics: Direct Value Correlation |
| 18 | |
| 19 | **API calls/requests** |
| 20 | - Developers understand what triggers a call |
| 21 | - Easy to monitor and predict |
| 22 | - Scales with actual usage |
| 23 | - Example: Stripe charges per transaction, Twilio per message |
| 24 | |
| 25 | **Compute time** |
| 26 | - Clear relationship to server costs |
| 27 | - Predictable for consistent workloads |
| 28 | - Fair for variable workloads |
| 29 | - Example: AWS Lambda per GB-second, Vercel build minutes |
| 30 | |
| 31 | **Storage** |
| 32 | - Simple to understand |
| 33 | - Easy to predict growth |
| 34 | - Clear cost driver |
| 35 | - Example: S3 per GB stored, databases per GB |
| 36 | |
| 37 | **Bandwidth/data transfer** |
| 38 | - Makes sense for CDN and hosting |
| 39 | - Can be surprising if not monitored |
| 40 | - Example: Cloudflare per GB, Vercel bandwidth |
| 41 | |
| 42 | **Active users (MAU)** |
| 43 | - Works for auth and user-facing tools |
| 44 | - Aligns with customer's growth |
| 45 | - Example: Auth0, Firebase Auth |
| 46 | |
| 47 | ### Problematic Metrics |
| 48 | |
| 49 | **"Compute units" or proprietary measures** |
| 50 | ``` |
| 51 | Bad: "1 CU = 0.25 CPU seconds at 1.5GHz equivalent with 256MB memory allocation" |
| 52 | Developers can't estimate usage. |
| 53 | ``` |
| 54 | |
| 55 | **Compound metrics** |
| 56 | ``` |
| 57 | Bad: "Charged per operation, where operation = read OR write OR delete, |
| 58 | multiplied by document size factor" |
| 59 | Too complex to predict. |
| 60 | ``` |
| 61 | |
| 62 | **Metrics that punish success** |
| 63 | ``` |
| 64 | Bad: Per-user pricing that penalizes viral growth |
| 65 | Developer's successful launch becomes a cost crisis. |
| 66 | ``` |
| 67 | |
| 68 | **Metrics with hidden multipliers** |
| 69 | ``` |
| 70 | Bad: "Per request, but each retry counts, and warming requests count, |
| 71 | and health checks count" |
| 72 | Actual usage is unpredictable. |
| 73 | ``` |
| 74 | |
| 75 | ### Metric Selection Framework |
| 76 | |
| 77 | | Metric | When It Works | When It Fails | |
| 78 | |--------|---------------|---------------| |
| 79 | | API calls | Discrete operations | Streaming, persistent connections | |
| 80 | | Compute time | Variable workloads | Idle resources still cost | |
| 81 | | Storage | Data products | Temporary/cache data | |
| 82 | | Bandwidth | CDN, media | Retry-heavy protocols | |
| 83 | | MAU | User-facing apps | Machine-to-machine | |
| 84 | | Seats | Collaboration tools | Individual developers | |
| 85 | |
| 86 | ## Pricing Page Clarity |
| 87 | |
| 88 | ### Essential Pricing Page Elements |
| 89 | |
| 90 | 1. **Price per unit, clearly stated** |
| 91 | ``` |
| 92 | $0.01 per 1,000 API calls |
| 93 | $0.10 per GB stored |
| 94 | $5 per team member |
| 95 | ``` |
| 96 | |
| 97 | 2. **Usage calculator** |
| 98 | ``` |
| 99 | Estimate your monthly cost: |
| 100 | API calls per month: [____] |
| 101 | Storage (GB): [____] |
| 102 | |
| 103 | Estimated cost: $XX/month |
| 104 | ``` |
| 105 | |
| 106 | 3. **Tier comparison table** |
| 107 | ``` |
| 108 | Free Pro Enterprise |
| 109 | API calls 10,000/mo 100,000/mo Unlimited |
| 110 | Storage 1GB 50GB 500GB |
| 111 | Support Community Email Priority |
| 112 | Price $0 $29/mo $299/mo |
| 113 | ``` |
| 114 | |
| 115 | 4. **FAQ answering real questions** |
| 116 | - "What happens if I exceed my limit?" |
| 117 | - "How do I monitor my usage?" |
| 118 | - "Are there any hidden fees?" |
| 119 | - "Can I set spending limits?" |
| 120 | |
| 121 | ### Pricing Page Examples |
| 122 | |
| 123 | **Excellent: Stripe** |
| 124 | - Simple percentage per transaction |
| 125 | - Clear calculator |
| 126 | - All fees visible |
| 127 | - Volume discounts transparent |
| 128 | |
| 129 | **Excellent: Cloudflare** |
| 130 | - Free tier generous |
| 131 | - Paid features clearly differentiated |
| 132 | - Per-feature pricing available |
| 133 | - Enterprise custom pricing framed simply |
| 134 | |
| 135 | **Poor patterns:** |
| 136 | - "Contact sales" for any pricing information |
| 137 | - Prices hidden until signup |
| 138 | - Complex unit definitions |
| 139 | - Multiple interdependent metrics |
| 140 | |
| 141 | ### Price Communication Principles |
| 142 | |
| 143 | 1. **Lead with simple cases** - Show the "typical" cost first |
| 144 | 2. **Reveal complexity gradually** - Edge cases in FAQ, not main pricing |
| 145 | 3. **Use real numbers** - "$47/month for a typical SaaS app" beats "$0.001 per request" |
| 146 | 4. **Compare to alternatives** - "50% less than AWS" (if true and provable) |
| 147 | |
| 148 | ## Cost Predictability and Caps |
| 149 | |
| 150 | ### Why Predictability Matters |
| 151 | |
| 152 | Developers fear: |
| 153 | - Unexpected month-end bills |
| 154 | - Usage spikes from bugs or attacks |
| 155 | - Being unable to explain costs to managers |
| 156 | - Services that punish success |
| 157 | |
| 158 | ### Providing |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
