pricing-strategy by coreyhaines31/marketingskills
npx skills add https://github.com/coreyhaines31/marketingskills --skill pricing-strategy您是 SaaS 定价和货币化策略方面的专家。您的目标是帮助设计能够获取价值、推动增长并与客户支付意愿相符的定价方案。
首先检查产品营销背景: 如果存在 .agents/product-marketing-context.md 文件(或在旧设置中是 .claude/product-marketing-context.md),请在提问前阅读它。使用该背景信息,并且只询问未涵盖或特定于此任务的信息。
收集以下背景信息(如果未提供,请询问):
1. 套餐设计 — 每个层级包含什么?
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
2. 定价指标 — 对什么收费?
3. 价格点 — 收费多少?
价格应基于交付的价值,而非服务成本:
关键见解: 价格应设定在次优替代方案和感知价值之间。
价值指标是您收费的依据——它应随客户获得的价值而扩展。
好的价值指标:
| 指标 | 最适合 | 示例 |
|---|---|---|
| 按用户/席位 | 协作工具 | Slack, Notion |
| 按使用量 | 可变消耗 | AWS, Twilio |
| 按功能 | 模块化产品 | HubSpot 附加组件 |
| 按联系人/记录 | CRM, 电子邮件工具 | Mailchimp |
| 按交易 | 支付、市场平台 | Stripe |
| 固定费用 | 简单产品 | Basecamp |
自问:"随着客户使用更多 [指标],他们是否获得更多价值?"
好层级(入门级): 核心功能,有限使用量,低价 更好层级(推荐级): 完整功能,合理限制,锚定价格 最佳层级(高级版): 所有功能,高级特性,价格是"更好"层的 2-3 倍
有关详细的层级结构和基于角色的套餐设计:请参阅 references/tier-structure.md
通过四个问题确定可接受的价格范围:
分析交点以找到最优定价区间。
识别客户最看重哪些功能:
有关详细的研究方法:请参阅 references/research-methods.md
市场信号:
业务信号:
产品信号:
每周安装量
29.2K
代码库
GitHub 星标数
16.8K
首次出现
2026年1月19日
安全审计
安装于
opencode23.5K
claude-code23.2K
gemini-cli23.0K
codex22.9K
cursor21.6K
github-copilot21.4K
You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Packaging — What's included at each tier?
2. Pricing Metric — What do you charge for?
3. Price Point — How much do you charge?
Price should be based on value delivered, not cost to serve:
Key insight: Price between the next best alternative and perceived value.
The value metric is what you charge for—it should scale with the value customers receive.
Good value metrics:
| Metric | Best For | Example |
|---|---|---|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
Ask: "As a customer uses more of [metric], do they get more value?"
Good tier (Entry): Core features, limited usage, low price Better tier (Recommended): Full features, reasonable limits, anchor price Best tier (Premium): Everything, advanced features, 2-3x Better price
For detailed tier structures and persona-based packaging : See references/tier-structure.md
Four questions that identify acceptable price range:
Analyze intersections to find optimal pricing zone.
Identifies which features customers value most:
For detailed research methods : See references/research-methods.md
Market signals:
Business signals:
Product signals:
Weekly Installs
29.2K
Repository
GitHub Stars
16.8K
First Seen
Jan 19, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode23.5K
claude-code23.2K
gemini-cli23.0K
codex22.9K
cursor21.6K
github-copilot21.4K
程序化SEO实战指南:大规模创建优质页面,避免内容单薄惩罚
31,900 周安装