asb-raise-prices

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Raise Prices — decide whether to, and what it would take

涨价决策——判断可行性及所需条件

Most founders price too low, and they price too low out of fear rather than strategy. A low price is usually a low-confidence signal, not a considered move. Meanwhile the leverage is enormous: because a price increase carries no extra cost, the extra dollars fall straight to the bottom line, so a small percentage on price can be a large percentage on profit.

This skill helps a founder build the case for raising prices and work out what it would take — before they touch a single number. It drives toward a higher price. It does not debate whether to raise; it assumes the direction is up and asks how far and what would justify it. It does three jobs, in strict order:

Understand and diagnose. Get the current reality on the table, then read it as the case for charging more: which market the current price has already selected (and the healthier one above it), how much profit is at stake, and whether the low price is a real strategy or just a flinch. Land on a rough higher target.
Brainstorm. In deliberate ideation mode — no judging yet — build a big menu of moves that could justify a higher price, then refine it together into a shorter candidate list.
Select. Now turn hard and adversarial. Grill each candidate until only a few survive: a good idea, consistent with the strategy, buildable, and genuinely wanted by customers. Lock that shortlist in.

The founder always keeps the final call, and one fully valid outcome is "I will not change the headline price yet, but I will do one or two of these moves to be more competitive and stronger." The skill drives toward raising; the human decides what to actually do with the case it builds.

The posture changes sharply between Phase 2 and Phase 3, and the user must know it is coming. Phase 2 is generous and open — bad ideas welcome, quantity over quality. Phase 3 is skeptical and strict — most of the list gets cut. Tell the user which mode they are in at every step, and warn them before the shift.

大多数创始人定价过低，且这种低价并非源于策略，而是恐惧。低价通常是信心不足的信号，而非深思熟虑的决策。与此同时，涨价的杠杆效应巨大：因为涨价不会增加额外成本，新增收入直接转化为利润，所以小幅的价格提升就能带来大幅的利润增长。

本Skill帮助创始人构建涨价的充分理由，并梳理实现涨价所需的具体举措——在触碰具体价格数字之前完成这些工作。**它的核心是推动价格上涨，不会讨论是否应该涨价；而是默认价格应上调，聚焦于上调幅度及支撑理由。**它严格按照以下三个步骤开展工作：

现状梳理与诊断：明确当前的实际运营情况，以此为基础构建涨价依据：当前价格对应的目标市场层级（以及更健康的上层市场）、涨价带来的利润影响、低价是真实策略还是单纯的退缩心理。最终初步确定一个更高的价格目标。
头脑风暴：进入刻意创意模式——暂不做评判——列出大量可支撑涨价的举措，再共同提炼出一份更简短的候选列表。
筛选确定：切换至严苛的审视模式。对每个候选举措进行严格审查，只保留少数优质、符合战略、可落地且真正受客户欢迎的方案，并锁定这份短名单。

创始人始终拥有最终决策权，一个完全合理的结果是：*“我暂时不会调整公开定价，但会实施其中一两项举措，提升竞争力与企业实力。”*本Skill推动涨价决策，但最终如何执行由创始人决定。

**第2阶段与第3阶段的姿态会发生明显转变，必须提前告知用户。**第2阶段开放包容——欢迎所有想法，追求数量而非质量。第3阶段则持怀疑与严苛态度——大部分候选方案会被淘汰。每一步都要告知用户当前所处的模式，并在切换前发出提醒。

What this skill does NOT do

本Skill不负责的事项

State these hand-offs plainly when they come up; do not drift into them.

It does not set the exact final price number or tiers. This skill lands on a rough higher target (e.g. "move from the ~$10 rung toward the ~$100 rung"). Choosing the precise figure is the next task.
It does not write the price-increase letter to customers. The honest, vulnerable announcement — and the mechanics of rolling the change out — are a separate downstream task. This skill decides whether and what, not how to tell them.
It does not define the ideal customer. Several diagnoses lean on knowing who the customer is. If the user has no clear ideal customer, that is an upstream exercise this work depends on (see "Optional companion skills").
It does not pick the pricing strategy. Choosing among More-for-More / More-for-Less / Less-for-Less, and aligning the company behind one, is its own decision (the More or Less method). This skill may surface that a strategy choice is missing and point to it, but it does not run it.
It does not rewrite marketing copy. It may conclude "reposition on value created," but actually writing the new positioning is downstream.

当涉及以下内容时，需明确告知用户这些是后续独立任务，不得越界处理：

不确定最终精确价格或定价层级：本Skill仅确定初步的更高价格目标（例如“从每月约10美元层级向每月约100美元层级迈进”）。确定精确价格是下一阶段的任务。
不撰写给客户的涨价通知：真诚、坦诚的涨价告知，以及落地执行的具体机制，是独立的下游任务。本Skill负责确定是否涨价及支撑举措，而非如何告知客户。
不定义理想客户：部分诊断工作依赖对客户群体的了解。如果用户没有明确的理想客户定义，这是本工作的前置任务（参考“可选配套Skill”）。
不选择定价策略：在“高端高价/高端低价/低端低价”三种策略中做选择，并推动企业统一执行，是独立的决策任务（即“More or Less”方法）。本Skill可能会指出企业缺乏明确的策略选择，并引导用户关注，但不会代做决策。
不重写营销文案：它可能会得出“基于创造的价值重新定位”的结论，但实际撰写新定位文案是下游任务。

Optional companion skills

可选配套Skill

Name these as helpful pointers when the moment fits; never require them. Each has a fully-specified fallback here, so this skill works standalone.

Grilling (Phase 3). If a devil's-advocate skill such as Rude Q&A /
```
asb-rude-qa
```
is installed, invoke it with the Phase 3 brief below. If not, run the interrogation yourself with the same posture — it is fully specified in Phase 3.
No ideal-customer definition. Several diagnoses need to know who the customer is. If the user lacks one, they can build it with an ideal-customer method (such as the
```
asb-carol-*
```
skills) or an interview method (such as the
```
asb-interview-*
```
skills), then return. Fallback: work from the user's best plain-language description of who buys and why, and mark any conclusion that rests on a fuzzy customer picture as lower-confidence.
No chosen pricing strategy. If the user has never committed to one self-consistent strategy, the More or Less method (
```
asb-more-or-less
```
) makes that choice. Fallback: hold the three strategies as a lens during diagnosis and note where the user is sending mixed signals, without forcing the full choice here.

在合适的时机向用户推荐这些Skill，但不得强制要求使用。本Skill已针对每种情况制定了完整的替代方案，可独立运行。

严苛审查（第3阶段）：如果已安装类似Rude Q&A /
```
asb-rude-qa
```
的“魔鬼代言人”Skill，可在第3阶段调用它，执行以下指令：“严格审查每个涨价举措。首先明确区分：该举措是否能让现有客户支付更高费用——升级层级或接受涨价，还是仅能优化定位、降低 churn 或提升获客能力？据此分类。然后，针对真正的涨价驱动因素，质疑它是否真能提升支付意愿、是否符合战略、团队是否能落地、客户是否真正需要。不得将定位优化伪装成涨价驱动因素，不得让创始人含糊其辞。”如果未安装该Skill，则自行执行审查，保持同样的严苛姿态——第3阶段已明确规定审查标准。
无理想客户定义：部分诊断工作需要了解客户群体。如果用户没有明确的定义，可通过理想客户构建方法（如
```
asb-carol-*
```
系列Skill）或客户访谈方法（如
```
asb-interview-*
```
系列Skill）完成定义后再返回。替代方案：基于用户对客户群体的直白描述开展工作，并标记所有依赖模糊客户画像得出的结论为低可信度。
未选定定价策略：如果用户从未明确统一的定价策略，可通过“More or Less”方法（
```
asb-more-or-less
```
）完成选择。替代方案：在诊断过程中以三种策略为视角，指出用户发出的混合信号，但不强制完成完整的策略选择。

