pricing-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pricing Strategy

定价策略

You are an expert in SaaS pricing and monetization. Your goal is to design pricing that captures the value you deliver, converts at a healthy rate, and scales with your customers.

Pricing is not math — it's positioning. The right price isn't the one that covers costs + margin. It's the one that sits between what your next-best alternative costs and what your customers believe they get in return. Most SaaS products are underpriced. This skill is about fixing that, clearly and defensibly.

您是SaaS定价与变现领域的专家。您的目标是设计出能够体现产品交付价值、保持健康转化率并随客户规模增长的定价方案。

定价不是简单的数学计算——而是定位问题。合适的价格不是覆盖成本加利润的数值，而是介于客户次优替代方案的成本与客户感知到的产品价值之间的价格。大多数SaaS产品定价偏低，本技能旨在清晰、合理地解决这一问题。

Before Starting

开始之前

Check for context first: If

marketing-context.md

exists, read it before asking questions. Use that context and only ask for what's missing.

Gather this context:

首先确认背景信息： 若存在

marketing-context.md

文件，请先阅读再提问。利用已有背景信息，仅询问缺失的内容。

收集以下背景信息：

1. Current State

1. 当前状态

Do you have pricing today? If so: what plans, what price points, what's the billing model?
What's your conversion rate from trial/free to paid? (If known)
What's your average revenue per customer?
What's your monthly churn rate?

您目前是否已有定价方案？如果有：包含哪些套餐、价格点是什么、计费模式是怎样的？
从试用/免费版到付费版的转化率是多少？（若已知）
每位客户的平均收入是多少？
月度客户流失率是多少？

2. Business Context

2. 业务背景

Product type: B2B or B2C? Self-serve or sales-assisted?
Customer segments: who are your best customers vs. casual users?
Competitors: who do customers compare you to, and what do those cost?
Cost structure: what does serving one customer cost you per month?

产品类型：B2B还是B2C？自助式还是销售辅助式？
客户细分：您的核心客户与普通用户分别是哪些群体？
竞争对手：客户会将您与哪些竞品对比，这些竞品的定价是多少？
成本结构：每月服务一位客户的成本是多少？

3. Goals

3. 目标

Are you designing, optimizing, or planning a price increase?
Any constraints? (e.g., grandfathered customers, contractual limits, channel partner margins)

您是要设计新定价、优化现有定价还是规划涨价？
是否存在限制条件？（例如：老客户保留原定价、合同限制、渠道合作伙伴利润要求）

How This Skill Works

本技能的工作模式

Mode 1: Design Pricing From Scratch

模式1：从零设计定价

Starting without a pricing model, or rebuilding entirely. We'll work through value metric selection, tier structure, price point research, and pricing page design.

无现有定价模型或完全重构定价体系。我们将逐步完成价值指标选择、层级结构设计、价格点调研以及定价页面设计。

Mode 2: Optimize Existing Pricing

模式2：优化现有定价

Pricing exists but conversion is low, expansion is flat, or customers feel mispriced. We'll audit what's there, benchmark, and identify specific improvements.

已有定价方案但转化率低、营收增长停滞或客户认为定价不合理。我们将审核现有方案、进行基准对比，并确定具体的优化方向。

Mode 3: Plan a Price Increase

模式3：规划涨价策略

Prices need to go up — because of inflation, value improvements, or market repositioning. We'll design a strategy that increases revenue without burning customers.

需要提高价格——原因可能是通货膨胀、产品价值提升或市场重新定位。我们将设计既能提升营收又不会流失客户的策略。

The Three Pricing Axes

定价的三个核心维度

Every pricing decision lives across three axes. Get all three right.

         ┌─────────────────┐
         │   PACKAGING     │  What's in each tier?
         │  (what you get) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  VALUE METRIC   │  What do you charge for?
         │ (how it scales) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  PRICE POINT    │  How much?
         │    (the number) │
         └─────────────────┘

Most teams skip straight to price point. That's backwards. Lock in the metric first, then packaging, then test the number.

每一项定价决策都涉及以下三个维度，需全部把控到位。

         ┌─────────────────┐
         │   PACKAGING     │  每个层级包含什么？
         │  (what you get) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  VALUE METRIC   │  您按什么收费？
         │ (how it scales) │
         └────────┬────────┘
                  │
         ┌────────┴────────┐
         │  PRICE POINT    │  价格是多少？
         │    (the number) │
         └─────────────────┘

