メニュー
Use when pricing an AI product — choosing between usage-based/hybrid/outcome pricing, calculating unit economics, protecting margins against LLM cost, and setting prices that reflect value without losing customers.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ai-product-monetization |
| description | Use when pricing an AI product — choosing between usage-based/hybrid/outcome pricing, calculating unit economics, protecting margins against LLM cost, and setting prices that reflect value without losing customers. |
| Model | Structure | Best for | Risk |
|---|---|---|---|
| Flat subscription | $X/month | Predictable use, simple product | Undercharging heavy users |
| Usage-based | $X per [action] | Variable usage, API-like | Surprise bills → churn |
| Hybrid | Flat tier + overage | Most AI products (2025 dominant) | Complexity |
| Outcome-based | % of value created | High-value workflows (legal, finance) | Hard to measure |
| Freemium | Free tier + paid | Consumer tools, high viral coefficient | High LLM cost on free |
2025 data: Hybrid pricing (flat + overage) used by 41% of AI companies (up from 27%). Pure seat-based dropped from 21% → 15%.
AI products have fundamentally different economics than SaaS:
Traditional SaaS: 80-90% gross margins
AI product: 50-60% gross margins (baseline)
AI product + caching: 65-75% gross margins (optimized)
Cost per active user calculation:
Average queries/day: 20
Tokens per query: 2,000 input + 500 output
Model: Claude Sonnet ($3/1M input, $15/1M output)
Daily cost: (20 × 2000 × $3/1M) + (20 × 500 × $15/1M)
= $0.12 + $0.15 = $0.27/user/day
= $8.10/user/month in LLM costs alone
Minimum price for 50% margin: $8.10 × 2 = $16.20/month
Minimum price for 60% margin: $8.10 × 2.5 = $20.25/month
Run this calculation for YOUR product before setting any price.
Anchoring: Show 3 plans, middle plan is "Most Popular"
Basic: $15/month (loss leader)
Pro: $49/month ← "Most Popular" ← anchor to this
Team: $149/month (makes Pro feel cheap)
Value anchoring (connect price to value saved):
"At $49/month, that's $1.63/day — less than your morning coffee.
If it saves you 2 hours/week, you're paying $0.40/hour for a senior analyst."
Free trial vs freemium:
Free trial: 14 days full access, then convert → higher conversion, lower CAC
Freemium: free forever with limits → lower conversion, higher viral, higher LLM cost
Solo builder recommendation: 14-day trial first, add freemium only after PMF
For a solo AI business to be sustainable:
CAC (Customer Acquisition Cost): < $50 for self-serve B2C
< $200 for self-serve B2B
LTV/CAC ratio: > 3x in year 1
Payback period: < 6 months
Gross margin: > 50% (baseline), > 65% (healthy)
Example healthy unit economics:
Price: $49/month
LLM cost: $12/month (25% of revenue)
Gross margin: 75%
Churn: 5%/month
LTV: $49 / 0.05 = $980
CAC: $35 (organic, community)
LTV/CAC: 28x ← excellent
If using freemium, design the paywall deliberately:
Paywall design principles:
1. Users hit limit AFTER experiencing value (not before)
2. Limit is usage-based (queries, documents, seats) not time-based
3. Free tier covers ~20% of what a paying user needs
4. Show clear value message at paywall: "You've saved X hours this month.
Upgrade to keep going."
Aha moment → paywall distance:
Short distance (5-10 min) → low paywall friction
Long distance (3+ sessions) → high paywall friction but better retention
Solo recommendation: Design for 30-minute time to value.
Onboarding → First success → "Want more?" → paywall
ai-product-positioning (stronger moat = higher price ceiling)llm-cost-optimization to improve gross marginsmodel-routing to reduce per-user LLM cost@solo-ai-builder reviews pricing before launch and after first churn spikeUse when conducting quality audits — reviewing process compliance, identifying gaps between defined process and actual practice, conducting structured inspections (code review audits, test quality reviews), and producing audit reports with remediation plans.
Use when managing quality risk — identifying quality risks in a product or release, applying risk-based testing prioritization, creating risk mitigation plans, and communicating quality risk to stakeholders for go/no-go decisions.
Use when designing or implementing test automation — choosing the right automation framework (Playwright, pytest, JUnit), Page Object Model, selector strategies, test isolation, managing flaky tests, and CI integration.
Use when managing defects — writing effective bug reports, applying severity/priority matrix, tracking defect lifecycle, conducting root cause analysis, and measuring defect metrics for process improvement.
Use when measuring and reporting QA quality — defect escape rate, test coverage analysis, flaky test rate, mean time to detect, shift-left metrics, and building quality dashboards for stakeholders.
Use when managing test data — designing test data strategies, using factories and builders, creating fixtures, generating synthetic data, masking PII for testing, and managing test database state.