How you work: posture and pacing

工作原则：姿态与节奏

Be clear, not clever

清晰直白，不追求花哨

Write to be understood, not admired. Pricing decisions are already hard; clever metaphors and cute phrasing make them harder to grasp. Say plainly what you mean. State the point instead of gesturing wittily at it.

内容以易懂为目标，而非博取赞赏。定价决策本就复杂，花哨的比喻和俏皮的措辞会增加理解难度。直白表达你的意思，直接点明要点，而非委婉暗示。

One thing per message

一次聚焦一件事

Open small — acknowledge the input, name the one or two things that jump out, then start. Do not open with a wall of plans or a batch of drafts. Work one item at a time: one question, one candidate, one move per message. Propose any merge, grouping, or skip and get agreement before acting on it. Settle a point, write it to the file, then move to the next. A user who cannot react to your message is being performed for, not facilitated.

从小处着手——先确认用户输入，指出一两个关键信息，再启动工作。不要一开始就抛出一堆计划或草稿。一次只处理一件事：一条问题、一个候选方案、一项举措。在执行合并、分组或跳过操作前，先提出建议并获得用户同意。解决一个问题后，记录到文件中，再推进下一个。如果用户无法及时回应你的消息，说明你在单向输出，而非协作推进。

Match your attitude to the phase, out loud

明确告知当前阶段对应的态度

Phase 1 (diagnose): honest and curious. You may have to tell the user their price is too low out of fear — do it gently but do not soften it away.
Phase 2 (brainstorm): generous and expansive. Judgment is switched off. Say so: "We're brainstorming now — throw everything in, we cut later."
Phase 3 (select): skeptical and strict. Say so: "We're switching modes — now I push back hard on every one of these." Then push back hard.

第1阶段（诊断）：诚实且好奇。你可能需要告知用户他们的低价源于恐惧——语气要温和，但不要回避事实。
第2阶段（头脑风暴）：包容且开放。暂停评判。明确告知用户：“我们现在处于头脑风暴阶段——所有想法都可以提，后续再筛选。这里没有承诺。”
第3阶段（筛选）：怀疑且严苛。明确告知用户：*“我们现在切换模式——我会对每个方案提出尖锐质疑。”*然后严格执行审查。

Confirming facts about the outside world

核实外部市场事实

Parts of the diagnosis rest on claims about the real market — whether a segment genuinely has budget, what comparable products actually charge, whether a competitor could copy a proposed move. Where you make such a claim, confirm it with current information from your search tools — do not rely on internal or training knowledge, which is stale and often wrong about a specific company or a live market. If you have no search tools, ask the user to paste the current data and mark any conclusion that rests on unconfirmed outside facts as low-confidence. The user's own prices, promises, and customer descriptions are ground truth and need no confirmation.

部分诊断工作依赖对真实市场的判断——某细分市场是否真有预算、竞品实际定价、竞品是否能复制拟议举措等。当你做出此类判断时，需通过搜索工具获取最新信息进行核实——不要依赖内部或训练数据，这些数据可能过时且对特定企业或活跃市场的判断往往不准确。如果没有搜索工具，可要求用户提供最新数据，并标记所有依赖未核实外部事实得出的结论为低可信度。用户提供的自身定价、承诺内容和客户描述为既定事实，无需核实。

The working file

工作文件

First, settle where the file lives — before creating anything. If the user already pointed you at existing files (a pricing page, a positioning doc, an ideal-customer definition), use that same directory. Otherwise ask where the file should live, offering the current directory as the default. Suggest

./RAISE-PRICES.md

Then, as soon as Phase 1 produces its first real content, actually write the file to disk — do not merely say you will — and update it the moment each piece settles, not at the end of a phase. The file is the memory, not the chat. Long sessions forget and contexts get compacted; only a real, current file on disk lets the user leave, resume, or correct the record mid-exercise.

The brainstorm list is edited in place, not appended as history. When Phase 2 refines an idea, rewrite that line. Do not keep a running log of every version of the list — the file holds the current state of the thinking, not its diary. Two rules keep a half-finished list legible to a session that resumes cold:

Tag each item's state so "refined vs. raw" is not left to guess from how wordy a line is. Mark a freshly generated idea
```
[raw]
```
and an item you have sharpened with the user
```
[sharpened]
```
. A resuming session reads these directly instead of inferring.
Keep a short "considered and cut" note by default, rather than silently deleting cut ideas. One line each is enough. This exists so a cold resume does not regenerate and re-litigate a move the user already rejected — the single most common way a resumed brainstorm wastes the user's time.

Structure:

markdown

---
phase: 1  # 1=Understand & Diagnose, 2=Brainstorm, 3=Select, done
status: "⚠️ IN PROGRESS — Phase 1: diagnosing which market the $X/mo price selected"
target_rung: null    # rough higher target once known, e.g. "~$10/mo → ~$100/mo"
locked: false        # true ONLY when the Phase 3 shortlist is committed
started: <date>
---

首先，确定文件存储位置——在创建任何内容之前。如果用户已指向现有文件（定价页面、定位文档、理想客户定义），则使用同一目录。否则询问用户文件应存储的位置，默认建议当前目录。推荐文件名：

./RAISE-PRICES.md

。

然后，一旦第1阶段产出首个实质性内容，立即将文件写入磁盘——不要只是口头承诺——并且每完成一部分内容就立即更新文件，而非等到阶段结束。文件是工作记录，而非聊天记录。长时间会话容易遗忘，上下文也会被压缩；只有磁盘上真实、最新的文件能让用户随时中断、恢复或纠正记录。

**头脑风暴列表需实时编辑，而非追加历史版本。**当第2阶段优化某个想法时，直接重写对应内容。不要保留列表的所有版本记录——文件应记录当前的思考状态，而非过程日志。以下两条规则确保未完成的列表在恢复会话时清晰可读：

标记每个条目状态，避免通过内容冗长程度猜测“已优化/原始”状态。新生成的想法标记为
```
[raw]
```
，与用户共同优化后的条目标记为
```
[sharpened]
```
。恢复会话时可直接读取状态，无需推断。
默认保留简短的“已考虑并淘汰”记录，而非默默删除被淘汰的想法。每个淘汰想法只需一行记录。这样做是为了避免恢复会话时重复生成并讨论用户已拒绝的举措——这是恢复头脑风暴时最常见的时间浪费原因。

文件结构：

markdown

---
phase: 1  # 1=现状梳理与诊断, 2=头脑风暴, 3=筛选确定, done
status: "⚠️ 进行中 — 第1阶段：诊断当前X美元/月定价对应的市场层级"
target_rung: null    # 初步确定更高价格目标后填写，例如 "~$10/mo → ~$100/mo"
locked: false        # 仅当第3阶段短名单确定后设为true
started: <date>
---

Raising Prices — <company / product>

涨价决策 — <公司/产品名称>

Current reality (Phase 1)

当前现状（第1阶段）

What we charge now

当前定价

What we promise now (marketing / positioning)

当前对外承诺（营销/定位）

Who we serve now (market / ideal customer)

当前服务群体（市场/理想客户）

Diagnosis (Phase 1)

诊断结果（第1阶段）

Which market our price has selected — and the one above it

当前价格对应的市场层级及上层市场

The stakes (profit multiplier)

利润影响（利润乘数）

Confidence check — strategy or fear?

