菜单
Design 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
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor comparison", "competitive content", "comparison table", "migration guide", "switch from [competitor]", "compare to [competitor]", "alternative to"
Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: "API onboarding", "time to first API call", "TTFAC", "developer onboarding", "first API call", "auth simplification", "sandbox environment", "interactive docs", "try it now", "API playground", "developer activation", "onboarding friction"
Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features. Trigger phrases: "changelog", "release notes", "product updates", "version communication", "breaking changes", "deprecation notice", "what's new", "release communication", "developer updates", "API versioning", "migration announcement"
When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums. Trigger phrases include "developer community," "Discord server," "Slack community," "community strategy," "community engagement," "community moderation," "community growth," or "community management."
Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: "competitor analysis", "track competitors", "competitive intelligence", "competitor research", "what are competitors doing", "competitive landscape", "competitor features", "competitor pricing", "battlecard", "competitive battlecard", "compete against", "vs [competitor]"
When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."
| name | usage-based-pricing |
| description | Design 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 |
| metadata | {"version":"1.0.0"} |
Design pricing models that developers understand, accept, and can predict—without surprise bills or confusing metrics.
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.
The best developer pricing is predictable, transparent, and obviously fair. Developers should be able to estimate their bill before they commit.
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.
API calls/requests
Compute time
Storage
Bandwidth/data transfer
Active users (MAU)
"Compute units" or proprietary measures
Bad: "1 CU = 0.25 CPU seconds at 1.5GHz equivalent with 256MB memory allocation"
Developers can't estimate usage.
Compound metrics
Bad: "Charged per operation, where operation = read OR write OR delete,
multiplied by document size factor"
Too complex to predict.
Metrics that punish success
Bad: Per-user pricing that penalizes viral growth
Developer's successful launch becomes a cost crisis.
Metrics with hidden multipliers
Bad: "Per request, but each retry counts, and warming requests count,
and health checks count"
Actual usage is unpredictable.
| Metric | When It Works | When It Fails |
|---|---|---|
| API calls | Discrete operations | Streaming, persistent connections |
| Compute time | Variable workloads | Idle resources still cost |
| Storage | Data products | Temporary/cache data |
| Bandwidth | CDN, media | Retry-heavy protocols |
| MAU | User-facing apps | Machine-to-machine |
| Seats | Collaboration tools | Individual developers |
$0.01 per 1,000 API calls
$0.10 per GB stored
$5 per team member
Estimate your monthly cost:
API calls per month: [____]
Storage (GB): [____]
Estimated cost: $XX/month
Free Pro Enterprise
API calls 10,000/mo 100,000/mo Unlimited
Storage 1GB 50GB 500GB
Support Community Email Priority
Price $0 $29/mo $299/mo
Excellent: Stripe
Excellent: Cloudflare
Poor patterns:
Developers fear:
Usage dashboards:
Current billing period: March 1-31
API calls: 45,000 / 100,000 (45%)
Storage: 12GB / 50GB (24%)
Bandwidth: 89GB / 100GB (89%) ⚠️
Projected bill: $47 (current: $38)
Usage alerts:
Alert settings:
[ ] 50% of monthly limit
[x] 75% of monthly limit
[x] 90% of monthly limit
[x] 100% of monthly limit
[ ] Daily usage spike (>2x average)
Spending caps:
Monthly spending cap: $100
When reached:
( ) Hard stop - service pauses
(x) Soft stop - alert and require approval
( ) No stop - continue and alert
Hard caps:
Soft caps:
Burst allowance:
Automatic scaling:
Bad invoice:
Usage charges: $147.00
Total: $147.00
Good invoice:
API Usage
- Requests: 245,000 @ $0.01/1,000 = $2.45
- Bandwidth: 150GB @ $0.10/GB = $15.00
Compute
- Function invocations: 50,000 @ $0.0001 = $5.00
- Compute time: 10,000 GB-sec @ $0.0000166 = $0.17
Storage
- Database: 25GB @ $0.50/GB = $12.50
Platform fee: $29.00 (Pro plan base)
Subtotal: $64.12
Credits applied: -$10.00 (new user credit)
Total: $54.12
Dashboard requirements:
API for usage data:
curl https://api.example.com/usage \
-H "Authorization: Bearer sk_live_xxx"
{
"period": "2024-03-01/2024-03-31",
"api_calls": 245000,
"bandwidth_gb": 150,
"cost_to_date": 54.12,
"projected_cost": 62.00
}
Don't just communicate price—communicate value relative to alternatives.
Alternative cost comparisons:
Running this yourself:
- Server costs: $200/mo
- Engineer time: $5,000/mo
- Maintenance: $500/mo
Total: $5,700/mo
Our service: $99/mo
You save: $5,601/mo
Time savings:
Without [Product]:
- 2 weeks to build
- 4 hours/month to maintain
With [Product]:
- 30 minutes to integrate
- Zero maintenance
Developer time saved: 120+ hours/year
For enterprise sales, provide ROI tools:
Your company:
- Developers: [10]
- Hours/week on auth: [5]
- Fully-loaded cost/hour: [$150]
Current cost: $3,000/week = $156,000/year
With [Product]:
- Integration: 20 hours one-time = $3,000
- Annual cost: $12,000
- Maintenance: Near zero
First year savings: $141,000
When prices seem high, justify with:
Map competitors by:
Pricing model analysis:
Competitor A: $0.015/request, no free tier, 99.9% SLA
Competitor B: $0.008/request, generous free tier, 99.5% SLA
Open source: $0 + hosting costs (~$0.005/request) + maintenance
Premium pricing:
Value pricing:
Penetration pricing:
Usage-aligned pricing:
For each competitor:
[Competitor Name]
Pricing model: [Per-seat / usage-based / flat]
Free tier: [Yes/No, limits]
Starting price: [$X/mo or $/unit]
Enterprise: [Custom / listed price]
Key differentiator: [Feature/price/market]
Developer sentiment: [From Twitter, HN, Reddit]
A/B testing considerations:
Qualitative research:
Developers share horror stories:
Solution: Spending caps, usage alerts, anomaly detection
Solution: Simple, clear, stable pricing
Solution: Transparent pricing, volume discounts listed
Solution: Grandfathering, clear migration paths, community communication
Some cloud providers:
Some companies:
Some user-based pricing:
/devmarketing-skills/skills/free-tier-strategy - Free tier design/devmarketing-skills/skills/developer-signup-flow - Getting to the pricing page/devmarketing-skills/skills/developer-onboarding - Demonstrating value before price