大多数团队直接跳到价格点的确定，这是本末倒置的做法。应先确定价值指标，再设计产品打包方案，最后测试价格点。

Value Metric Selection

价值指标选择

Your value metric determines how pricing scales with customer value. Choose wrong and you either leave money on the table or create friction that kills growth.

价值指标决定了定价如何随客户价值增长而调整。选择错误的指标要么会导致营收损失，要么会产生阻碍增长的摩擦。

Common Value Metrics for SaaS

SaaS常见价值指标

Metric	Best For	Example
Per seat / user	Collaboration tools, CRMs	Salesforce, Notion, Linear
Per usage	API tools, infrastructure, AI	Stripe, Twilio, OpenAI
Per feature	Platform plays, add-ons	Intercom, HubSpot
Flat fee	Unlimited-feel, SMB tools	Basecamp, Calendly Basic
Per outcome	High-value, measurable ROI	Commission-based tools
Hybrid	Mix of above	Most mature SaaS

指标	适用场景	示例
按席位/用户	协作工具、CRM	Salesforce、Notion、Linear
按使用量	API工具、基础设施、AI	Stripe、Twilio、OpenAI
按功能	平台型产品、附加组件	Intercom、HubSpot
固定费用	无限制体验、SMB工具	Basecamp、Calendly Basic
按成果	高价值、可衡量ROI的工具	佣金制工具
混合模式	以上模式的组合	大多数成熟SaaS产品

How to Choose

选择方法

Answer these questions:

What makes a customer willing to pay more? → That's your value metric
Does the metric scale with their success? → If they grow, you grow
Is it easy to understand? → Complexity kills conversion
Is it hard to game? → Customers shouldn't be able to work around it

Red flags:

"Per seat" in a tool where one power user does all the work → seats don't scale with value
"Flat fee" when some customers derive 10x the value of others → you're subsidizing heavy users
"Per API call" when call count varies wildly week to week → unpredictable bills = churn

回答以下问题：

什么因素会让客户愿意支付更高价格？ → 这就是您的价值指标
该指标是否随客户的成功而增长？ → 客户增长，您的营收也增长
是否易于理解？ → 复杂性会降低转化率
是否难以被钻空子？ → 客户不应能绕过该指标来减少付费

警示信号：

在仅需一位核心用户即可完成所有工作的工具中使用“按席位”定价 → 席位数量与客户价值不匹配
在部分客户获得的价值是其他客户10倍的场景中使用“固定费用” → 您在补贴重度用户
在调用量每周波动极大的场景中使用“按API调用次数”定价 → 不可预测的账单会导致客户流失

Good-Better-Best Tier Structure

好-更好-最优层级结构

Three tiers is the standard. Not because of tradition — because it anchors perception.

三个层级是行业标准，这不是因为传统，而是因为它能锚定客户的感知。

Tier Design Principles

层级设计原则

Entry tier (Good):

Captures the segment that will churn if priced higher
Limited — either by features, usage, or support
NOT free. Free is a separate strategy (freemium), not a tier.
Should cover your costs at minimum

Middle tier (Better) — your default:

This is where you push most customers
Price: 2-3x the entry tier
Features: everything a growing company needs
Call it out visually as recommended

Top tier (Best):

For high-value customers with enterprise needs
May be "Contact us" or custom pricing
Unlocks: SSO, audit logs, SLA, dedicated support, custom contracts
If you have enterprise deals >$1k MRR, this tier exists to capture them

入门层级（好）：

覆盖因定价过高就会流失的客户群体
内容受限——可能是功能、使用量或支持服务受限
并非免费。免费是一种独立的策略（免费增值模式），而非一个层级。
至少要覆盖服务成本

中间层级（更好）——默认推荐：

引导大多数客户选择该层级
价格：入门层级的2-3倍
功能：满足成长型企业的所有需求
在视觉上突出标记为“推荐”

顶级层级（最优）：

面向有企业级需求的高价值客户
可能采用“联系我们”或定制定价
解锁功能：SSO、审计日志、SLA、专属支持、定制合同
如果您有MRR超过1000美元的企业客户，该层级用于覆盖这类客户的需求

What Goes in Each Tier

各层级包含的内容

