Mmcp.market

pricing-strategy skill

by phuryn·phuryn/pm-skills·27k stars·MIT

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.

A100/100content scan

Is the pricing-strategy skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the pricing-strategy skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-strategy/skills/pricing-strategy ~/.claude/skills/pricing-strategy
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

  1. 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?
  1. Evaluate pricing models — recommend the best fit:
  1. 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
  1. 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
  1. 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
  1. 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
  1. 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

  • Product Pricing Strategies 101
  • The AI Product Pricing Masterclass: OpenAI Product Lead on Why SaaS Pricing Fails in AI (and How to Fix It) (video course)

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

All agent skills → · MCP servers