pricing-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

When this skill is activated, always start your first response with the 🧢 emoji.

当激活此Skill时，你的第一条回复请以🧢表情开头。

Pricing Strategy

定价策略

A practical framework for designing, packaging, and testing software pricing. Pricing is the highest-leverage growth lever most teams ignore - a 1% improvement in pricing yields 2-4x the revenue impact of a 1% improvement in acquisition. This skill covers the full pricing lifecycle: choosing a model (freemium, usage-based, seat-based, flat), packaging features into tiers, building enterprise plans that close six-figure deals, and running price tests without torching customer trust. Agents can use this to draft pricing pages, evaluate model trade-offs, design packaging, and structure experiments.

这是一个用于设计、打包和测试软件定价的实用框架。定价是大多数团队忽略的最高杠杆增长手段——定价提升1%带来的收入影响是获客提升1%的2-4倍。此Skill覆盖完整的定价生命周期：选择定价模型（freemium、基于使用量、按席位、固定费率）、将功能分层打包、制定能促成六位数交易的企业级方案，以及在不损害客户信任的前提下开展价格测试。Agent可使用它来撰写定价页面内容、评估模型利弊、设计功能打包方案，以及规划实验。

When to use this skill

何时使用此Skill

Trigger this skill when the user:

Is designing or redesigning a pricing page or pricing model
Needs to decide between freemium, free trial, usage-based, or seat-based pricing
Wants to package features into tiers (good/better/best)
Is building an enterprise tier and needs to structure negotiation levers
Wants to run a price test or willingness-to-pay survey
Needs to set or change prices for a SaaS product
Is evaluating free-to-paid conversion rates or upgrade triggers
Asks about price anchoring, decoy pricing, or price discrimination strategies

Do NOT trigger this skill for:

Billing system implementation details (use a payments or Stripe skill)
General business strategy or go-to-market planning unrelated to pricing

当用户出现以下需求时触发此Skill：

正在设计或重新设计定价页面或定价模型
需要在freemium、免费试用、基于使用量或按席位计费之间做选择
希望将功能分层打包（基础版/进阶版/高级版）
正在搭建企业级套餐，需要制定谈判筹码
想要开展价格测试或支付意愿调研
需要为SaaS产品设定或调整价格
正在评估免费转付费的转化率或升级触发机制
询问价格锚定、诱饵定价或价格歧视策略

请勿在以下场景触发此Skill：

计费系统的具体实施细节（请使用支付或Stripe相关Skill）
与定价无关的一般商业策略或上市规划

Key principles

核心原则

Value before price - Price is a function of perceived value, not cost. Before setting any number, articulate the measurable outcome customers get. If you cannot name the outcome, you cannot defend the price.
Packaging is strategy, pricing is tactics - Which features go in which tier matters more than the dollar amount on each tier. Get packaging wrong and no price point saves you. Get packaging right and you have room to adjust prices later.
One metric to rule them all - The best pricing models charge on a single value metric that scales with the customer's success. Seats work when every user gets equal value. API calls work when consumption correlates with revenue. Pick the metric where "more usage = more value for the customer."
Segment by willingness to pay, not by cost to serve - Tiers should separate customers who get different amounts of value, not customers who cost you different amounts. A startup and an enterprise both use the same servers, but the enterprise extracts 100x more value - price accordingly.
Test prices, not just features - Most teams A/B test buttons and headlines but never test prices. Price sensitivity data is the highest-signal input to pricing decisions and can be gathered safely with the right methodology.