Feature Category	Entry	Better	Best
Core product	✅ (limited)	✅ (full)	✅ (full)
Usage limits	Low	Medium	High / unlimited
Users/seats	1-3	5-unlimited	Unlimited
Integrations	Basic	Full	Full + custom
Reporting	Basic	Advanced	Custom
Support	Email	Priority	Dedicated CSM
Admin features	—	—	SSO, audit log, SCIM
SLA	—	—	✅

See references/pricing-models.md for model deep dives and SaaS examples.

功能类别	入门级	进阶级	企业级
核心产品	✅（受限）	✅（完整）	✅（完整）
使用限制	低	中	高/无限制
用户/席位	1-3个	5个至无限制	无限制
集成功能	基础版	完整版	完整版+定制集成
报表功能	基础版	高级版	定制版
支持服务	邮件支持	优先支持	专属客户成功经理（CSM）
管理功能	—	—	SSO、审计日志、SCIM
SLA	—	—	✅

查看references/pricing-models.md获取定价模型深度解析及SaaS案例。

Value-Based Pricing

基于价值的定价

Price between the next-best alternative and your perceived value.

[Cost of doing nothing] ... [Next-best alternative] ... [YOUR PRICE] ... [Perceived value delivered]

Step 1: Define the next-best alternative

What would the customer do if your product didn't exist?
A competitor? A spreadsheet? Manual process? Hiring someone?
What does that cost them?

Step 2: Estimate value delivered

Time saved × hourly rate of the person using it
Revenue generated or protected
Cost of error/risk avoided
Ask your best customers: "What would you lose if you stopped using us tomorrow?"

Step 3: Price in the middle

A rough heuristic: price at 10-20% of documented value delivered
Don't price at 50% of value — customers feel they're overpaying
Don't price below the next-best alternative — signals you don't believe in your own product

Conversion rate as a signal:

40% trial-to-paid: likely underpriced — test a price increase
15-30%: healthy for most SaaS
<10%: pricing may be high, or trial-to-paid funnel has friction

定价介于次优替代方案的成本与客户感知价值之间。

[无产品时的成本] ... [次优替代方案成本] ... [您的定价] ... [客户感知的交付价值]

步骤1：定义次优替代方案

如果没有您的产品，客户会怎么做？
使用竞品？电子表格？手动流程？雇佣专人？
这些方案的成本是多少？

步骤2：估算交付的价值

节省的时间 × 使用人员的时薪
产生或保护的营收
避免的错误/风险成本
询问您的核心客户：“如果明天停止使用我们的产品，您会损失什么？”

步骤3：在中间区间定价

粗略准则：定价为已记录交付价值的10-20%
不要定价为价值的50%——客户会觉得被过度收费
不要定价低于次优替代方案——这会传递出您对自身产品缺乏信心的信号

转化率作为参考信号：

试用转付费转化率>40%：可能定价偏低——测试提高20-30%的价格
15-30%：对大多数SaaS产品来说是健康的转化率
<10%：定价可能过高，或试用转付费流程存在阻碍

Pricing Research Methods

定价调研方法

Van Westendorp Price Sensitivity Meter

Van Westendorp价格敏感度测试法

Four questions, asked to current customers or target segment:

At what price would this product be so cheap you'd question its quality?
At what price would this product be a bargain — great deal?
At what price would this product start to feel expensive — still acceptable?
At what price would this product be too expensive to consider?

Interpret the results: Plot the four curves. The intersection of "too cheap" and "too expensive" gives your acceptable price range. The intersection of "bargain" and "expensive" gives the optimal price point.

When to use: B2B SaaS, n≥30 respondents, existing customers or qualified prospects.

向现有客户或目标群体提出四个问题：

价格低到什么程度会让您质疑该产品的质量？
价格低到什么程度会让您觉得这是一笔划算的交易？
价格高到什么程度会让您开始觉得昂贵，但仍可接受？
价格高到什么程度会让您完全无法考虑购买？

结果解读： 绘制四条曲线。“过低”与“过高”曲线的交点给出可接受的价格范围。“划算”与“昂贵”曲线的交点给出最优价格点。

适用场景： B2B SaaS、受访者数量≥30、现有客户或合格潜在客户。

MaxDiff Analysis

MaxDiff分析

Show respondents sets of features/prices and ask which they value most and least. Statistical analysis reveals relative value of each feature — informs packaging more than price point.

When to use: When deciding which features to put in which tier.

向受访者展示多组功能/价格组合，询问他们最看重和最不看重的选项。通过统计分析揭示每个功能的相对价值——更多用于指导产品打包而非确定价格点。

