phuryn/pm-skills

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill pricing-strategy

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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:
ModelBest ForExample
Flat-rateSimple products, predictable costsBasecamp ($99/mo flat)
Per-seatCollaboration tools, team productsSlack, Figma
Usage-basedInfrastructure, API productsAWS, Twilio
TieredProducts with distinct user segmentsMost SaaS (Free/Pro/Enterprise)
FreemiumProducts with viral/network effectsSpotify, Notion
Freemium + usagePlatform productsVercel, OpenAI API
Value-basedHigh-impact enterprise toolsSalesforce, Palantir
  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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1時間の導入数
4
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

ansoff-matrix

Generate 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.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日