价值先于价格 - 价格是感知价值的函数，而非成本的函数。在设定任何价格之前，要明确客户能获得的可衡量成果。如果无法说出具体成果，你就无法为价格辩护。
打包是策略，定价是战术 - 哪些功能归入哪个套餐，比每个套餐的价格数字更重要。如果打包出错，任何价格都无法挽救；如果打包正确，后续还有调整价格的空间。
单一核心指标主导 - 最佳定价模型基于单一价值指标收费，该指标会随客户的成功而增长。当每个用户获得的价值相同时，按席位计费适用；当使用量与客户收入相关时，按API调用量计费适用。选择“使用越多=客户获得的价值越多”的指标。
按支付意愿细分，而非服务成本 - 套餐分层应区分获得不同价值的客户，而非服务成本不同的客户。初创企业和企业客户使用相同的服务器，但企业客户获得的价值是前者的100倍——定价应与此匹配。
测试价格，而非仅测试功能 - 大多数团队会A/B测试按钮和标题，但从不测试价格。价格敏感度数据是定价决策中信号最强的输入，使用正确方法可以安全地收集这些数据。

Core concepts

核心概念

Value metric is the unit you charge on - seats, API calls, messages sent, revenue processed, GB stored. The ideal value metric is easy to understand, scales with customer value, and is predictable enough for customers to budget. Slack charges per seat. Twilio charges per message. Stripe charges per transaction. Each aligns price with the value the customer receives.

Packaging is the act of grouping features into tiers. The standard model is good/better/best (three tiers). The middle tier should be the target - it is where 60-70% of customers should land. The top tier exists to make the middle tier look reasonable (anchoring) and to capture high-willingness-to-pay customers.

Price fences are the criteria that separate tiers. They must be objective and hard to game. Good fences: number of seats, API volume, data retention period, SLA level. Bad fences: company size (self-reported), "startup" vs "enterprise" (subjective).

Willingness to pay (WTP) is the maximum price a customer segment will accept. It varies dramatically by segment. You discover WTP through Van Westendorp surveys, Gabor-Granger analysis, or conjoint studies - never by asking "what would you pay?" directly.

价值指标是你收费的单位——席位、API调用量、发送消息数、处理收入额、存储GB数。理想的价值指标应易于理解、随客户价值增长，且足够稳定以便客户预算。Slack按席位收费，Twilio按消息收费，Stripe按交易收费。每种方式都让价格与客户获得的价值保持一致。

功能打包是将功能分组为套餐的行为。标准模式是基础版/进阶版/高级版（三个套餐）。中间套餐应为目标套餐——60-70%的客户应选择此套餐。顶级套餐的存在是为了让中间套餐看起来合理（价格锚定），同时捕获支付意愿高的客户。

价格门槛是区分套餐的标准，必须客观且难以钻空子。优质门槛：席位数量、API流量、数据保留期限、SLA等级。糟糕门槛：公司规模（自我申报）、“初创企业”vs“企业客户”（主观判断）。

**支付意愿（WTP）**是某一客户群体能接受的最高价格，不同群体之间差异巨大。你可以通过Van Westendorp调研、Gabor-Granger分析或联合分析来了解WTP——切勿直接问“你愿意付多少钱？”

Common tasks

常见任务

Design a three-tier SaaS pricing page

设计三层SaaS定价页面

Framework: Good / Better / Best

Name tiers by persona, not size - "Starter / Team / Business" beats "Small / Medium / Large." Names signal who the tier is for.
Anchor with the top tier - Show the most expensive tier first (left or top). It reframes the middle tier as reasonable.
Highlight the target tier - Use a "Most Popular" badge on the middle tier. 60-70% of signups should land here.
Limit to 3-4 tiers - More tiers create decision paralysis. If you need a fourth, make it "Enterprise - Contact Sales."
Feature differentiation checklist:
- Free/Starter: core value proposition, hard usage cap, no integrations
- Team/Pro: collaboration features, higher limits, basic integrations
- Business/Enterprise: SSO, audit logs, SLA, dedicated support, custom contracts

Pricing page copy pattern:

[Tier name]
[One sentence: who this is for]
[$X / mo per seat]
[3-5 feature bullets, starting with the most differentiating]
[CTA button]

框架：基础版/进阶版/高级版