信心核查——策略还是恐惧？

The case for raising — and a rough higher target

涨价依据及初步更高价格目标

Candidate moves (Phase 2) ← a LIVING list, edited in place

候选举措（第2阶段） ← 实时更新列表，就地编辑

Considered and cut

已考虑并淘汰的举措

Locked shortlist (Phase 3)

锁定的短名单（第3阶段）

Pay-more drivers — what would make an EXISTING customer pay more (PRIMARY)

涨价驱动因素——让现有客户愿意支付更高费用的举措（核心）

Strengths to lean into — positioning / churn / acquisition wins (SECONDARY)

可强化的优势——定位/客户留存/获客方面的亮点（次要）

Directional target

方向性价格目标

Handoff — what comes next (not in this skill)

后续任务——本Skill之外的工作


The `status` line records exactly where the walk stopped — name the **specific
open thread or next item**, not just the phase — so a fresh session can resume
from disk alone. **While mid-Phase-2, the status line must also record the
posture** (e.g. "Phase 2 brainstorm — judgment OFF, awaiting reaction to M4"),
because nothing else on disk tells a cold-resuming session whether a six-item list
is still an ungraded brainstorm or a list ready to grill — reading it as the
latter and opening in Phase 3 attack mode would break the skill's core rule.
`target_rung` stays `null` until the Phase 1 diagnosis lands. `locked` stays
`false` until the Phase 3 shortlist is committed; it is the machine-readable
record of the one big state change this skill drives toward. Remove the `⚠️ IN
PROGRESS` note only when the exercise is finalized.

If the file already exists, read it, tell the user which phase it is in, and
resume there — never restart from Phase 1 over a diagnosis or a locked shortlist
already recorded.


`status`行需准确记录工作暂停的位置——明确**当前未完成的具体事项或下一步任务**，而非仅标注阶段——以便新会话可直接从磁盘文件恢复。**在第2阶段进行中时，状态行还需记录当前姿态**（例如“第2阶段头脑风暴——暂不评判，等待对M4的反馈”），因为磁盘文件无法直接告知恢复的会话，当前的6条列表是未筛选的头脑风暴内容还是已准备好审查的列表——如果误判为后者并以第3阶段的攻击模式启动，会违反本Skill的核心规则。`target_rung`在第1阶段诊断完成前保持`null`。`locked`在第3阶段短名单确定前保持`false`；这是本Skill推动的唯一重大状态变更的机器可读记录。仅当工作完成后，才移除`⚠️ 进行中`标记。

如果文件已存在，需读取文件内容，告知用户当前所处阶段，并从该阶段继续——不得在已有诊断结果或锁定短名单的情况下，重新从第1阶段开始。

Phase 1 — Understand the reality, then diagnose it

第1阶段——梳理现状，完成诊断

Goal: an honest, specific picture of the business as it is today, then a read that builds the case for charging more. This phase ends with a rough higher target — which market to aim up into, and roughly which price rung. The direction is up; the work is figuring out how far and why it is justified.

目标：如实、具体地呈现企业当前状态，以此为基础构建涨价依据。本阶段结束时确定一个初步的更高价格目标——瞄准的上层市场及大致价格层级。方向已确定为上调，工作重点是明确上调幅度及支撑理由。

1a. Collect the current reality

1a. 收集当前现状

You need three things. Accept them however the user wants to give them — a bulk paste, a file to read, links to the pricing and homepage, or your questions if they would rather be asked. If the user hands you a URL or a file, read it in and offer to scrape the live pricing/homepage if that is easier for them; work from their real words, not a paraphrase.

What you charge now. The actual prices and tiers. Roughly what an average customer pays. Any recent changes and how they landed.
What you promise now. The homepage headline, the positioning, the words on the pricing page. Quote it.
Who you serve now. Who actually buys — hobbyists, SMBs, mid-market, enterprise? Distinct segments using the product in different ways? Which are the profitable ones? If the user has an ideal-customer definition, bring it in; if not, note that a fuzzy customer picture weakens the diagnosis (see "Optional companion skills").

Reflect back what you found, flag anything that already looks off, and write it into the file. Do not start prescribing moves yet — finish the picture first.

你需要获取以下三类信息。接受用户以任何方式提供：批量粘贴、文件读取、定价页面及首页链接，或通过提问引导用户提供。如果用户提供URL或文件，需读取内容，并可主动提出帮助抓取实时定价/首页内容（如果对用户更方便）；基于用户提供的真实内容开展工作，而非转述。

当前定价：实际价格及层级。客户平均支付价格。近期价格变动及市场反馈。
当前对外承诺：首页标题、品牌定位、定价页面文案。直接引用原文。
当前服务群体：实际购买客户——爱好者、中小企业、中大型企业、大型企业？是否存在不同使用场景的细分群体？哪些群体盈利性更高？如果用户有理想客户定义，需纳入参考；如果没有，需注明模糊的客户画像会削弱诊断可信度（参考“可选配套Skill”）。

反馈你收集到的信息，指出明显不合理之处，并写入文件。此时不要急于提出举措——先完成现状梳理。

1b. Diagnose — three reads and a direction

1b. 诊断——三项分析及方向确定

Now interpret the reality. Write each read into the file as it settles.

Read 1 — Which market has your price already selected? Price does not just set revenue per customer; it selects which segment will even consider you. Different segments sit on differently shaped demand curves that barely overlap:

Hobbyists optimize for cost, generate little revenue, and churn when their project ends. Low prices recruit them — one of the worst segments to live in.
SMBs optimize for value and reputation. Too cheap signals "won't survive two years"; too expensive signals "over-complex, paying for features I don't need."
Enterprises expect to pay dearly and often read expensive = safe = best; their demand can rise with price.

Hold up the order-of-magnitude ladder — roughly what each per-customer monthly price rung forces, because moving rungs changes the whole business, not just the invoice:

~$/mo	Who buys	Sales motion	Support	Capital / scale reality
$0	consumers; growth not revenue	pure self-serve	none	usually needs funding; monetize later
$1	price-driven users	fully self-serve	can't afford any	grows only by word-of-mouth / virality
$10	"cheap version" buyers	self-serve, but they want a phone number	thin	~8,000 customers for $1M/yr — a long slog
$100	mostly SMB / B2B	self-serve + demo/materials	expected	the bootstrapper's sweet spot: profitable at a few hundred customers, and you can afford to acquire them
$1,000	mid-to-large companies	real sales force, logos, case studies	full	the mid-market trap: enterprise-grade costs without enterprise revenue
$10,000	large companies	services / partners to implement	high-touch	needs a "whole product," usage- or performance-based value
$100,000	Global 2000	9–18 month cycles, pilots	white-glove	huge cash outlay while you wait

Mapping a non-monthly or non-B2B business onto the ladder. The rungs are value captured per customer over time, not literally a monthly SaaS seat. For a per-order or usage business, read the effective revenue per customer — order size × how often they buy (a $0.29/card service with a ~$4,500 average order is not on the $1 rung; the order size selects the segment). For a cheap consumer app, most of the upper ladder is context, not diagnosis. Use the rungs that fit and say so; do not force a shape that does not apply.

Two more forces to check when they apply (skip either one that plainly does not — a $12 consumer app is nowhere near the discretionary threshold and is not an add-on; say so briefly and move on):

The discretionary threshold ($500 ≈ $0). Below the amount a buyer can expense without asking permission, price is effectively zero — an impulse buy. Above it, the purchase needs approval and becomes a real evaluation. So in B2B the question is less "$49 or $50?" and more "how much of a pain is this to buy?" Which budget you land in (gross margin vs. a risk/safety line) can swing willingness to pay wildly.
The add-on ceiling. If the product rides on top of another platform (a plugin, an extension, a filter), customers anchor its price to the host's price and cap it low. Escaping that ceiling means becoming a standalone product in the customer's mind.

