Help us improve
Share bugs, ideas, or general feedback.
From pm-product-strategy
Analyzes and designs pricing strategies including models, competitor pricing, willingness-to-pay estimation, and price elasticity. Useful for setting prices, evaluating models, price adjustments, or freemium vs paid comparisons.
npx claudepluginhub killvxk/pm-skills-zh --plugin pm-product-strategyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-strategy:pricing-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
从价值交付、竞争定位和支付意愿出发,设计有依据的定价策略。
Analyzes and designs pricing strategies: models (flat-rate, per-seat, usage-based, tiered, freemium), competitor pricing, willingness to pay, elasticity. Use for pricing setup, evaluation, changes, or freemium comparisons.
Use this skill when the user asks to "review our pricing", "help me think through pricing", "should we change our price", "pricing strategy", "how should we price this", "pricing tiers", "is our pricing right", "freemium vs. paid", or wants to evaluate or design their product's pricing model.
Structures pricing strategy decisions, packaging options, and tier design for SaaS and digital products. Produces a recommendation with model rationale, tier structure, competitive positioning, and rollout plan.
Share bugs, ideas, or general feedback.
从价值交付、竞争定位和支付意愿出发,设计有依据的定价策略。
你正在为 $ARGUMENTS 制定定价策略。
如果用户提供了文件(竞品定价、调研数据、财务模型或用量数据),请先阅读。如有需要,使用网络搜索调研竞品定价。
理解交付的价值:
评估定价模型——推荐最适合的模型:
| 模型 | 最适合 | 示例 |
|---|---|---|
| 统一费率(Flat-rate) | 简单产品,成本可预期 | Basecamp(每月 $99 统一收费) |
| 按席位(Per-seat) | 协作工具、团队产品 | Slack、Figma |
| 按用量(Usage-based) | 基础设施、API 产品 | AWS、Twilio |
| 分级定价(Tiered) | 有明显用户细分的产品 | 多数 SaaS(免费/专业/企业) |
| 免费增值(Freemium) | 有病毒传播/网络效应的产品 | Spotify、Notion |
| 免费增值 + 用量(Freemium + usage) | 平台类产品 | Vercel、OpenAI API |
| 价值定价(Value-based) | 高影响力企业工具 | Salesforce、Palantir |
分析竞争定价:
设计定价结构:
估算价格敏感度:
规划定价实验:
输出定价建议:
推荐模型:[模型类型]
计费单元:[收费依据]
| 套餐 | 价格 | 目标细分 | 核心功能 | 定位 |
|---|---|---|---|---|
关键假设:
- [假设] → [验证方法]
风险:
- [风险] → [缓解措施]
逐步思考。保存为 markdown 格式。标注上线前需要验证的假设。