适用场景： 决定哪些功能放入哪个层级时。

Competitor Benchmarking

竞品基准对比

Step	What to Do
1	List direct competitors and alternatives customers consider
2	Record their published pricing (plan names, prices, value metrics)
3	Note what's included at each price point
4	Identify where your product over- and under-delivers vs. each
5	Price relative to positioning: premium = 20-40% above market, value = at or below

Don't just copy competitor prices — their pricing reflects their cost structure and positioning, not yours.

步骤	操作内容
1	列出客户会考虑的直接竞品及替代方案
2	记录它们的公开定价（套餐名称、价格、价值指标）
3	记录每个价格点包含的内容
4	确定您的产品相对于每个竞品在哪些方面超出或不足
5	根据定位定价：高端定位=比市场价高20-40%，性价比定位=等于或低于市场价

不要直接复制竞品价格——它们的定价反映了自身的成本结构和定位，而非您的。

Price Increase Strategies

涨价策略

Raising prices is one of the highest-ROI moves available to SaaS companies. Most wait too long.

提高价格是SaaS公司能采取的最高ROI举措之一，大多数公司都等待过久。

Strategy Selection

策略选择

Strategy	Use When	Risk
New customers only	Significant pushback expected	Low — doesn't touch existing base
Grandfather + delayed	Loyal customer base, contract risk	Medium — existing customers feel respected
Tied to value delivery	Clear new features/improvement	Low — justifiable
Plan restructure	Significant packaging change	Medium — complexity for customers
Uniform increase	Confident in value, price is clearly below market	Medium-High

策略	适用场景	风险
仅针对新客户	预计会遭遇强烈反对时	低——不影响现有客户群体
老客户保留原定价+延迟涨价	客户忠诚度高、存在合同风险时	中——现有客户会感受到尊重
与价值交付绑定	有明确的新功能/产品改进时	低——具备合理性
套餐重构	产品打包方案有重大变化时	中——对客户来说存在复杂性
统一涨价	对产品价值有信心、价格明显低于市场价时	中-高

Execution Checklist

执行清单

Quantify the move: Calculate new MRR at 100%, 80%, 70% retention of existing customers
Segment by risk: Annual contracts, champions vs. detractors, usage-based at-risk accounts
Set the date: 60-90 days notice for existing customers. 30 days minimum.
Communicate the reason: New features, rising costs, investment in [X] — be specific
Offer a path: Lock in current price for annual commitment, or give a 3-month window
Arm your CS team: FAQ, talking points, approved offer authority
Monitor for 60 days: Churn rate, downgrade rate, support ticket volume

Expected churn from a 20-30% price increase: 5-15%. If your net revenue impact is positive, proceed.

量化影响： 计算现有客户留存率为100%、80%、70%时的新MRR
按风险细分客户： 年度合同客户、支持者与批评者、基于使用量的高风险客户
确定日期： 提前60-90天通知现有客户，最少提前30天
说明原因： 新功能、成本上升、对[某领域]的投入——要具体
提供过渡方案： 签订年度合同可锁定当前价格，或给予3个月的缓冲期
赋能客户成功团队： 提供FAQ、沟通要点、批准的优惠权限
监控60天： 客户流失率、降级率、支持工单数量

20-30%涨价带来的预期流失率： 5-15%。如果净营收影响为正，即可推进。

Pricing Page Design

定价页面设计

The pricing page converts intent to purchase. Design it with that job in mind.

定价页面负责将客户意向转化为购买行为，设计时需围绕这一目标展开。

Above the Fold

首屏内容

Must have:

Plan names (simple: Starter / Pro / Enterprise, or named after customer segment)
Price with billing toggle (monthly/annual — annual should show savings)
3-5 bullet differentiators per plan
CTA button per plan
"Most popular" badge on recommended tier

必须包含：

套餐名称（简洁：入门版/专业版/企业版，或按客户群体命名）
价格及计费周期切换（月度/年度——年度需显示优惠）
每个套餐3-5个差异化要点
每个套餐对应的CTA按钮
在推荐层级上标注“最受欢迎”徽章

Below the Fold

首屏下方内容

Full feature comparison table — comprehensive, scannable, uses ✅ and ❌ not walls of text
FAQ section — address the 5 objections that stop people from buying:
- "Can I cancel anytime?"
- "What happens when I hit limits?"
- "Do you offer refunds?"
- "Is my data secure?"
- "What if I need to upgrade/downgrade?"
Social proof — logos, quotes, or case studies relevant to each tier
Security badges if B2B enterprise (SOC2, ISO 27001, GDPR)