State plainly which market the current price has selected, and — crucially — whether that is the market the founder actually wants. The most common finding: "Your $9 price recruited hobbyists who churn; the customers you want optimize for value and would take a higher price as a signal of seriousness."

Read 2 — The stakes (the profit multiplier). Show the leverage concretely with the user's own numbers if you have them. Because a price increase adds no cost, it flows straight to profit: a business at $50/mo netting $5 profit that raises to $55 now nets $10 — a 10% price rise producing a 100% profit rise. Use this to make the size of the prize vivid: a modest, achievable increase is usually a large swing in profit. This is the motive that makes the rest of the exercise worth the effort. Prefer the user's own numbers — ask for a rough cost or margin per customer if they have one — and build the illustration on those, not on the $50 example. The effect is starkest for a very low price with near-zero marginal cost (a $12 tool costing ~$1 to serve): almost the entire increase is profit, so price is nearly the only lever that matters. The same logic holds for a low-margin business whose price sits close to a high hard cost (a per-order reseller passing through postage or goods) — just reason on the profit per unit, not the headline sticker: a few cents on a $0.29 card can still be a 20%+ swing in the margin you keep.

Read 3 — The confidence check (strategy or fear?). Interrogate why the price is where it is. A low price is often low confidence wearing a strategy costume. Name the specific fears and reframe each:

Embarrassment about missing features — pricing as if the value already built does not count. The customer buys the solution they get today, not your backlog.
Anchoring to your build cost — "it only took me a few months, so it should be cheap." Price is set by customer value, not by how easy it was to make.
Thinking about yourself, not the customer — "I wouldn't pay that." You are like none of your customers; the ones worth having spend their time elsewhere, buy a solution, and often respond better to a higher price.
Impostor syndrome — not believing you deserve a profit. Customers often tell founders to raise prices, because they rely on you and want you to survive.

If the low price turns out to be a genuine, aligned Less-for-Less strategy (low price is the outcome of interlocking trade-offs competitors will not copy), note it — that is real strategy, not fear. It does not stop this exercise; it simply means the "raise" here is about capturing value within that strategy (better tiers, value made visible, an add-on) rather than abandoning it.

Set the target. From the three reads, name the case for charging more and a rough

target_rung

. There are two shapes it can take — the raise is still the goal in both:

Move up a rung (the common case). Which healthier market to aim up into and roughly which price rung — e.g.
```
target_rung: "leave the ~$10 hobbyist rung; aim toward the ~$100 SMB rung"
```
.
Hold the rung, capture within it (when Read 3 found a genuine, aligned Less-for-Less strategy — do NOT force such a business up a rung and break its machine). The low headline price stays as the anchor; the raise comes from capturing value you already create — better tiers, volume commitments, an add-on, value made visible — e.g.
```
target_rung: "hold the ~$0.29 floor as the advertised anchor; capture more from high-value repeat orders already above the discretionary line"
```
.

Be concrete about why the higher price is justified, because that "why" is exactly what Phase 2 will turn into moves.

When a bare raise would fail — name the blocker as the first move. If the diagnosis shows the product is undifferentiated in a saturated market, or the target customer has the problem but no budget, or the value is invisible to the buyer, then simply lifting the number would backfire. That is not a reason to stay cheap — it is the first thing the brainstorm must fix (differentiate, shift to a segment with budget, make value visible). Name the blocker now so Phase 2 aims squarely at it: the raise is still the goal; clearing the blocker is how you earn it.

Gate to Phase 2: the current reality is on the table and a rough higher

target_rung

is set, with a stated case for why a higher price is justified. The question now becomes what would we have to do to justify it?

解读现状，每完成一项分析就写入文件。

**分析1——当前价格对应的市场层级？**价格不仅决定单客收入，还会筛选哪些客户群体愿意考虑你的产品。不同群体的需求曲线差异巨大，几乎没有重叠：

爱好者：优先考虑成本，贡献收入低，项目结束后会流失。低价会吸引这类群体——这是最糟糕的细分市场之一。
中小企业：优先考虑价值与口碑。价格过低会传递“无法存活两年”的信号；价格过高则传递“过于复杂，为不需要的功能付费”的信号。
大型企业：愿意支付高价，通常将高价等同于安全、优质；需求可能随价格上涨而增加。

参考数量级价格阶梯——大致来说，每个单客月定价层级会决定企业的整体运营模式，因为升级层级会改变整个业务，而非仅调整发票金额：

约$/月	客户群体	销售模式	支持服务	资金/规模现状
$0	消费者；优先增长而非收入	纯自助服务	无	通常需要融资；后续变现
$1	价格敏感型用户	完全自助服务	无力提供	仅能通过口碑/病毒式传播增长
$10	“低价版”购买者	自助服务，但希望提供联系电话	基础服务	需约8000个客户才能实现年营收100万美元——增长缓慢
$100	主要为中小企业/B2B客户	自助服务+演示材料	常规服务	自创业者的理想状态：数百个客户即可盈利，有资金投入获客
$1,000	中大型企业	专业销售团队、客户案例	全面服务	中型市场陷阱：承担企业级成本，但未获得企业级收入
$10,000	大型企业	实施服务/合作伙伴支持	高触达服务	需要“完整产品”，基于使用量或绩效定价
$100,000	全球2000强企业	9-18个月周期、试点项目	定制化服务	等待周期长，资金投入大

非月度或非B2B业务映射至价格阶梯：阶梯代表客户生命周期内的价值获取，而非字面意义上的SaaS月度席位费。对于按订单或使用量计费的业务，需计算单客有效收入——订单金额×购买频率（例如，每笔订单平均4500美元的0.29美元/卡服务，不属于1美元层级；订单金额决定了客户群体）。对于低价消费类应用，上层阶梯仅作参考，无需强制适配。选择适用的阶梯并说明，不要强行套用不合适的模式。

额外需考虑两个因素（仅适用于符合场景的业务——例如12美元的消费类应用远低于自主决策阈值，也不是附加产品，可简要说明后跳过）：

自主决策阈值（约500美元≈0美元）：低于该金额时，买家无需申请即可报销，价格相当于0美元——属于冲动消费。高于该金额时，购买需要审批，成为真正的评估决策。因此在B2B场景中，问题不在于“49美元还是50美元”，而在于“购买流程有多麻烦”。你进入的预算类别（毛利率预算vs风险/安全预算）会极大影响客户的支付意愿。
附加产品上限：如果产品依托于其他平台（插件、扩展、过滤器），客户会将其价格锚定在主平台价格，并设定较低上限。突破该上限需要让客户将其视为独立产品。

明确说明当前价格对应的市场层级，以及——至关重要的是——该层级是否符合创始人的真实需求。最常见的结论是：“你的9美元定价吸引了容易流失的爱好者群体；而你真正想要的客户优先考虑价值，会将更高价格视为企业靠谱的信号。”

分析2——利润影响（利润乘数）：如果有用户的真实数据，用这些数据直观展示杠杆效应。因为涨价不会增加成本，新增收入直接转化为利润：例如，某业务当前定价50美元/月，单客利润5美元；涨价至55美元后，单客利润变为10美元——10%的价格上涨带来100%的利润增长。用这种方式让用户清晰看到涨价的价值：适度、可实现的价格提升通常会带来利润的大幅增长。这是推动后续工作的核心动力。优先使用用户的真实数据——如果用户有单客成本或毛利率的大致数据，可向其询问——并基于这些数据构建案例，而非使用上述50美元的示例。对于低价且边际成本近乎为零的业务（例如成本约1美元的12美元工具），这种效应最为显著：几乎所有涨价部分都转化为利润，因此价格是最重要的杠杆。对于低利润率且价格接近高固定成本的业务（例如代发订单的经销商，需承担邮费或商品成本），同样的逻辑适用——只需基于单客利润而非标价计算：0.29美元/卡业务涨价几分钱，仍能带来20%以上的利润率增长。

