pricing — Claude Code command: what it does, how to install
Builds a pricing plan from product value, competitor data, willingness to pay, and pricing tests. Useful when launching or changing a product’s pricing.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-product-strategy@pm-skillsWhat pricing does
The command maps the product, delivered value, current plans, customer profile, budget context, and reason for a pricing decision. It compares flat-rate, per-seat, usage-based, tiered, freemium, and hybrid models, then connects a suitable model to packaging and revenue projection assumptions.
It uses web research to benchmark 3-5 competitors, spot category patterns, and capture pricing and positioning data. When survey or customer-feedback data exists, the command can apply Van Westendorp analysis; otherwise it estimates willingness to pay from product value, competitive anchors, and market norms.
The output is saved as Markdown. It covers plan structure, free or trial access, migration for existing customers, pricing experiments, risks, and tracking metrics. Van Westendorp analysis requires survey or customer-feedback data.
What it helps with
- choose a payment model for a product
- benchmark competitor plans and prices
- estimate customer willingness to pay
- plan a move to new pricing
- design tests for pricing changes
Example prompts for the agent
- Design pricing for a SaaS project-management tool moving from free to paid.
- Should this product move from per-seat pricing to usage-based pricing?
- Compare competitor pricing with our current data and save the result as Markdown.
How to install pricing
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-product-strategy@pm-skills2Manually: put the files in place
.claude/commands/pricing.mdCall it with /pricing. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/pricing.mdCall it with /prompts:pricing. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/pricing.prompt.mdManually: put the files in place
.gemini/commands/pricing.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about pricing
How do I install pricing in Claude Code?
Add the marketplace with /plugin marketplace add phuryn/pm-skills, install the plugin with /plugin install pm-product-strategy@pm-skills, then use .claude/commands/pricing.md.
What does pricing do?
It develops a pricing strategy by comparing payment models, researching competitors, estimating willingness to pay, and proposing pricing experiments.
What data does the willingness-to-pay analysis need?
Van Westendorp analysis uses survey or customer-feedback data. Without that material, the command estimates willingness to pay from product value, competitor anchors, and market norms.
Source text
pricing.md · MIT
--- description: Design a pricing strategy — models, competitive analysis, willingness-to-pay estimation, and pricing experiments argument-hint: "<product or pricing question>" --- # /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 ``` /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] ``` ## Workflow ### Step 1: Understand the Pricing Context Ask: - What is the product? What value does it deliver? - Current pricing (if any): model, price points, packaging - What's the trigger? (new product, pricing change, competitive pressure, growth stall) - Target customer profile and their budget context - Any constraints? (contractual obligations, market expectations, competitive positioning) ### Step 2: Analyze Pricing Models Apply the **pricing-strategy** and **monetization-strategy** skills: Evaluate applicable models: - **Flat-rate**: Simple, predictable — best for commoditized products - **Per-seat/user**: Scales with adoption — best for collaboration tools - **Usage-based**: Aligns cost with value — best for infrastructure and API products - **Tiered**: Captures different willingness to pay — best for segmented markets - **Freemium**: Drives adoption — best for products with network effects - **Hybrid**: Combines models — best for complex products with multiple value levers For each relevant model: pros, cons, fit for your product, revenue projection approach. ### Step 3: Competitive Pricing Analysis Using web research: - Benchmark pricing against 3-5 competitors - Identify pricing model patterns in the category - Note pricing trends (e.g., shift from per-seat to usage-based in B2B SaaS) - Find pricing page screenshots and data points ### Step 4: Willingness to Pay Estimation If the user has survey data or customer feedback: - Apply Van Westendorp analysis (if data available) - Segment willingness to pay by user type If no data: - Estimate based on value delivered, competitive anchoring, and market norms - Design a willingness-to-pay survey the user can run ### Step 5: Generate Pricing Recommendation ``` ## 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. ### Step 6: Offer Next Steps - "Want me to **create a monetization strategy** with alternative revenue models?" - "Should I **run a market scan** to validate pricing assumptions?" - "Want me to **draft customer communication** for the pricing change?" - "Should I **design the A/B test** for pricing experiments?" ## Notes - Pricing is the most powerful lever for revenue growth — a 1% improvement in pricing typically has 3-4x the impact of 1% improvement in customer acquisition - Value-based pricing always beats cost-plus — start from customer value, not your costs - The best pricing is simple to understand and predictable for the customer - Freemium only works if free users generate value (network effects, word of mouth, marketplace liquidity) - Always design a migration path for existing customers — pricing changes that alienate your base destroy trust
© Paweł Huryn · MIT · phuryn/pm-skills