Help us improve
Share bugs, ideas, or general feedback.
From pm-product-strategy
Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments
npx claudepluginhub tarunccet/pm-skills --plugin pm-product-strategyHow this command is triggered — by the user, by Claude, or both
Slash command
/pm-product-strategy:pricing <product or pricing question>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /pricing -- Pricing Strategy Design Build a pricing strategy from first principles: analyze pricing models, estimate willingness to pay, benchmark against competitors, and design pricing experiments. ## Invocation ## Workflow ### Step 0: Triage — What Kind of Pricing Question Is This? **First, ask the user:** > "Are you exploring **how to charge** (pricing models, tiers, willingness-to-pay) or **what to charge for** (revenue streams, monetization approaches)?" - **"How to charge"** → This is a pricing design question. Proceed through Steps 1–5 using the **pricing-strategy** skill...
/pricingDesigns a pricing strategy: analyzes models, benchmarks competitors, estimates willingness-to-pay, and plans experiments for your product.
/pricingFetches latest Claude model pricing from claudetop GitHub repo, updates local cache, and displays current pricing per model.
Share bugs, ideas, or general feedback.
Build a pricing strategy from first principles: analyze pricing models, estimate willingness to pay, benchmark against competitors, and design pricing experiments.
/pricing SaaS project management tool moving from free to paid
/pricing Should we switch from per-seat to usage-based pricing?
/pricing [upload competitor pricing pages or current pricing data]
First, ask the user:
"Are you exploring how to charge (pricing models, tiers, willingness-to-pay) or what to charge for (revenue streams, monetization approaches)?"
Ask:
Apply the pricing-strategy and monetization-models skills:
Evaluate applicable models:
For each relevant model: pros, cons, fit for your product, revenue projection approach.
Using web research:
If the user has survey data or customer feedback:
If no data:
## Pricing Strategy: [Product]
**Date**: [today]
**Current pricing**: [if applicable]
### Recommended Model: [Model Name]
**Why this model**: [rationale tied to product value delivery]
### Pricing Structure
| Tier | Price | Includes | Target Segment | Key Limit |
|------|-------|---------|---------------|-----------|
### Free / Trial Strategy
[What's free, what's gated, conversion triggers]
### Competitive Benchmark
| Competitor | Model | Price Range | Positioning |
|-----------|-------|-----------|------------|
### Revenue Projections
| Scenario | Assumptions | Year 1 ARR | Year 2 ARR |
|----------|-----------|-----------|-----------|
| Conservative | [X] | [Y] | [Z] |
| Expected | [X] | [Y] | [Z] |
| Optimistic | [X] | [Y] | [Z] |
### Migration Plan
[If changing pricing: how to transition existing customers]
- Grandfathering approach
- Communication plan
- Timeline
### Pricing Experiments
| Experiment | What We're Testing | Method | Duration |
|-----------|-------------------|--------|----------|
### Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|-----------|
### Key Metrics to Track
- Conversion rate by tier
- Average revenue per user (ARPU)
- Upgrade/downgrade rates
- Churn by price sensitivity
- Price elasticity signals
Save as markdown.