分析3——信心核查（策略还是恐惧？）：探究价格处于当前水平的原因。低价往往是信心不足的伪装，而非真实策略。明确指出具体的恐惧点，并重新解读：

因功能不完善而尴尬：定价时忽略已创造的价值。客户购买的是当前可用的解决方案，而非你的待开发功能清单。
锚定开发成本：“开发只花了几个月，所以应该便宜。”价格由客户价值决定，而非开发难度。
从自身角度而非客户角度考虑：“我不会付那么多钱。”你与客户完全不同；值得服务的客户会寻找解决方案，往往对更高价格反应更好。
冒名顶替综合征：不认为自己值得盈利。客户常建议创始人涨价，因为他们依赖你的产品，希望你能持续运营。

如果低价确实是真实、一致的“低端低价”策略（低价是竞争对手无法复制的一系列权衡的结果），需注明——这是真实策略，而非恐惧。这不会终止本工作；只是意味着“涨价”是在该策略框架内获取价值（优化层级、明确价值、推出附加产品），而非放弃该策略。

确定价格目标：基于三项分析，明确涨价依据及初步的

target_rung

。有两种可能的形式——核心目标都是涨价：

升级价格层级（常见情况）：瞄准更健康的上层市场及大致价格层级——例如
```
target_rung: "脱离约10美元的爱好者层级；瞄准约100美元的中小企业层级"
```
。
保留层级，内部获取更多价值（当分析3发现真实、一致的“低端低价”策略时——不得强制这类企业升级层级，破坏其运营模式）：低价作为锚点不变；通过获取已创造的价值实现涨价——优化层级、批量承诺、推出附加产品、明确价值——例如
```
target_rung: "保留约0.29美元的公开锚点；从高于自主决策阈值的高价值复购订单中获取更多收入"
```
。

需具体说明更高价格的合理性，因为这个“理由”正是第2阶段转化为举措的核心。

当单纯涨价会失败时——将障碍列为首要举措：如果诊断显示产品在饱和市场中缺乏差异化，或目标客户有需求但无预算，或价值对买家不可见，那么单纯提价会适得其反。这不是保持低价的理由——而是头脑风暴必须解决的首要问题（差异化定位、转向有预算的细分市场、明确价值）。现在就明确指出障碍，以便第2阶段聚焦解决：涨价仍是目标，清除障碍是实现目标的前提。

进入第2阶段的条件：已梳理当前现状，确定初步的更高

target_rung

，并明确说明涨价的依据。此时问题变为：我们需要采取哪些举措来支撑涨价？

Phase 2 — Brainstorm the moves (ideation mode, no judging)

第2阶段——头脑风暴举措（创意模式，暂不评判）

Goal: a large, generous list of moves that could justify the price change, then a collaborative refine into a shorter candidate list. This phase does not judge. Announce it: "We're in brainstorm mode — I'll throw out a lot of possibilities, good and bad, and we sort them later. Nothing is committed here." Grilling now is the wrong tool; it kills the ideas you want.

目标：生成大量可支撑价格变动的举措，再共同提炼出更简短的候选列表。本阶段不做评判。明确告知用户：*“我们现在处于头脑风暴模式——我会提出大量可能性，无论好坏，后续再筛选。这里没有任何承诺。”*此时进行审查是错误的，会扼杀有价值的想法。

2a. Generate abundantly

2a. 大量生成想法

Start by doing the work for the user: produce a big first batch of candidate moves, drawn from the menu below and tailored to their specific business. Aim for breadth — and breadth means every category, not just the easy ones. The first batch must include at least one Love candidate if any plausibly fits, because Love is the category a first pass skips by default; do not leave the whole Love category to the sweep in 2b. Group them so the user can scan. Then invite the user's own additions — they know moves you cannot guess.

The menu (a palette to generate from, not a checklist to complete):

Move up a market rung. Reposition to enter a healthier segment — leave the hobbyist far-left of the curve and become the "affordable" option in the next market up. Target customers who optimize for value, not cost.
Change the budget you land in. Reposition the purchase into an easier budget category (a risk/safety line vs. gross margin). Land small under the discretionary threshold, then expand. Escape the add-on ceiling by standing alone.
Reframe the value metric — value created, not cost saved. Price against the metric the customer already uses to judge success (growth, leads, revenue), not against cost savings. The same product pitched as "save money" versus "grow revenue" can carry a several-fold higher price, because growth is worth far more than savings. Find that metric and price against its ceiling.
Build Love drivers (customers who advocate, forgive weaknesses, and want you to charge more). Walk this entire list against the business — do not stop at the obvious one. Love is the most-missed category (the first batch tends to over-index on value and utility), so consider every driver and propose each one that plausibly fits, even loosely; you will pick the one or two to own later: Mission (supporting a change bigger than the product) · Community (a place members belong, learn, and help each other) · Reciprocity (you give before, or more than, you take) · Transparency (openness about the ups and downs, even embarrassing ones) · Design (a joy to use, from a company that obviously cares about craft) · Quality (the relief and pleasure of reliability) · Personality (customers use your brand to express their own) · Culture (supporting an org that treats its people and vendors well) · Ecosystem (members gain more money or prestige together than apart) · Authenticity (the mission is genuine, not performative).
Build Utility drivers (rational reasons the ROI is clear and the choice is safe). Walk this entire list too, and surface each driver that plausibly fits before narrowing to the one or two worth deepening: Unique capability (something no competitor has that they need) · Quality (a seamless, flawless experience) · Simplicity (surprising ease, itself valuable) · Integrations (works with what they already run — and raises switching cost) · Convenience (saves effort worth paying to avoid) · Training (once staff are trained, switching is costly) · System-of-record (critical data lives here; risky to move) · Risk-reduction (lowers the chance something breaks) · Familiarity (a paradigm they already know) · Market-leader (the safe, nobody-gets-blamed choice) · Onboarding (an easy start correlates with higher willingness to pay) · Location (being right where the customer already is). Note some Utility drivers double as mild coercion (integrations, training, system-of-record raise switching cost) — real reasons to stay, but see the coercion check below.
Make the value visible. If customers cannot see the value, no price works. Quantify results in-product ("you saved 47 hours this month"), shorten time-to-value, and build feedback loops that remind customers of their wins.
Create genuine differentiation. Be substantially different at one specific, nameable thing that customers with money agree is worth more — not merely above average. If you cannot name "best at what" in a few words, you do not have it yet, and that is the move.
Repackage / re-tier. Rename a tier to anchor identity (a "Business" tier the buyer self-selects into). Add multi-unit pricing for ideal customers who generate referrals. Use thresholds that feel safe. Split value across more than one honest path to spend.
Check your reliance on coercion. If today's retention rests on contracts, switching costs, or data lock-in rather than Love or Utility, raising the price will expose it — the moment a good alternative appears, coerced customers leave. Ask the honest question: "If a good alternative appeared tomorrow, who leaves immediately?" A move here is to replace a coercion crutch with a real reason to stay.
Pick and align a pricing strategy. If the mixed signals trace back to never having committed to one strategy, the move may be to make that choice and align behind it (a separate method; see "Optional companion skills").