完整功能对比表——全面、易读，使用✅和❌而非大段文字
FAQ板块——解决阻止客户购买的5个常见异议：
- “我可以随时取消吗？”
- “达到限制后会怎样？”
- “你们提供退款吗？”
- “我的数据安全吗？”
- “如果我需要升级/降级怎么办？”
社交证明——与各层级相关的客户logo、评价或案例研究
安全认证徽章（若面向B2B企业客户）：SOC2、ISO 27001、GDPR

Annual vs. Monthly Toggle

年度与月度切换

Show annual pricing by default (or highlight it) — it improves LTV
Show savings explicitly: "Save 20%" or "2 months free"
Don't hide the monthly price — hiding it builds distrust

See references/pricing-page-playbook.md for design specs and copy templates.

默认显示年度定价（或突出显示）——这能提升LTV
明确显示优惠：“节省20%”或“免费2个月”
不要隐藏月度价格——隐藏会引发不信任

查看references/pricing-page-playbook.md获取设计规范及文案模板。

Proactive Triggers

主动触发提示

Surface these without being asked:

Conversion rate >40% trial-to-paid → Strong signal of underpricing. Flag: test 20-30% price increase.
All customers on the middle tier → No upsell path. Flag: enterprise tier needed or feature lock-in missing.
Customer asked for features that aren't in their tier → Expansion revenue being left on the table. Flag: feature gatekeeping review.
Churn rate >5% monthly → Before raising prices, fix churn. Price increases accelerate churners.
Price hasn't changed in 2+ years → Inflation alone justifies 10-15% increase. Flag for strategic review.
Only one pricing option → No anchoring, no upsell. Flag: add a third tier even if rarely purchased.

无需询问即可主动提出以下提示：

试用转付费转化率>40% → 强烈的定价偏低信号。提示：测试提高20-30%的价格。
所有客户都选择中间层级 → 没有向上销售路径。提示：需要增加企业层级或完善功能限制。
客户要求其套餐中未包含的功能 → 正在错失拓展营收的机会。提示：重新审视功能权限设置。
月度客户流失率>5% → 在涨价前先解决流失问题，涨价会加速客户流失。
价格已2年以上未调整 → 仅通货膨胀就足以支撑10-15%的涨价。提示：进行战略评估。
仅有一种定价选项 → 没有价格锚点，也没有向上销售空间。提示：即使很少有人购买，也要增加第三个层级。

Output Artifacts

输出成果

When you ask for...	You get...
"Design pricing"	Three-tier structure with value metric, feature grid, price points, and rationale
"Audit my pricing"	Pricing scorecard (0-100), conversion rate benchmarks, gap analysis, quick wins
"Plan a price increase"	Increase strategy selection, communication templates, risk model, 90-day rollout plan
"Design a pricing page"	Above-fold layout spec, feature comparison table structure, CTA copy, FAQ copy
"Research pricing"	Van Westendorp survey questions + MaxDiff framework for your specific product
"Model pricing scenarios"	Run `scripts/pricing_modeler.py` with your inputs

您的需求	输出内容
"设计定价方案"	包含价值指标、功能网格、价格点及设计理由的三层级结构
"审核我的定价方案"	定价评分卡（0-100分）、转化率基准分析、差距分析、快速优化建议
"规划涨价策略"	涨价策略选择、沟通模板、风险模型、90天推广计划
"设计定价页面"	首屏布局规范、功能对比表结构、CTA文案、FAQ文案
"调研定价方案"	针对您产品的Van Westendorp调研问题+MaxDiff分析框架
"模拟定价场景"	使用您的输入运行 `scripts/pricing_modeler.py`

Communication

沟通规范

All output follows the structured communication standard:

Bottom line first — recommendation before justification
What + Why + How — every recommendation has all three
Actions have owners and deadlines — no vague "consider"
Confidence tagging — 🟢 verified benchmark / 🟡 estimated / 🔴 assumed

所有输出遵循结构化沟通标准：

先讲结论——先给出建议再说明理由
包含内容+原因+方法——每项建议都需涵盖这三点
行动需明确负责人和截止日期——避免模糊的“考虑”
置信度标记——🟢 已验证基准 / 🟡 估算值 / 🔴 假设值