mcpbeat

Pricing Strategy

phuryn/pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

916 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
24819
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/phuryn/pm-skills --skill pricing-strategy

The instruction itself

4 sections, as written by the author

Pricing Strategy

Design a pricing strategy grounded in value delivery, competitive positioning, and willingness to pay.

Context

You are developing a pricing strategy for $ARGUMENTS.

If the user provides files (competitor pricing, survey data, financial models, or usage data), read them first. Use web search to research competitor pricing if needed.

Instructions

  • Understand the value delivered:
  • What is the core value proposition?
  • What is the customer's alternative (and its cost)?
  • What quantifiable outcomes does the product deliver? (time saved, revenue gained, cost reduced)
  • What is the customer's willingness to pay based on that value?
  • Evaluate pricing models — recommend the best fit:

| Model | Best For | Example |

|---|---|---|

| Flat-rate | Simple products, predictable costs | Basecamp ($99/mo flat) |

| Per-seat | Collaboration tools, team products | Slack, Figma |

| Usage-based | Infrastructure, API products | AWS, Twilio |

| Tiered | Products with distinct user segments | Most SaaS (Free/Pro/Enterprise) |

| Freemium | Products with viral/network effects | Spotify, Notion |

| Freemium + usage | Platform products | Vercel, OpenAI API |

| Value-based | High-impact enterprise tools | Salesforce, Palantir |

  • Analyze competitive pricing:
  • Map competitor pricing tiers and what's included
  • Identify where your product sits (premium, mid-market, budget)
  • Find pricing gaps or opportunities
  • Note any industry pricing conventions
  • Design the pricing structure:
  • Tiers: Define 2-4 tiers with clear differentiation
  • Feature gating: Which features go in which tier? (Use value metrics, not arbitrary limits)
  • Value metric: What unit do you charge on? (users, events, storage, API calls)
  • Anchor pricing: Set the most popular tier to feel like the obvious choice
  • Annual discount: Typically 15-20% off monthly pricing
  • Estimate price sensitivity:
  • Van Westendorp Price Sensitivity Meter (if survey data available):
  • Too cheap → quality concerns
  • Cheap → good value
  • Expensive → starting to hesitate
  • Too expensive → won't buy
  • Alternatively, estimate based on competitor pricing and value delivered
  • Plan pricing experiments:
  • A/B test pricing pages (different price points, tier names, feature bundles)
  • Founder-led sales conversations to test willingness to pay
  • Landing page tests with different price anchors
  • Cohort analysis of conversion rates by price point
  • Output a pricing recommendation:
   Recommended Model: [Model type]
   Value Metric: [What you charge on]

   | Tier | Price | Target Segment | Key Features | Positioning |
   |---|---|---|---|---|

   Key Assumptions:
   - [Assumption] → [How to test]

   Risks:
   - [Risk] → [Mitigation]

Think step by step. Save as markdown. Flag any assumptions that need validation before launch.

Further Reading

How to use it

Copy the folder

Take phuryn/pricing-strategy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.