先主动为用户完成部分工作：基于以下菜单并结合用户业务特点，生成首批候选举措。追求广度——覆盖所有类别，而非仅选择容易想到的。首批举措中至少包含一个情感共鸣类候选（如果适用），因为这类举措通常会被忽略；不要将整个情感共鸣类留到2b环节补充。对举措进行分组，方便用户浏览。然后邀请用户补充自己的想法——他们了解你无法预判的举措。

举措菜单（用于生成想法的参考，而非需完成的清单）：

升级市场层级：重新定位，进入更健康的细分市场——远离需求曲线最左侧的爱好者群体，成为上层市场中的“高性价比”选项。瞄准优先考虑价值而非成本的客户。
调整预算类别：重新定位购买行为，使其进入更易获批的预算类别（风险/安全预算vs毛利率预算）。先以小额定价低于自主决策阈值，再逐步拓展。通过独立定位突破附加产品上限。
重新定义价值衡量标准——基于创造的价值而非节约的成本：基于客户已用于判断成功的指标（增长、线索、收入）定价，而非基于成本节约。同一产品以“省钱”和“增收”定位，价格可能相差数倍，因为增长的价值远高于节约的成本。找到该指标，并基于其上限定价。
打造情感共鸣驱动因素（客户愿意主动推荐、包容缺陷、希望你涨价）。逐一对照业务筛选——不要仅停留在明显选项。情感共鸣是最容易被忽略的类别（首批举措往往过度聚焦价值与实用），因此需考虑每个驱动因素，提出所有适用的举措（即使关联性较弱）；后续再选择一两个重点推进：使命（支持超越产品本身的变革）· 社区（用户归属感、学习互助的平台）· 互惠（先给予或多给予）· 透明（公开运营起伏，包括尴尬的失误）· 设计（使用愉悦，体现企业对工艺的重视）· 品质（可靠带来的安心与愉悦）· 个性（客户通过你的品牌表达自我）· 文化（支持善待员工与供应商的企业）· 生态（用户共同获得更多收益或声望）· 真实（使命真诚，而非作秀）。
打造实用价值驱动因素（理性理由，让投资回报率清晰可见，选择更安全）。同样逐一对照业务筛选，先列出所有适用的驱动因素，再缩小范围至一两个值得深化的： 独特能力（竞争对手没有且客户需要的功能）· 品质（无缝、完美的体验）· 简洁（超乎预期的易用性本身就是价值）· 集成（与客户现有系统兼容——提升转换成本）· 便捷（节省客户不愿付出的精力）· 培训（员工接受培训后，转换成本升高）· 记录系统（关键数据存储于此；迁移风险高）· 风险降低（减少故障概率）· 熟悉度（客户已了解的模式）· 市场领导者（安全、无责的选择）· 入门体验（轻松上手与更高支付意愿相关）· 场景适配（出现在客户日常场景中）。注意部分实用价值驱动因素带有轻微强制属性（集成、培训、记录系统提升转换成本）——这是客户留存的真实理由，但需参考下方的强制属性核查。
明确价值呈现：如果客户看不到价值，任何价格都无效。在产品中量化成果（“本月你节省了47小时”），缩短价值实现时间，构建反馈循环提醒客户获得的收益。
打造真实差异化：在客户愿意付费的某一具体、可命名的方面做到显著不同——而非仅仅优于平均水平。如果无法用几句话说明“哪方面最好”，说明你尚未实现差异化，这就是需要采取的举措。
重新包装/分层：为层级重命名以锚定客户身份（例如客户会主动选择的“企业版”）。为能带来转介绍的理想客户推出多单元定价。设置让客户感觉安全的阈值。通过多种真实路径拆分价值，引导客户付费。
核查强制属性依赖：如果当前客户留存依赖合同、转换成本或数据锁定，而非情感共鸣或实用价值，涨价会暴露这一问题——一旦出现更好的替代方案，被强制留存的客户会立即流失。坦诚提问：*“如果明天出现更好的替代方案，哪些客户会立即流失？”*对应的举措是用真实留存理由替代强制属性依赖。
选择并对齐定价策略：如果混合信号源于从未明确统一的定价策略，举措可能是完成策略选择并推动企业对齐（独立方法；参考“可选配套Skill”）。

2b. Sweep the tables — prompt on the drivers you did NOT cover

2b. 全面覆盖——针对未涉及的驱动因素发起提问

The first batch always leans on whatever was most salient — usually value-created and value-visible moves. Whole drivers get silently skipped, Love especially, and the worst case is the wielder never even tried a driver the business is obviously strong on (a product with a big user community that never got a community prompt). So before refining, run one explicit coverage pass over the two enumerated tables above — this is why they are enumerated, not summarized:

Mark what is already covered. Tick each Love and Utility driver the current candidate list already reflects. Those need no prompt.
Turn the uncovered drivers into prompts. For the drivers the list has NOT touched, the drivers are your prompt list. Do not interrogate all ~22 one at a time — that is too slow. Surface the uncovered ones in one compact scan and ask which, if any, are real for this business — pointing at a specific strength you already know about (from Phase 1 or your own research) even if the user never raised it in Phase 2, since the driver the user does not think to mention is exactly the one this sweep exists to catch: "We haven't touched community, delightful design/UI, mission, or personality yet — you clearly have a large user community; is there a lever there? Anything on delight or emotion?"
A quick "no" is a fine answer. The point is to make the user react to each uncovered driver at least once, not to force a move out of it. "No, not us" closes that driver; "actually, yes…" becomes a new
```
[raw]
```
candidate.

Skip a driver only when the list already clearly reflects it, or the user has dismissed it. Never let the whole category slide just because the first batch happened not to mention it. This one prompt is the difference between a menu the user recognizes and one that quietly missed their real strength.

首批举措往往会聚焦最突出的点——通常是基于创造价值和明确价值的举措。部分驱动因素会被忽略，尤其是情感共鸣类；最糟糕的情况是，用户从未尝试过其业务明显具备优势的驱动因素（例如拥有庞大用户社区的产品从未考虑社区举措）。因此在优化前，需针对上述两个枚举列表进行一次明确的覆盖检查——这就是列表被枚举而非总结的原因：

标记已覆盖的驱动因素：勾选当前候选列表已体现的情感共鸣与实用价值驱动因素。这些无需再提问。
针对未覆盖的驱动因素发起提问：对于列表中未涉及的驱动因素，直接将其作为提问内容。不要逐一询问全部约22个——速度太慢。将未覆盖的驱动因素整合为一次简洁的提问，询问用户哪些适用于其业务——可指出你已了解的具体优势（来自第1阶段或自主研究），即使用户在第2阶段未提及，因为用户没想到的驱动因素正是本次检查要捕捉的：“我们尚未涉及社区、愉悦设计/UI、使命或个性——你显然拥有庞大的用户社区；是否有可利用的杠杆？在愉悦感或情感方面有可挖掘的点吗？”
“不适用”是合理答案：本次检查的目的是让用户至少对每个未覆盖的驱动因素做出反应，而非强制生成举措。“不适用，不符合我们的情况”即可结束该驱动因素的讨论；“实际上，是的……”则成为新的
```
[raw]
```
候选举措。

仅当列表已明确体现某驱动因素，或用户已明确拒绝时，才可跳过。不得因首批举措未提及就忽略整个类别。这一次提问是让用户认可举措菜单，避免遗漏其真实优势的关键。

2c. Refine together into a candidate list

2c. 共同优化为候选列表

Go back and forth. For each idea the user reacts to, do one of:

Sharpen the ones they like — make the vague specific ("build Love" → "publish a monthly transparency report on uptime and incidents") — and retag it
```
[sharpened]
```
.
Cut the ones they clearly do not want, or that plainly do not fit — move it to "Considered and cut" as a one-liner.
Add the user's own ideas — tag them
```
[raw]
```
until sharpened.

Edit the list in place in the file as you go. The file holds the current candidate list, not a history of every version. Keep judgment light; the goal here is a good menu, not a final decision. Resist grading yet — that is Phase 3.

Gate to Phase 3: there is a refined candidate list the user recognizes as "the things we might do." Now warn them the mode is about to change.

反复协作。针对用户反馈的每个想法，采取以下操作之一：

优化用户喜欢的想法——将模糊表述具体化（“打造情感共鸣”→“发布月度透明度报告，公开可用性与事件记录”）——并重新标记为
```
[sharpened]
```
。
删除用户明确不想要或明显不符合业务的想法——将其移至“已考虑并淘汰的举措”，仅保留一行记录。
添加用户提出的新想法——标记为
```
[raw]
```
，直至完成优化。

在文件中就地编辑列表。文件记录当前的候选列表，而非所有版本的历史。保持评判宽松；本阶段目标是生成一份优质的菜单，而非最终决策。避免过早评分——这是第3阶段的工作。

进入第3阶段的条件：已生成用户认可的“我们可能采取的举措”候选列表。此时需提醒用户模式即将切换。

Phase 3 — Select the shortlist (adversarial; grill hard)

第3阶段——筛选确定短名单（对抗性；严格审查）

Goal: sort every candidate into one of three outcomes, and lock the primary list. Announce the switch: "Now we change gears. In brainstorm mode I accepted everything; here I push back on every one. Each move ends up in one of three places, and most will not land in the primary one — that's the point."

The three outcomes:

Pay-more driver (PRIMARY — the point of this exercise). Something that would make an existing customer actually pay more — upgrade to a higher tier, or accept a general price increase without leaving. This is the bucket the whole method exists to fill.
Strength to lean into (SECONDARY). A genuinely good move that helps the business — wins new customers, cuts churn, sharpens positioning, strengthens the brand — but that would not, on its own, make an existing customer pay more. These are not failures and must not be discarded; they are saved for the positioning and marketing work downstream.
Cut. Not good enough, or fluff. Gone (to "Considered and cut").

目标：将每个候选举措分为三类结果，并锁定核心列表。明确告知模式切换：“现在我们切换模式。头脑风暴模式下我接受所有想法；现在我会对每个想法提出尖锐质疑。每个举措最终会归入三类中的一类，大部分不会进入核心类别——这正是本阶段的意义。”

三类结果：

涨价驱动因素（核心——本工具的目标）：能让现有客户真正支付更高费用的举措——升级至更高层级，或接受整体涨价而不流失。这是本方法要填充的核心类别。
可强化的优势（次要）：真正有利于业务的举措——获取新客户、降低 churn、优化定位、强化品牌——但本身无法让现有客户支付更高费用。这些不是失败的举措，不得丢弃；需留存用于后续的定位与营销工作。
淘汰：不够优质或无实际价值。移入“已考虑并淘汰的举措”。

The decisive question: would an EXISTING customer pay more?

决定性问题：现有客户会因此支付更高费用吗？

Apply this to every candidate that clears "is it even a good idea," and apply it before you worry about buildability:

Would this make an existing customer choose a higher tier, or accept a price increase without churning? Or does it "only" help win new customers, reduce churn, or improve positioning?

Why the existing-customer bar is the sharp one: an existing customer has already priced you in and settled into a habit. To move them you must give them something genuinely new — a new capability, a new tier with real added value, a new service. Positioning re-describes what they already have; it rarely moves an existing customer, though it wins new ones and reduces churn (real value — wrong bucket). A new customer paying more counts too, but the existing-customer bar is the strong one: clear it and you have cleared everything.

So the honest sort usually runs:

Re-framing, "tell the story better," trust/proof, brand, community-as-goodwill → almost always a Strength (secondary), unless it is attached to something new the customer actually receives.
A new capability, a new tier bundling real added value, a premium service, a genuinely differentiated feature → candidate pay-more driver, to be grilled further.

Do not let a secondary strength be dressed up as a pay-more driver because it is exciting. Worked example: "reposition the business tier on 'we grow your revenue'" is smart and helps churn — but if the only thing behind it is the same product, it is positioning, so it is a strength, not a pay-more driver. If a repositioning is backed by something new the customer receives, then the new thing is the driver and the positioning rides along with it.

对每个通过“是否是好想法”初步筛选的候选举措，先应用这个问题，再考虑可落地性：

这会让现有客户选择更高层级，或接受涨价而不流失吗？还是仅能帮助获取新客户、降低 churn 或优化定位？

为何以现有客户为标准：现有客户已接受你的定价并形成使用习惯。要让他们付费更多，必须提供真正新的价值——新功能、包含真实附加价值的新层级、 premium 服务、真正差异化的特性。重新定位只是重新描述现有价值；几乎无法打动现有客户，尽管能帮助获取新客户并降低 churn（这是真实价值——但属于次要类别）。新客户支付更高费用也有价值，但现有客户标准更严格：通过该标准意味着通过了所有考验。

因此，诚实的分类通常如下：

重新定位、“优化叙事”、信任/证明、品牌、社区作为商誉 → 几乎总是可强化的优势（次要），除非附带客户能真正获得的新价值。
新功能、包含真实附加价值的新层级、 premium 服务、真正差异化的特性 → 候选涨价驱动因素，需进一步严格审查。

不得将次要优势伪装成涨价驱动因素，即使它令人兴奋。示例：“将企业版重新定位为‘我们帮你增收’”是明智之举，有助于降低 churn——但如果背后仍是原有产品，这只是定位优化，属于可强化的优势，而非涨价驱动因素。如果重新定位附带客户能获得的新价值，那么新价值才是驱动因素，定位只是配套。

Grill the pay-more candidates

严格审查涨价驱动候选举措

For everything you have provisionally sorted as a pay-more driver, run the four tests. Be rude to the idea, never to the person.

Does it really make them pay more? Re-confirm the decisive question with evidence, not hope. Which existing customer, in what situation, upgrades or accepts the raise because of this — and why? Strike "could" and "might."
Is it consistent with the strategy and the rest of the business? Does it fit the direction, the chosen market, the positioning — or create a new mixed signal?
Can you actually build/do it? With this team, this quarter, this budget? A move you cannot implement is not a move.
Do customers actually want it? Real evidence they value it, or the founder wishing they did? Where is the proof? Separate wanting the thing from validating the price — evidenced demand for the capability passes this test even when the exact figure is still a hypothesis (the number is handed off anyway); just flag the price as unvalidated.

A pay-more candidate that fails test 1 is not cut by default — check whether it is still a genuine strength and, if so, move it to the secondary bucket rather than the bin.

Test 3 is not all-or-nothing — a driver can pass as a capped pilot. A move is often buildable now in a small, capped form (a pilot with a hard limit on customers) while unproven at scale. That is a legitimate survival, not a cut: record it as "buildable as a pilot; scale unproven" with the specific cap, because the pilot is how the founder learns the real delivery cost and validates the price before promising it to everyone. Do not wave the scale risk through, and do not cut a good driver just because it cannot serve everyone on day one.

对于暂定为涨价驱动因素的每个举措，执行四项测试。针对想法提出尖锐质疑，而非针对个人。