按用户角色命名套餐，而非规模 - “入门版/团队版/商务版”比“小型/中型/大型”更好。名称能明确该套餐针对的用户群体。
以顶级套餐为锚点 - 先展示最昂贵的套餐（左侧或顶部），这会让中间套餐显得合理。
突出目标套餐 - 在中间套餐上添加“最受欢迎”标识，60-70%的注册用户应选择此套餐。
限制为3-4个套餐 - 套餐过多会导致决策瘫痪。如果需要第四个，可设为“企业版 - 联系销售”。
功能差异化清单：
- 免费版/入门版：核心价值主张、严格的使用上限、无集成功能
- 团队版/专业版：协作功能、更高的使用限额、基础集成功能
- 商务版/企业版：SSO、审计日志、SLA、专属支持、定制合同

定价页面文案模板：

[套餐名称]
[一句话描述：适用人群]
[$X / 每月每席位]
[3-5个功能要点，从最具差异化的功能开始]
[CTA按钮]

Choose between freemium and free trial

在freemium和免费试用之间做选择

Factor	Freemium	Free Trial
Best when	Product has viral/network effects, low marginal cost	Product value is obvious but needs time to discover
Conversion rate	2-5% free to paid (typical)	15-25% trial to paid (typical)
Risk	Freeloaders consume resources without converting	Short trial may not show full value
Examples	Slack, Dropbox, Figma	Salesforce, HubSpot, Netflix

Decision rule: Use freemium when free users create value for paid users (network effects, content creation, referrals). Use free trial when the product's value requires sustained use to appreciate but does not benefit from a large free base.

Hybrid option: Free trial of the paid tier, then downgrade to a limited free tier. This shows users the full value, then lets them keep a foothold. Zoom does this well.

因素	Freemium	免费试用
适用场景	产品具有病毒式/网络效应、边际成本低	产品价值明确但需要时间体验才能感知
转化率	免费转付费2-5%（典型值）	试用转付费15-25%（典型值）
风险	免费用户消耗资源但不转化	试用期过短可能无法展示全部价值
案例	Slack、Dropbox、Figma	Salesforce、HubSpot、Netflix

决策规则： 当免费用户能为付费用户创造价值（网络效应、内容创作、推荐）时，使用freemium；当产品价值需要持续使用才能感知，但不需要庞大的免费用户群体时，使用免费试用。

混合方案： 付费套餐提供免费试用期，到期后降级为受限免费版。这样可以让用户体验全部价值，同时保留使用入口。Zoom就是很好的例子。

Implement usage-based pricing

实施基于使用量的计费

When to use: The customer's value scales linearly with consumption, and usage is measurable and predictable. Good fits: API platforms, cloud infrastructure, messaging services, data pipelines.

Structure options:

Pure pay-as-you-go - No commitment, pay per unit. Low barrier, but revenue is unpredictable. Best for developer tools (Twilio, AWS Lambda).
Committed use + overage - Base commitment at a discount, then per-unit overage. Gives revenue predictability. Best for mid-market and enterprise (Snowflake).
Tiered volume - Price per unit drops as volume increases. Incentivizes growth. Best when you want customers to consolidate spend (Stripe's volume discounts).

Implementation checklist:

Pick one value metric (not two or three)
Set a minimum monthly commitment (even $0 with a credit card on file)
Provide a usage dashboard and spend alerts
Offer committed-use discounts for annual contracts
Bill in arrears with a clear invoice breakdown

Gotcha: Usage-based pricing makes revenue forecasting harder. Pair it with annual commitments or minimum spend agreements for enterprise customers.

适用场景： 客户价值随使用量线性增长，且使用量可衡量、可预测。适合的产品：API平台、云基础设施、消息服务、数据管道。

结构选项：

纯按需付费 - 无承诺，按使用单位付费。门槛低，但收入不可预测。最适合开发者工具（Twilio、AWS Lambda）。
承诺使用量+超额计费 - 基础承诺量享受折扣，超出部分按单位计费。能保证收入可预测。最适合中大型企业客户（Snowflake）。
阶梯式按量计费 - 单位价格随使用量增加而降低。激励客户增长。最适合希望客户整合支出的场景（Stripe的批量折扣）。

实施清单：

选择一个价值指标（而非两个或三个）
设置最低月度承诺（即使是$0，也要留存信用卡信息）
提供使用量仪表盘和支出提醒
为年度合同提供承诺使用量折扣
事后计费，并提供清晰的发票明细

注意事项：基于使用量的计费会让收入预测更困难。针对企业客户，可搭配年度承诺或最低支出协议。

Structure an enterprise tier

制定企业级套餐

Enterprise pricing is not a number on a webpage - it is a negotiation framework.

Must-have enterprise features (price fences):

SSO / SAML integration
Audit logs and compliance certifications (SOC 2, HIPAA)
Dedicated support (named CSM, SLA with uptime guarantee)
Custom contracts and invoicing (NET 30/60/90)
Data residency and security controls
Admin controls, role-based access, and user provisioning (SCIM)

Pricing levers for negotiation:

Seat count - volume discount at 100+, 500+, 1000+ thresholds
Contract length - 10-20% discount for multi-year commits
Payment terms - annual upfront is default; quarterly or monthly at a premium
Usage tiers - committed volume at lower per-unit cost
Professional services - onboarding, migration, custom integrations as add-ons

Pricing floor rule: Never discount more than 30% off list price. If the customer needs more than 30% off, restructure the deal (fewer seats, shorter term, fewer features) rather than deepening the discount. Deep discounts set bad renewal precedents.

企业级定价不是网页上的一个数字——它是一个谈判框架。

必备企业级功能（价格门槛）：

SSO / SAML集成
审计日志和合规认证（SOC 2、HIPAA）
专属支持（指定客户成功经理、带 uptime 保障的SLA）
定制合同和发票（NET 30/60/90账期）
数据驻留和安全控制
管理员权限、基于角色的访问控制和用户配置（SCIM）

谈判定价杠杆：

席位数量 - 达到100+、500+、1000+席位时提供批量折扣
合同期限 - 多年合同可享受10-20%折扣
付款条款 - 默认年度预付；季度或月度付款需支付20-30%溢价
使用量套餐 - 承诺使用量享受更低的单位成本
专业服务 - 入职培训、迁移服务、定制集成作为附加服务

定价底线规则： 折扣幅度不得超过标价的30%。如果客户需要超过30%的折扣，应调整交易结构（减少席位、缩短期限、减少功能），而非进一步降价。大幅折扣会为后续续约树立不良先例。

Run a price test

开展价格测试

Method 1: Van Westendorp Price Sensitivity Meter

Ask four questions to a sample of target customers:

At what price would this be so cheap you would question quality? (Too Cheap)
At what price is this a bargain - a great value? (Cheap)
At what price is this getting expensive but you would still consider? (Expensive)
At what price is this too expensive - you would never buy? (Too Expensive)

Plot the cumulative distributions. The intersection of "Too Cheap" and "Expensive" gives the optimal price point. The range between "Cheap/Too Expensive" intersection and "Too Cheap/Expensive" intersection gives the acceptable price range.

Method 2: A/B test with geographic or cohort splits

Never show different prices to the same market simultaneously - it destroys trust if discovered.

Safe approaches:

Test in different geographic markets (e.g., US vs UK)
Test on new signups only (grandfather existing customers)
Test different packaging (features per tier) at the same price
Use time-based splits (this month vs next month for new cohorts)

Method 3: Gabor-Granger for demand curve

Show a price and ask "would you buy at this price?" Vary the price across respondents. Plot price vs % who would buy. Find the revenue-maximizing point (price * conversion).

Golden rule: Never test prices on existing paying customers. Only test on new prospects or in new markets.

方法1：Van Westendorp价格敏感度测试

向目标客户样本询问四个问题：

价格低到什么程度会让你质疑产品质量？（过低）
价格低到什么程度会让你觉得很划算——极具价值？（划算）
价格高到什么程度你仍会考虑购买？（偏高）
价格高到什么程度你绝对不会购买？（过高）

绘制累积分布曲线。“过低”和“偏高”的交点为最优价格点。“划算/过高”交点与“过低/偏高”交点之间的范围为可接受价格区间。

方法2：按地域或用户群拆分的A/B测试

切勿在同一市场同时展示不同价格——如果被发现会损害客户信任。

安全的测试方式：

在不同地域市场测试（如美国vs英国）
仅针对新注册用户测试（老用户保持原价格）
在相同价格下测试不同的功能打包方案
按时间拆分测试（本月vs下月的新用户群）

方法3：Gabor-Granger需求曲线测试

展示一个价格并询问“你会以这个价格购买吗？”在不同受访者中调整价格。绘制价格与购买意愿百分比的曲线，找到收入最大化的点（价格×转化率）。

黄金法则：切勿在现有付费客户身上测试价格。仅针对新潜在客户或新市场测试。

Set initial prices for a new product

为新产品设定初始价格

Step 1 - Competitor anchoring: List 3-5 competitors and their pricing. You are not matching them - you are using them to understand the market's reference frame.

Step 2 - Value quantification: Calculate the economic value your product creates. If your tool saves 10 hours/month of a $100/hr employee's time, the value created is $1,000/month. Price at 10-20% of value created.

Step 3 - Segment analysis: Identify 2-3 customer segments by willingness to pay. Map features to segments. Price the top segment first, then work down.

Step 4 - Round and simplify: End prices in 9 for consumer ($49, $99, $199). Use round numbers for enterprise ($500, $1,000). Never use decimal prices for SaaS.

Step 5 - Launch high, discount down: It is dramatically easier to lower prices than raise them. Launch at the top of your acceptable range and adjust based on conversion data. A product that is "too expensive" still gets feedback; a product that is "too cheap" leaves money on the table silently.

步骤1 - 竞品锚定： 列出3-5个竞品及其定价。你不需要匹配它们的价格，而是用它们来了解市场的参考框架。

步骤2 - 价值量化： 计算你的产品为客户创造的经济价值。如果你的工具每月能为一名时薪$100的员工节省10小时，那么创造的价值就是每月$1000。定价应为创造价值的10-20%。

步骤3 - 用户群分析： 按支付意愿划分2-3个客户群体，将功能与群体匹配。先为最高支付意愿的群体定价，再往下推导。

步骤4 - 简化并取整： 面向C端的价格以9结尾（$49、$99、$199）；面向企业的价格使用整数（$500、$1,000）。SaaS产品切勿使用带小数的价格。

步骤5 - 高价上线，逐步降价： 降价比涨价容易得多。在可接受价格区间的上限上线，然后根据转化率数据调整。“价格过高”的产品仍能获得反馈；而“价格过低”的产品会悄无声息地损失收入。

Design upgrade triggers for freemium

设计freemium的升级触发机制

Upgrade triggers are the moments when a free user hits a limit that motivates them to pay. Design these intentionally.

Effective triggers:

Usage limits - "You have used 95% of your free storage" (Dropbox)
Feature gates - "Upgrade to unlock advanced analytics" (Mixpanel)
Collaboration gates - "Add more than 3 team members" (Notion)
Time-based - "Your premium trial ends in 3 days" (LinkedIn)
Export/integration gates - "Export to CSV requires Pro" (Airtable)

Design rules:

Let users experience the core value loop before hitting the gate
Show what they are missing (preview locked features, not just a lock icon)
Trigger upgrade prompts at moments of high engagement, not frustration
Make the upgrade path one click - pre-select the right tier based on their usage

升级触发机制是指免费用户达到某个限制，从而促使他们付费的时刻。需要有意设计这些机制。

有效的触发机制：

使用量限制 - “你已使用95%的免费存储空间”（Dropbox）
功能限制 - “升级解锁高级分析功能”（Mixpanel）
协作限制 - “添加超过3名团队成员需升级”（Notion）
时间限制 - “你的高级试用将在3天后结束”（LinkedIn）
导出/集成限制 - “导出为CSV需要专业版”（Airtable）

设计规则：

让用户先体验核心价值循环，再触发限制
展示他们错过的内容（预览锁定的功能，而不仅仅是锁图标）
在用户高参与度时刻触发升级提示，而非在他们受挫时
升级路径一键完成——根据用户的使用情况预先选择合适的套餐

Anti-patterns / common mistakes

反模式/常见错误

Mistake	Why it's wrong	What to do instead
Pricing based on cost-plus	Your costs are irrelevant to what customers will pay; you leave massive value on the table	Price based on value delivered, use competitor pricing as reference frame
Too many tiers (5+)	Decision paralysis reduces conversion; operational complexity increases	Stick to 3 tiers plus an enterprise "Contact Sales" option
Identical feature sets across tiers (only limits differ)	Customers see no qualitative difference; defaults to cheapest tier	Differentiate tiers by feature category (collaboration, security, support) not just quantity
Offering monthly-only pricing	Revenue is unpredictable; churn is higher on monthly plans	Default to annual billing with a monthly option at 20-30% premium
Discounting to close every deal	Trains the market to expect discounts; erodes pricing power over time	Discount only with a trade (longer term, case study, referral) - never for free
Changing prices on existing customers without notice	Destroys trust, spikes churn, generates negative press	Grandfather existing customers or give 90+ days notice with clear value justification
Hiding pricing entirely	Creates friction; self-serve buyers leave; only works for true enterprise sales	Show pricing for self-serve tiers; use "Contact Sales" only for enterprise

错误做法	错误原因	正确做法
基于成本加成定价	你的成本与客户愿意支付的价格无关，会浪费大量潜在价值	基于交付的价值定价，将竞品定价作为参考框架
套餐过多（5个以上）	决策瘫痪会降低转化率，运营复杂度也会增加	坚持3个套餐，外加一个“企业版 - 联系销售”选项
套餐间功能完全相同（仅使用限额不同）	客户看不到质的差异，会默认选择最便宜的套餐	按功能类别（协作、安全、支持）区分套餐，而非仅按数量
仅提供月度定价	收入不可预测，月度套餐的客户流失率更高	默认提供年度计费，月度计费需支付20-30%溢价
为了成交所有订单而降价	会让市场形成降价预期，长期来看会削弱定价权	仅在有交换条件（更长合同期限、案例研究、推荐）时才降价——绝不免费降价
未提前通知就更改现有客户的价格	会损害信任，导致客户流失，引发负面舆论	为现有客户保留原价格，或提前90天以上通知并提供明确的价值理由
完全隐藏价格	会增加摩擦，自助购买用户会离开；仅适用于纯企业级销售场景	展示自助套餐的价格；仅对企业版使用“联系销售”

References

参考资料

For detailed frameworks on specific pricing sub-domains, read the relevant file from the

references/

folder:

```
references/pricing-models.md
```
- deep comparison of all pricing model types (flat-rate, per-seat, usage-based, hybrid, reverse trial) with decision trees and real-world examples
```
references/price-testing.md
```
- detailed methodology for Van Westendorp, Gabor-Granger, conjoint analysis, and safe A/B testing approaches with sample survey templates

Only load a references file when the current task requires it - they are long and will consume context.

如需了解特定定价子领域的详细框架，请阅读

references/

文件夹中的相关文件：

```
references/pricing-models.md
```
- 所有定价模型类型（固定费率、按席位、基于使用量、混合、反向试用）的深度对比，包含决策树和真实案例
```
references/price-testing.md
```
- Van Westendorp、Gabor-Granger、联合分析和安全A/B测试方法的详细说明，包含调研模板示例

仅在当前任务需要时加载参考文件——这些文件篇幅较长，会占用上下文资源。