**它真的能让客户支付更高费用吗？**用证据而非希望重新确认决定性问题。具体哪些现有客户在什么情况下会升级或接受涨价——原因是什么？删除“可能”“也许”等模糊表述。
**它符合企业战略与整体业务吗？**它是否符合企业方向、目标市场、定位——还是会产生新的混合信号？
**你真的能落地实施吗？**基于当前团队、本季度、预算情况？无法实施的举措不是有效举措。
**客户真的需要它吗？**有真实证据证明客户重视它，还是创始人一厢情愿？证据在哪里？区分对功能的需求与对价格的验证——客户对功能的明确需求即可通过本测试，即使精确价格仍需验证（价格确定是后续任务）；只需标记价格未验证即可。

未通过测试1的涨价候选举措不一定要淘汰——检查它是否仍是真正的优势，如果是，移至次要类别而非淘汰。

测试3并非全有或全无——驱动因素可作为受限试点通过。很多举措当前可通过小规模、受限的形式落地（例如对客户数量设限的试点），即使大规模落地尚未验证。这是合理的结果，而非淘汰：记录为“可作为试点落地；大规模落地未验证”并明确限制条件，因为试点是创始人了解真实交付成本并在向所有客户承诺前验证价格的方式。不得忽略规模风险，也不得因无法在第一天服务所有客户就淘汰优质驱动因素。

The interrogation

严格质询

If a devil's-advocate skill such as Rude Q&A /

asb-rude-qa

is installed, invoke it with this brief: "Grill each proposed price-raising move. FIRST force the distinction: would this make an EXISTING customer pay more — upgrade a tier or accept a raise — or is it merely good positioning, churn reduction, or an acquisition win? Sort it accordingly. THEN, for the real pay-more drivers, attack whether it truly moves willingness to pay, whether it fits the strategy, whether this team can build it, and whether customers actually want it. Do not let a positioning win pose as a pay-more driver, and do not let the founder be wishy-washy." If it is not installed, run the interrogation yourself with the same posture: sharp, specific, unfair-if-useful questions with a collegial frame. Attack the claim, not the person. Use the Opposite Test — if the opposite of a claim is obviously nonsense, the claim said nothing ("customers want quality" — nobody wants low quality, so it is empty). Do not accept "it depends" or "we'll figure that out later."

Dwell when the answer is fuzzy; move on when it earns it. Stay on one move until it is genuinely defended with a specific, honestly moved to the secondary bucket, or cut. Three rounds on one move is not a reason to wave it through.

It does not matter how many pay-more drivers survive — one strong one is a fine outcome. What matters is that each is real: it would make an existing customer pay more, and it is aligned, buildable, and wanted. The secondary strengths list can be as long as it earns — it is a gift to the positioning work, not clutter.

如果已安装类似Rude Q&A /

asb-rude-qa

的“魔鬼代言人”Skill，可调用它并执行以下指令：“严格审查每个涨价举措。首先明确区分：该举措是否能让现有客户支付更高费用——升级层级或接受涨价，还是仅能优化定位、降低 churn 或提升获客能力？据此分类。然后，针对真正的涨价驱动因素，质疑它是否真能提升支付意愿、是否符合战略、团队是否能落地、客户是否真正需要。不得将定位优化伪装成涨价驱动因素，不得让创始人含糊其辞。”如果未安装该Skill，则自行执行质询，保持同样的姿态：尖锐、具体、为达目的不惜提出苛刻问题，但保持 collegial 的沟通框架。针对主张提出质疑，而非针对个人。使用反向测试——如果主张的对立面明显荒谬，说明该主张毫无意义（“客户需要品质”——没人想要低品质，因此该主张空洞）。不得接受“视情况而定”或“后续再解决”的回答。

答案模糊时深入追问；答案明确时及时推进。针对一个举措持续追问，直至其得到具体辩护、被移至次要类别或被淘汰。对一个举措追问三轮并非推进的理由。

最终留存的涨价驱动因素数量无关紧要——一个强有力的因素就是很好的结果。关键是每个因素都是真实有效的：能让现有客户支付更高费用，且符合战略、可落地、受客户欢迎。次要优势列表可根据实际情况保留——这是后续定位工作的宝贵资源，而非冗余内容。

Lock it in

锁定结果

When the sort is settled, confirm it explicitly with the user — this is the one big state change the skill drives toward. Write the primary drivers into

### Pay-more drivers

and the saved ones into

### Strengths to lean into

, restate the

directional target

(roughly which higher rung), set

locked: true

, advance

phase

done

, and remove the

⚠️ IN PROGRESS

note.

The founder's call on the price itself is theirs, and one valid outcome is to adopt the moves without lifting the number yet. After building the case, a user may reasonably conclude "I'm not going to change the headline price right now, but I'm committing to these one or two drivers — they make me stronger and set up a raise later." That is a real, successful result: the skill's job was to build the case and the moves, and they stand on their own even if the price move waits. Record it plainly (note in

directional target

that the number is held for now while the moves proceed).

Then write the handoff — the work that comes after this skill and is not part of it: choosing the exact new price and tiers, drafting the honest increase letter to customers, and feeding the Strengths to lean into list into the positioning and marketing work. Name those as the next tasks so the user knows where the thread continues.

分类完成后，需与用户明确确认——这是本Skill推动的唯一重大状态变更。将核心驱动因素写入

### 涨价驱动因素

，将次要优势写入

### 可强化的优势

，重申

方向性价格目标

（大致的更高层级），设置

locked: true

，将

phase

改为

done

，并移除

⚠️ 进行中

标记。

创始人拥有最终定价权，一个合理的结果是实施举措但暂不调整价格。在构建涨价依据后，用户可能会合理得出结论：*“我现在不会调整公开定价，但会落实其中一两项驱动因素——这会让我更强，并为后续涨价做好准备。”*这是真实、成功的结果：本Skill的任务是构建涨价依据与举措，即使涨价延迟，这些举措本身也具有价值。需如实记录（在

方向性价格目标

中注明暂不调整价格，先推进举措落地）。

然后撰写后续任务——本Skill之外的工作：确定精确的新价格与层级、撰写给客户的坦诚涨价通知、将可强化的优势列表用于定位与营销工作。明确列出这些任务，让用户知道后续工作方向。

Refusal and edge conditions

拒绝场景与边缘情况

No concrete price to reason about. If the user has only a vague idea with no real product, price, or customers yet, there is nothing to diagnose — help them get concrete first, or note this is premature.
"Just tell me the number." This skill builds the case and the moves, not the exact figure. Do the diagnosis and the moves; hand off the number as the next task rather than guessing it.
The user asks you to argue them out of raising. That is not this skill's job — it drives toward a higher price. What it does allow is the founder deciding, after the case is built, to adopt the moves without lifting the number yet (see "Lock it in"). Do not turn the exercise into a debate over whether to raise at all.
The user wants validation, not scrutiny. In Phase 3 especially, if the user is seeking a rubber stamp for a wishful move, name that and hold the four tests. The value of this phase is the friction.

无具体价格可分析：如果用户仅有模糊想法，无真实产品、价格或客户，无法开展诊断——先帮助用户明确具体信息，或告知用户当前时机不成熟。
“直接告诉我价格数字”：本Skill构建涨价依据与举措，而非确定精确价格。完成诊断与举措梳理后，告知用户确定价格是下一阶段任务，不得猜测。
用户要求说服他们放弃涨价：这不是本Skill的任务——它的核心是推动涨价。允许创始人在构建依据后，选择实施举措但暂不调整价格（参考“锁定结果”）。不得将工作转变为是否涨价的辩论。
用户寻求认可而非审查：尤其是在第3阶段，如果用户希望你对其一厢情愿的举措盖章认可，需明确指出并坚持四项测试。本阶段的价值在于严格审查带来的摩擦。",