asb-willingness-to-pay

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Willingness to Pay — map the desire, commit to what to own

付费意愿（Willingness to Pay）——梳理动机，聚焦深耕方向

Economists use "willingness to pay" to mean the highest price a customer will tolerate. That single number hides the thing that actually matters: why the customer pays. Two companies can have the same willingness to pay and completely different futures — one whose customers advocate for them and cheer when they profit, and one whose customers are praying for a competitor to rescue them.

This skill separates those two companies. It maps the desire behind the price and helps the founder commit to the one or two kinds of desire worth owning. It answers "why do they want this, and which kind of wanting is it?" — not "what should the price be." That distinction is the whole point, and this skill holds it: it never sets or raises a price. It ends at a committed strategy that other work — pricing, positioning, retention, the roadmap — then consumes.

经济学家用「Willingness to Pay」指代客户能接受的最高定价，但这个单一数字掩盖了真正关键的问题：客户为什么付费。两家公司可能拥有相同的付费意愿数据，但未来发展却截然不同——一家的客户会主动拥护，为其盈利欢呼；另一家的客户则盼着竞争对手来「解救」自己。

本工具正是用来区分这两种情况的。它梳理定价背后的客户动机，帮助创始人聚焦于值得深耕的1-2类核心动机。它回答的是「客户为什么想要这个产品，这种需求属于哪类？」——而非「定价应该是多少」。这种区分是核心，且本工具始终坚守这一点：绝不设定或提高定价。它最终输出的是明确的策略，后续的定价、定位、留存、产品路线图等工作都将以此为基础。

The three kinds of desire

三类客户动机

Desire comes in three kinds. All three make a customer pay, so an economist treats them as the same. Strategically they could not be more different. They rank in ascending value:

	What it is	What the customer does	Strategic value
Love	Buying something bigger than the product — a mission, a community, an identity, a company they root for.	Forgives weaknesses, does not comparison-shop, advocates in public, wants you to charge more and thrive.	Highest. A non-linear growth engine competitors cannot copy — advocacy grows you at no added acquisition cost.
Utility	A rational, functional reason. The problem is solved, the ROI is clear, the choice is safe.	Stays for logical reasons, expands usage as they grow, but will make a rational switch to something better or cheaper.	Real, but switchable. Grows existing customers; neutral-to-positive on new ones.
Coercion	Trapped against their will — contracts, switching costs, data lock-in, monopoly.	Pays begrudgingly, warns others away, flees the instant a viable alternative appears.	Lowest. Inorganic, temporary retention. An anti-multiplier long-term.

The fragility test that cuts through all of it: "If a good alternative appeared tomorrow, who leaves immediately?" The answer names your Coercion and separates it from real loyalty. Cable customers did not comparison-shop the day streaming arrived — they fled. That is what fake willingness looks like.

The truth this skill tells, plainly and without preaching: strong companies often run all three at once (Apple earns Love through design, Utility through convenience, and quietly leans on Coercion through lock-in). Examine all three seriously. But Love is the most durable and the best thing to invest in; Coercion is the most fragile and the worst thing to rely on. A couple of honest coercive mechanics are fine. Building your retention on them is a warning sign.

客户动机分为三类。三类动机都会促使客户付费，因此经济学家将其视为同等因素，但从战略角度看，它们有着天壤之别。按价值从低到高排序如下：

	定义	客户行为	战略价值
Love	购买的是产品之外的更大价值——使命、社群、身份认同，或是客户愿意支持的企业。	包容产品缺陷，不做竞品对比，公开拥护品牌，希望你提高定价并发展壮大。	最高。是竞争对手无法复制的非线性增长引擎——客户拥护能零获客成本推动增长。
Utility	理性、功能性的需求。问题得到解决，投资回报率清晰，选择安全可靠。	因逻辑理由留存，随业务增长扩大使用规模，但会理性转向更优或更便宜的替代方案。	真实但可替代。能促进现有客户增长，对新客户影响中性偏正面。
Coercion	被迫付费——受合同、转换成本、数据锁定、垄断等因素限制。	不情愿地付费，劝阻他人购买，一旦出现可行替代方案立即流失。	最低。是非有机、临时性的留存，长期来看是反增长因素。

穿透一切的脆弱性测试：*「如果明天出现优质替代方案，哪些客户会立即流失？」*答案会揭示你的Coercion因素，将其与真实忠诚度区分开。流媒体出现时，有线电视客户没有做竞品对比就直接流失——这就是虚假付费意愿的表现。

本工具会直白地揭示真相：实力强劲的公司往往同时存在三类动机（苹果通过设计获得Love，通过便捷性获得Utility，还悄悄借助数据锁定实现Coercion）。需认真审视三类动机，但Love是最持久、最值得投资的；Coercion是最脆弱、最不应依赖的。少量合理的Coercion机制无可厚非，但将留存建立在Coercion之上则是危险信号。

What this skill produces

本工具的输出成果

One committed willingness-to-pay strategy: the one or two Love drivers you will authentically own, the one or two Utility attributes worth deepening, and a clear-eyed plan for the Coercion you currently mistake for loyalty (what to drop, and the couple of honest mechanics to keep). Recorded in a working file, in the customer's terms, backed by evidence rather than aspiration.

That is the finish line. The order matters: you create the desire first, and only then decide how to capture it — as advocacy, retention, and growth, or as a higher price. This skill does the first half. What you do with a stronger Love driver — raise the price, drive advocacy, cut churn, reprioritize the roadmap — is downstream and out of scope (see "What this skill does NOT do").

一份明确的付费意愿策略：你将真正深耕的1-2个Love驱动因素，值得强化的1-2个Utility属性，以及针对当前被误认为忠诚度的Coercion的清晰规划（要摒弃的部分，以及可保留的少量合理机制）。成果将记录在工作文件中，采用客户视角的表述，以证据而非愿景为支撑。

这就是最终目标。顺序至关重要：先创造客户动机，再决定如何将其转化为拥护、留存和增长，或是更高定价。本工具负责前半部分。至于如何利用更强的Love驱动因素——提高定价、推动客户拥护、降低流失率、重新规划产品路线图——则属于后续工作，不在本工具的范围内（详见「本工具不负责的内容」）。

What this skill does NOT do

本工具不负责的内容

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

It does not set or raise the price. This skill decides which desire to own. Turning a stronger desire into a higher number — the target, the case, the moves — is a separate task. This skill's output is an input to that work, not a substitute for it.
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 the self-consistency half of pricing and its own method. This skill is the desire half. It may note that a strategy choice is missing and point to it, but it does not run it.
It does not define the ideal customer. The map is sharper when you know who your best customer is. If you do not, that is upstream work this depends on (see "Optional companion skills").
It does not rewrite marketing copy. It may conclude "own the community driver," but writing the headline that expresses it is downstream positioning work.

当涉及以下内容时，需明确告知用户并转交其他工具处理，切勿越界：

不设定或提高定价。本工具确定要深耕的动机，将更强的动机转化为更高定价数字——包括目标、依据、行动——是独立任务。本工具的输出是该任务的输入，而非替代方案。
不选择定价策略。在「多换多/多换少/少换少」等定价策略中做选择，并推动公司统一执行，属于定价工作中「自我一致性」的部分，有独立的方法。本工具负责的是「动机」部分，可能会指出缺少策略选择并引导至对应工具，但不会执行该工作。
不定义理想客户。明确理想客户能让动机梳理更精准。如果用户尚未定义，这是本工具的前置工作（详见「可选配套工具」）。
不改写营销文案。本工具可能会得出「深耕社群驱动因素」的结论，但撰写对应的营销标题属于后续定位工作。

Optional companion skills

可选配套工具

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 the commitment (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. If the user cannot say who their best customer is, 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.

Where this output goes next. When the strategy is committed, the file becomes an input to downstream work: a price-raising exercise can use the owned Love and Utility drivers as the ready-made case for a higher number instead of re-deriving them; positioning work turns the owned driver into copy; retention work replaces the dropped Coercion with the real reason to stay. Name whichever of these the user is heading toward; do not do that work here.

在合适的时机向用户推荐这些工具，但绝不强制要求。本工具为每种情况都提供了完整的备选方案，因此可独立运行。

质疑承诺（第三阶段）。如果已安装「Rude Q&A」/
```
asb-rude-qa
```
这类唱反调的工具，可调用它并提供第三阶段的任务说明。如果未安装，则自行执行该质疑工作——第三阶段已明确规定了具体方式。
未定义理想客户。如果用户无法明确最佳客户群体，可使用理想客户定义工具（如
```
asb-carol-*
```
系列工具）或客户访谈工具（如
```
asb-interview-*
```
系列工具）完成定义后再返回。备选方案：基于用户对购买群体及原因的直白描述开展工作，并标记所有基于模糊客户画像得出的结论为低可信度。

输出成果的后续流向。当策略确定后，该文件将成为后续工作的输入：提价工作可直接利用已深耕的Love和Utility驱动因素作为依据，无需重新推导；定位工作将把深耕的驱动因素转化为文案；留存工作将用真实留存理由替代已摒弃的Coercion。告知用户后续对应的工作方向，但不执行该工作。

How you work: posture and pacing

工作方式：姿态与节奏

Be clear, not clever

清晰直白，而非故作聪明

Write to be understood, not admired. These are already slippery ideas — Love and Coercion hide behind soft words like "loyalty" and "stickiness." Say plainly what you mean. State the point instead of gesturing wittily at it.

写作以易懂为目标，而非博人赞赏。这些概念本就难以界定——Love和Coercion常隐藏在「忠诚度」「粘性」等模糊词汇背后。需直白表达你的意思，直接点明要点，而非巧妙暗示。

Facilitate — do not play oracle

扮演引导者，而非预言家

This is the single most important rule in the skill, and the one it most easily breaks. You are a facilitator, not an expert delivering verdicts. Your job is to surface the framework's full menu and draw the answers out of the user — not to study their business, decide the two drivers you think apply, and hand them your conclusion. A run where you named a couple of drivers yourself and never made the user react to the rest has failed, however smart your picks were. When in doubt, show more of the menu and ask more of the user.

这是本工具最重要的规则，也是最容易被打破的规则。你是引导者，而非给出结论的专家。你的职责是呈现框架的全部选项，引导用户得出答案——而非研究用户的业务，自行决定适用的驱动因素并直接给出结论。如果你自行指定了几个驱动因素，却未让用户对其他选项做出反应，那么这次运行就是失败的，无论你的选择多么明智。如有疑问，就展示更多选项并向用户提出更多问题。

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 segment, one proposed change, one decision 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.

The one sanctioned batch is the Phase 1 inventory menu: you present a full palette of desire areas at once, so the user can scan the whole landscape and react to it. Everywhere else — every proposed change, every commitment — is one item per message.

从小处着手——确认输入内容，指出1-2个关键点，然后开始工作。不要一开始就抛出一堆计划或草稿。逐个处理项：每次消息只处理一个部分、一个拟议调整或一个决策。在执行合并、分组或跳过操作前，先提出建议并获得用户同意。解决一个问题后，将其写入文件，再处理下一个。如果用户无法对你的消息做出反应，那你就不是在引导，而是在单向输出。

唯一允许批量处理的是第一阶段的动机清单：一次性呈现所有动机领域，让用户能全面浏览并做出反应。除此之外——所有拟议调整、所有承诺——都要逐个处理。

Match your attitude to the phase, out loud

明确匹配阶段的态度

The three phases ask three different questions. Keep them separate, out loud, and hold the line when the user jumps ahead.

Phase 1 (map what's TRUE TODAY): honest, curious, and above all facilitative. Draft a first read if you like, but then put it in front of the user and pull the rest out of them: "what am I missing? what should be here that isn't? what am I overstating?" You may have to tell the user that what they call loyalty is really lock-in — do it gently, but do not soften it away. Guardrail: Phase 1 is only what is true now. When the user reaches for "we could add a community," stop them kindly: "Hold that — here we're only inventorying what's true today. We get to what we'd change next."
Phase 2 (what we'd do DIFFERENTLY): generous and expansive. Now the question flips forward — of what you have, and what you could authentically build, what would you own, deepen, or drop? Judgment is light; surface possibilities, do not grade them yet. Say so.
Phase 3 (validate): skeptical and strict. Say so: "Now I push back — a change survives only if you can genuinely own it, with evidence, not wish it." Double- check every proposed change is real, then commit.

三个阶段对应三个不同的问题。需明确区分，大声告知用户，并在用户超前时及时拉回。

第一阶段（梳理当前真实状况）：诚实、好奇，且首要任务是引导。可先起草初步版本，但随后要交给用户并引导他们补充：「我遗漏了什么？哪些内容应该包含但未提及？哪些内容被我夸大了？」你可能需要告诉用户，他们所谓的忠诚度其实是锁定——要温和但明确地指出，切勿含糊其辞。边界：第一阶段只记录当前真实状况。当用户提到「我们可以添加社群」时，要及时制止：「先记下来——这里我们只盘点当前已有的内容，后续再讨论要做哪些改变。」
第二阶段（规划差异化行动）：开放且包容。现在问题转向未来——*基于现有情况，以及你真正能打造的内容，你要深耕、强化或摒弃什么？*此时不宜做评判，要挖掘可能性，而非打分。明确告知用户这一点。
第三阶段（验证）：持怀疑态度且严格。明确告知用户：*「现在我要提出反对意见——只有当你真正能深耕该调整，且有证据支撑而非仅凭愿望时，它才能通过验证。」*仔细检查每个拟议调整是否真实可行，然后做出承诺。

Confirming facts about the outside world

核实外部事实

Parts of the map rest on claims about the real world — whether customers actually advocate for you, whether a competitor could copy a mission, what review sites say. 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. If you have no search tools, ask the user to paste the evidence and mark any conclusion that rests on unconfirmed outside facts as low-confidence. The user's own description of who buys and why is ground truth and needs no confirmation — but a claim of Love ("our customers love us") is exactly the kind of thing to check against real advocacy, not accept.

When the user reports advocacy you cannot independently verify, treat it as a claim to confirm, not a settled Love finding: record that area's Love as provisional, name the specific evidence that would confirm it (public reviews, unprompted referrals, defending you against a competitor), and keep it out of the committed strategy until confirmed. Do not agonize over a numeric confidence label — "Love, provisional — confirm with X" is enough.

动机梳理的部分内容基于对现实世界的判断——客户是否真的拥护你，竞争对手是否能复制你的使命，评论网站的评价等。当你做出此类判断时，需通过搜索工具获取最新信息进行核实——不要依赖内部或培训知识，这些知识可能过时且常与具体公司的实际情况不符。如果没有搜索工具，可要求用户提供证据，并标记所有基于未核实外部事实得出的结论为低可信度。用户对购买群体及原因的描述是既定事实，无需核实，但Love的主张（如「我们的客户热爱我们」）则需要通过真实的客户拥护行为来验证，不能直接接受。

当用户报告了你无法独立核实的拥护行为时，要将其视为待确认的主张，而非已确定的Love结论：记录该领域的Love为暂定状态，明确指出能确认它的具体证据（公开评价、主动推荐、在竞品面前为你辩护等），在确认前不将其纳入已确定的策略。无需纠结于数值化的可信度标签，「Love（暂定）——需通过X确认」即可。

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

./WILLINGNESS-TO-PAY.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 lists in the file are edited in place, not appended as history. When you sharpen an item, rewrite that line. Do not keep a running log of every version. Two rules keep a half-finished file legible to a session that resumes cold:

Tag each item's state. In the Phase 1 inventory, mark each area
```
[have]
```
,
```
[partial]
```
,
```
[none]
```
, or
```
[unsure]
```
— the map of what is true today — and
```
[todo]
```
for an area you have not walked yet, so a session that resumes mid-palette can tell "not asked" from
```
[none]
```
. When an area is true for one segment but not another, mark it
```
[partial]
```
and name the split in a note ("
```
[partial]
```
— have for agencies, none for solo freelancers"). In the Phase 2 change list, mark a freshly surfaced idea
```
[raw]
```
and one you have examined with the user
```
[explored]
```
. A resuming session reads these directly instead of inferring.
Keep a short "considered and set aside" note by default, rather than silently deleting. One line each. This exists so a cold resume does not regenerate and re-litigate an item the user already dismissed.

Structure:

markdown

---
phase: 1  # 1=Map what's true today, 2=What we'd do differently, 3=Validate & commit, done
status: "⚠️ IN PROGRESS — Phase 1: inventorying the Love areas with the user"
committed: false   # true ONLY when the WTP strategy is locked
started: <date>
---

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

./WILLINGNESS-TO-PAY.md

。

然后，一旦第一阶段产生第一份真实内容，立即将文件写入磁盘——不要只是说会这么做——并在每个部分确定后立即更新文件，而非在阶段结束后统一更新。文件是记忆载体，而非聊天记录。长时间会话容易遗忘，且上下文会被压缩；只有磁盘上真实、最新的文件能让用户随时离开、恢复或在过程中修正记录。

文件中的列表要就地编辑，而非追加历史版本。当你优化某个项时，直接改写该行。不要保留每个版本的运行日志。两条规则确保未完成的文件在恢复会话时仍清晰可读：

标记每个项的状态。在第一阶段的清单中，标记每个领域为
```
[have]
```
（已具备）、
```
[partial]
```
（部分具备）、
```
[none]
```
（完全不具备）、
```
[unsure]
```
（不确定）或
```
[todo]
```
（待梳理）——这是当前真实状况的梳理结果，让恢复的会话能区分「未询问」和
```
[none]
```
。当某个领域仅适用于部分客户群体时，标记为
```
[partial]
```
并在备注中说明（如「
```
[partial]
```
——代理客户已具备，独立自由职业者未具备」）。在第二阶段的调整列表中，将新提出的想法标记为
```
[raw]
```
（原始想法），与用户讨论过的标记为
```
[explored]
```
（已探讨）。恢复的会话可直接读取这些标记，无需推断。
默认保留简短的「已考虑并搁置」备注，而非默默删除。每个想法只需一行。这样可避免恢复会话时重新生成并争论用户已否决的项。

文件结构：

markdown

---
phase: 1  # 1=梳理当前真实状况, 2=规划差异化行动, 3=验证并承诺, done=完成
status: "⚠️ 进行中 — 第一阶段：与用户梳理Love领域"
committed: false   # 仅当付费意愿策略锁定时设为true
started: <日期>
---

Willingness to Pay — <company / product>

付费意愿（Willingness to Pay）—— <公司/产品名称>

Current reality (Phase 1)

当前现状（第一阶段）

Who pays, and the segments

付费群体及细分

Why they pay now — first read

当前付费原因——初步判断

The desire map — what's TRUE TODAY (Phase 1)

动机梳理——当前真实状况（第一阶段）

Love — which areas we have

Love——已具备的领域

Utility — which areas we have

Utility——已具备的领域

Coercion — what is actually operating

Coercion——实际存在的因素

Parked for Phase 2

留待第二阶段探讨

The fragility test — who leaves the moment a good alternative appears

脆弱性测试——一旦出现优质替代方案，哪些客户会立即流失

First read — where our willingness to pay actually comes from today

初步结论——当前付费意愿的实际来源

What we'd do differently (Phase 2) ← a LIVING list, edited in place

差异化行动规划（第二阶段） ← 动态列表，就地编辑

Love — to own or build

Love——要深耕或打造的领域

Utility — to deepen or build

Utility——要强化或打造的属性

Coercion — reliance to drop & replace; honest mechanics to keep

Coercion——要摒弃的依赖及替代方案；可保留的合理机制

Considered and set aside

已考虑并搁置的想法

Validated & committed strategy (Phase 3)

已验证并确定的策略（第三阶段）

Love driver(s) we will own

我们将深耕的Love驱动因素

Utility attribute(s) we will deepen

我们将强化的Utility属性

Coercion — what we drop, what we keep honestly

Coercion——要摒弃的部分，以及合理保留的机制

Handoff — what consumes this next (not in this 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. **The status line must also record the posture** (e.g. "Phase 1 — inventory,
walking Utility areas with the user" or "Phase 2 — judgment LIGHT, awaiting reaction
to a community idea"), because nothing else on disk tells a cold-resuming session
whether it is inventorying, exploring, or ready to grill — opening in Phase 3 mode
over an ungraded list would break the skill's core rule. `committed` stays `false`
until the Phase 3 strategy is locked; 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 map or a committed strategy already
recorded. When you resume, re-state the current posture aloud (inventory in Phase 1,
light judgment in Phase 2) before continuing, so a cold resume does not slide into
grading.


`status`行要准确记录会话中断的位置——明确指出**具体的未完成线程或下一个任务**，而非仅标注阶段——这样新的会话仅通过磁盘文件即可恢复。**status行还必须记录当前姿态**（如「第一阶段——梳理中，与用户探讨Utility领域」或「第二阶段——宽松评判，等待用户对社群想法的反馈」），因为磁盘上的其他内容无法告知恢复的会话当前处于梳理、探讨还是质疑阶段——如果在第三阶段模式下打开未打分的列表，会违反本工具的核心规则。`committed`在第三阶段策略锁定前保持`false`；这是本工具推动的唯一重大状态变化的机器可读记录。只有当练习完成后，才移除`⚠️ 进行中`备注。

如果文件已存在，读取文件，告知用户当前所处阶段，并从该阶段继续——切勿在已有梳理结果或确定策略的情况下重新从第一阶段开始。恢复会话时，要先大声说明当前姿态（第一阶段梳理、第二阶段宽松评判），再继续，避免恢复时直接进入质疑模式。

Phase 1 — Map what's true today

第一阶段——梳理当前真实状况

Goal: an honest, user-generated map of who pays today and which desires actually operate — walked area by area across the full palette, not guessed at by you. This is inventory, not strategy: only what is true now. The most common way this skill fails is the wielder quietly deciding the answers itself and naming a driver or two; your job is the opposite — surface the whole menu and pull the truth out of the user.

目标：由用户生成的、诚实的当前付费群体及实际动机的梳理结果——逐一梳理所有动机领域，而非由你猜测。这是盘点，而非策略：仅记录当前真实状况。本工具最常见的失败方式是操作者悄悄自行决定答案并指定几个驱动因素；你的职责恰恰相反——呈现所有选项，引导用户说出真相。

1a. Collect the current reality

1a. 收集当前现状

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

Who pays. The distinct segments who buy — and, if they differ, how each uses the product. 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 map (see "Optional companion skills").
Why they pay — the user's first guess. In their own words, why does each segment buy and stay? Do not correct it yet.

Reflect back what you found and write it into the file. Do not prescribe drivers to build yet — finish the picture first.

你需要两个信息。接受用户提供的任何形式——批量粘贴、文件、定价页及首页链接，或通过提问获取。如果用户提供URL或文件，要读取内容；基于用户的真实表述开展工作，而非转述。

付费群体：购买产品的不同细分群体，以及（如果存在差异）每个群体的使用方式。哪些是盈利群体。如果用户已有理想客户定义，要纳入其中；如果没有，需指出模糊的客户画像会削弱梳理结果的可信度（详见「可选配套工具」）。
当前付费原因——用户的初步判断：用用户自己的话描述每个细分群体购买并留存的原因。暂不纠正。

反馈你收集到的信息并写入文件。此时不要提出要打造的驱动因素——先完成现状梳理。

1b. Inventory the desire, area by area, WITH the user

1b. 与用户逐一梳理动机领域

This is the heart of Phase 1, and the step the skill exists to force. Walk the full palette of each kind of desire and, for every area, get the user to say whether it is true of them today: have it, partly, don't, or not sure. Do the three kinds in order — Love first (it is the most valuable and the most overlooked), then Utility, then the Coercion actually operating.

How to run it so it facilitates instead of lectures:

Show the whole menu, grouped and scannable — do not pre-filter it. Present all the areas of Love at once (then Utility) so the user can see the full landscape and spot what is missing. Handing the user only the two or three you guessed is the exact failure to avoid; the value is in making them react to areas they would never have raised.
Draft a first read if you can, then hand it back for correction. It is fine to pre-mark a few from what you already know ("from your site, Design and Community look like have"). But immediately put it to the user: "That's my first pass — what am I missing? What should be on here that isn't? What am I overstating that really isn't true?" The user's edits are the point, not your draft.
Mark each area
```
[have]
```
/
```
[partial]
```
/
```
[none]
```
/
```
[unsure]
```
and write it to the file as you go. A quick "no, not us" is a complete answer; move on. Dwell only where the user says have/partial — get the specific evidence ("you said you have Community — where does it live, who's in it, what do they do there?"), because a claimed area with nothing behind it is not a have.
Hold the line to today. If the user says "we don't have a mission but we could," welcome it and park it: "Good — that's a Phase 2 move. Right now I'm only marking what's already true." Record it right away as a
```
[raw]
```
line in the Phase 2 change list, tagged "(parked in P1)", so it is waiting there when the question flips — then keep inventorying.

The palette of Love areas — read all of these to the user:

Mission — supporting a change bigger than the product; a movement customers want to see win.
Community — a place members belong, learn, teach, and help each other.
Reciprocity — you give before you take, or give more than you take.
Transparency — openness about the ups and downs, even the embarrassing ones.
Design — a pleasure to use, made by a team that visibly sweats the craft.
Quality — the relief and pleasure of reliability.
Personality — customers use your brand to express their own identity.
Culture — supporting an organization that treats its people and vendors well.
Ecosystem — belonging pays: members earn more money or standing inside the group than outside it.
Authenticity — the genuineness is itself the draw, not a performed mission.

The palette of Utility areas — read all of these to the user:

Unique — a capability no competitor has that customers 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 — you are already present where the customer works.
Cheap — a low price is its own reason to buy.

(Quality appears in both palettes on purpose — as Love it is the relief of reliability that earns devotion; as Utility it is a flawless experience the buyer rationally pays for. Mark it in each place; it is not a duplicate to delete.)

Then the Coercion actually operating — not a wish list, what is genuinely holding customers against their will today. Its forms: contractual lock-in, data you will not let them export, switching costs, an effective monopoly, price-fixing, bundle- stuffing, raising the price only once they are at scale, corporate policy, legal fiat. Some Utility areas double as mild Coercion — integrations, training, and system-of-record all raise switching cost — so where the user marked those

[have]

, ask honestly whether they are a real reason to stay, a trap, or both.

这是第一阶段的核心，也是本工具存在的意义。逐一梳理每类动机的所有领域，对于每个领域，让用户说明当前是否符合：已具备、部分具备、完全不具备或不确定。按顺序梳理三类动机——先Love（价值最高且最易被忽视），再Utility，最后是实际存在的Coercion。

如何以引导而非说教的方式开展：

展示完整的、分组的可扫描列表——不要预先过滤。一次性呈现所有Love领域（然后是Utility），让用户能看到全貌并发现遗漏的内容。只向用户展示你猜测的两三个领域是绝对要避免的错误；价值在于让用户对他们从未想到的领域做出反应。
可先起草初步版本，再交给用户修正。可根据已知信息预先标记几个领域（如「从你的网站来看，Design和Community似乎属于已具备」）。但要立即交给用户：*「这是我的初步版本——我遗漏了什么？哪些内容应该包含但未提及？哪些内容被我夸大了？」*用户的修改才是重点，而非你的草稿。
标记每个领域为
```
[have]
```
/
```
[partial]
```
/
```
[none]
```
/
```
[unsure]
```
，并在梳理过程中写入文件。快速回答「不，我们没有」即可；继续下一个领域。仅在用户回答已具备/部分具备时停留——获取具体证据（如「你说已具备Community——它在哪里，成员有哪些，他们在里面做什么？」），因为没有证据支撑的声称并非真正的已具备。
严格聚焦于当前状况。如果用户说「我们没有使命，但我们可以打造」，要表示欢迎并留待后续：*「很好——这是第二阶段的任务。现在我们只标记已有的内容。」*立即将其记录在第二阶段调整列表中，标记为
```
[raw]
```
并标注「（第一阶段留存）」，这样当问题转向未来时它已准备就绪——然后继续梳理。

Love领域列表——向用户完整读出：

Mission（使命）——支持超越产品的变革；客户希望看到成功的运动。
Community（社群）——成员归属感强，相互学习、传授知识、提供帮助的场所。
Reciprocity（互惠）——先予后取，或多予少取。
Transparency（透明度）——公开业务的起伏，甚至是尴尬的情况。
Design（设计）——使用体验愉悦，团队明显用心打磨。
Quality（品质）——可靠带来的安心与愉悦。
Personality（品牌个性）——客户通过你的品牌表达自身身份。
Culture（企业文化）——支持善待员工和供应商的组织。
Ecosystem（生态系统）——加入社群能获得更多收益或地位。
Authenticity（真实性）——真诚本身就是吸引力，而非刻意营造的使命。

Utility领域列表——向用户完整读出：

Unique（独特性）——竞争对手没有且客户需要的功能。
Quality（品质）——无缝、无瑕疵的体验。
Simplicity（简洁性）——出人意料的易用性，本身具有价值。
Integrations（集成性）——与客户已使用的工具兼容（同时提高转换成本）。
Convenience（便捷性）——节省值得付费避免的精力。
Training（培训）——员工接受培训后，转换成本升高。
System-of-record（记录系统）——关键数据存储于此，迁移风险高。
Risk-reduction（风险降低）——减少故障发生的概率。
Familiarity（熟悉度）——客户已了解的范式。
Market-leader（市场领导者）——安全、不会出错的选择。
Onboarding（入门体验）——轻松上手与更高付费意愿相关。
Location（地域优势）——你已布局在客户的工作场景中。
Cheap（低价）——低价本身就是购买理由。

（Quality同时出现在两个列表中是有意为之——在Love中，它是赢得客户忠诚的「可靠带来的安心」；在Utility中，它是客户理性付费的「无瑕疵体验」。要在两个位置分别标记，不要视为重复内容删除。）

然后是实际存在的Coercion——并非愿望清单，而是当前真正迫使客户付费的因素。形式包括：合同锁定、不允许导出的数据、转换成本、有效垄断、价格操纵、捆绑销售、客户规模扩大后提价、企业政策、法律强制。部分Utility领域同时属于轻度Coercion——集成性、培训、记录系统都会提高转换成本，因此当用户标记这些领域为

[have]

时，要坦诚询问它们是真实的留存理由、陷阱，还是两者兼具。

1c. Run the fragility test

1c. 执行脆弱性测试

With the inventory down, run the single most clarifying question in the method, on the whole base: "If a good alternative appeared tomorrow, who leaves immediately?" Whoever leaves was held by Coercion, whatever you were calling it. Name them. Do not let "they're locked into a contract" pass as "they're loyal." This is what separates a real

[have]

in Love from Utility-plus-lock-in wearing its costume.

Name where your willingness to pay actually comes from today. The common, uncomfortable finding: "You thought you had loyal customers; you have a useful product plus switching costs, and the moment Linear-for-your-market ships, a third of them are gone." State it plainly and write it to the file. That honest baseline is exactly what Phase 2 works to change.

Gate to Phase 2: the full palette is inventoried with the user (every area marked, the live ones evidenced), the fragility test is answered, and the file names where today's willingness to pay really comes from. The question now flips forward: what would we do differently?

完成盘点后，对整个客户群体提出最具启发性的问题：*「如果明天出现优质替代方案，哪些客户会立即流失？」*立即流失的客户就是被Coercion留住的，无论你之前如何称呼这种留存。明确指出这类客户。不要让「他们受合同约束」被当作「他们忠诚」。这正是区分真实的Love

[have]

与伪装成忠诚的Utility+锁定的关键。

明确当前付费意愿的实际来源。常见且令人不安的结论：*「你以为拥有忠诚客户；但实际上你只有实用的产品加上转换成本，一旦针对你所在市场的Linear产品推出，三分之一的客户会立即流失。」*直白地陈述并写入文件。这种诚实的基线正是第二阶段要改变的内容。

进入第二阶段的条件：与用户完成所有领域的盘点（每个领域都已标记，已具备的领域有证据支撑），完成脆弱性测试，文件明确指出当前付费意愿的实际来源。现在问题转向未来：我们要做出哪些改变？

Phase 2 — What we'd do differently

第二阶段——规划差异化行动

Goal: a generous set of changes — which desire to own, deepen, or build, and which Coercion to drop — working from the Phase 1 inventory. Now the question flips from "what is true" to "what would we do differently," so judgment is light. Announce it: "We inventoried what's true today. Now we go forward: given that, what would we build, deepen, or drop? I'll surface possibilities; nothing is committed here." Do not grade yet; grading now kills the idea you want.

Two sources feed the change list, and you should draw from both:

Deepen a
[have]
or
[partial]
. The strongest candidates are usually areas the inventory already marked true — an existing Community you could invest in, a Utility you could sharpen. These are ownable because they already exist.
Build a
[none]
you could authentically earn. A missing area is fair game if the business could genuinely earn it — genuineness is the gate, because an inauthentic mission or community invites backlash (as Skechers found when it copied TOMS). This is where the "we could add X" notes you parked in Phase 1 come back in.

Go one idea at a time: propose, let the user react, tag

[raw]

when freshly surfaced and

[explored]

once examined together. Point at specific inventory findings ("you marked Community partial and it has real people in it — that's the obvious one to own"). You do not need to re-read the full palette — Phase 1 already walked it; here you work from what it surfaced plus the authentic could-builds.

Frame every change by the value the customer measures, not the cost it removes. This is where the biggest gains hide. The same capability described as "save money" versus "grow your revenue / leads / pipeline" can carry several times the willingness to pay, because customers value growth far above savings. So phrase a driver in the customer's own success metric — "generates $40,000 in additional leads a month," not "cuts your cost per lead." Do this as part of how you describe the change; it is a framing discipline, not a separate step. (Some Love drivers benefit too — "join a community that makes you more money" beats "join our forum.")

One caution on Cheap. If the inventory marked Cheap a real

[have]

, do not turn "deepen Cheap" into a change here. Leaning into low price as the reason to buy is a pricing-strategy choice (the "Less for Less" path), which belongs to the strategy method, not this skill. Note it and hand it off; do not turn this exercise into a race to the bottom.

The Coercion you rely on is a change target, not an asset. For each place the fragility test showed retention resting on a contract, switching costs, trapped data, or a lack of alternatives, the forward move is to build a Love or Utility reason to stay in its place (the T-Mobile "Un-carrier" reversal: they dropped the contracts and the termination fees and won the market by earning loyalty instead of enforcing it). Know the stakes even in cold profit terms: of two identical companies, one held by Love and one by Coercion, the Love company is the better investment — its customers grow it for free while the coerced company's customers lobby to leave. So the anti-Coercion case does not rest on ethics; it is the smarter bet. Record two things: the reliance you'll aim to drop and replace, and the couple of honest mechanics you'll keep (a positive bundle discount, an annual commitment the customer chooses for a real benefit — legitimate, entered into with eyes open; do not moralize those away).

Gate to Phase 3: there is a set of proposed changes the user recognizes as "what we'd do differently," plus the Coercion drop/keep list. Now warn them the mode is about to change.

目标：基于第一阶段的盘点结果，生成一系列调整方案——要深耕、强化或打造的动机，以及要摒弃的Coercion。现在问题从「现状是什么」转向「我们要做出哪些改变」，因此评判标准宽松。告知用户：*「我们已梳理完当前现状。现在展望未来：基于此，我们要打造、强化或摒弃什么？我会提出一些可能性，目前无需做出承诺。」*此时不要打分，过早打分会扼杀有价值的想法。

调整列表有两个来源，你需要兼顾两者：

强化
[have]
或
[partial]
的领域。最有力的候选者通常是盘点中已标记为真实的领域——已有的社群可进一步投资，已有的Utility可进一步优化。这些领域更易深耕，因为它们已存在。
打造可真正实现的
[none]
领域。缺失的领域也可考虑，但前提是企业能真正实现——真实性是关键，因为虚假的使命或社群会引发反弹（正如斯凯奇模仿TOMS时的遭遇）。这就是第一阶段留存的「我们可以添加X」想法发挥作用的地方。

逐个提出想法：提出建议，让用户做出反应，新提出的想法标记为

[raw]

，与用户讨论过的标记为

[explored]

。要指向盘点中的具体发现（如「你标记Community为部分具备，且已有真实成员——这显然是值得深耕的领域」）。无需重新读取完整列表——第一阶段已完成梳理，此处基于梳理结果及可真正实现的想法开展工作。

以客户衡量的价值而非节约的成本来描述每个调整。这是最大收益的隐藏之处。同一功能用「节省资金」和「增加收入/线索/销售管道」描述，付费意愿可能相差数倍，因为客户对增长的重视远高于成本节约。因此要用客户自身的成功指标来描述驱动因素——如「每月产生4万美元的额外线索」，而非「降低线索获取成本」。这是描述调整的一部分，是一种框架规范，而非独立步骤。（部分Love驱动因素也可受益——如「加入能让你赚更多钱的社群」优于「加入我们的论坛」。）

关于Cheap的注意事项。如果盘点中标记Cheap为真实的

[have]

，不要将「强化Cheap」作为此处的调整方案。将低价作为购买理由属于定价策略选择（「少换少」路径），归属于策略工具，而非本工具。要指出这一点并转交处理，不要让本练习演变成价格战。

你依赖的Coercion是调整目标，而非资产。对于脆弱性测试显示留存依赖合同、转换成本、数据锁定或缺乏替代方案的每个领域，未来的行动是用Love或Utility留存理由替代它（如T-Mobile的「非运营商」转型：他们取消了合同和终止费，通过赢得忠诚而非强制留存赢得了市场）。即使从冰冷的利润角度看，也要了解其风险：两家相同的公司，一家依靠Love留存，一家依靠Coercion留存，前者是更好的投资——其客户会免费推动增长，而后者的客户则会设法离开。因此反对Coercion的理由并非基于道德，而是更明智的选择。记录两件事：要摒弃并替代的Coercion依赖，以及可保留的少量合理机制（如正向捆绑折扣、客户为获得真实利益而选择的年度承诺——合法且自愿，无需道德批判）。

进入第三阶段的条件：有一套用户认可的「我们要做出的改变」方案，以及Coercion的摒弃/保留列表。现在要告知用户模式即将改变。

Phase 3 — Validate and commit

第三阶段——验证并承诺

Goal: double-check every change proposed in Phase 2 is real, narrow to a committed strategy — the one or two Love drivers you will own, the one or two Utility attributes you will deepen, and the Coercion plan — and lock it in. Announce the switch: "Now we change gears. In Phase 2 I accepted every idea; here I push back on each one, and most will not make the final cut — that's the point. A strategy is what you say no to."

目标：仔细检查第二阶段提出的每个调整是否真实可行，缩小范围至明确的策略——你将深耕的1-2个Love驱动因素，要强化的1-2个Utility属性，以及Coercion规划——并锁定策略。明确告知模式切换：「现在我们切换模式。第二阶段我接受所有想法；此处我会对每个想法提出反对意见，大多数想法不会进入最终方案——这就是关键。策略就是学会说不。」

The bar: can you genuinely OWN it?

标准：你能否真正深耕？

Willingness to pay is not built by claiming a driver — it is built by being it, credibly and consistently. So the test for a surviving change is ownership, not appeal. Apply it to every Love and Utility candidate:

Can you own this — for real, better than the alternatives, consistent with what you already do — such that a customer would feel it? Or are you wishing it were true?

The four questions behind that bar:

Is it already true, or credibly buildable? Where is the evidence you have this driver, or a concrete path to it? Strike "we could seem more…". A Love driver especially must be genuine; a performed one backfires.
Is it self-consistent with the rest of you? Does the driver fit your product, your price, your other signals — or does it fight them? (A "premium design" Love claim on a product that ships buggy is not self-consistent; customers feel the contradiction and none of it lands.)
Can few competitors copy it? Love drivers resist copying because inauthentic imitation invites backlash; a Utility driver may be more easily matched. The harder to copy, the more durable the willingness to pay.
Is it worth concentrating on? You are choosing one or two to own, not ten to dabble in. A driver you will pursue at only half-effort is not a commitment.

Concentrate. The finish line is one or two Love drivers and one or two Utility attributes — not a long even list. Owning one driver to an extreme beats being slightly-above-average at six. Force the choice; do not let the user keep everything.

付费意愿不是靠声称拥有某个驱动因素就能建立的——而是靠持续、极致地践行该驱动因素。因此调整能否通过验证的标准是能否深耕，而非吸引力。将该标准应用于每个Love和Utility候选者：

你能否真正深耕这一点——真实可信，优于竞争对手，与你已有的行动一致——让客户能切实感受到？还是你只是希望它成真？

该标准背后的四个问题：

是否已真实存在，或可切实打造？ 你有哪些证据证明拥有该驱动因素，或有具体的实现路径？剔除「我们可以看起来更……」这类想法。Love驱动因素尤其要真实可信，虚假的驱动因素会适得其反。
是否与你的其他方面一致？ 该驱动因素是否符合你的产品、定价及其他信号——还是与之冲突？（如在存在大量bug的产品上声称「高端设计」的Love驱动因素就不一致；客户会感受到矛盾，无法产生共鸣。）
竞争对手能否轻易复制？ Love驱动因素难以复制，因为虚假模仿会引发反弹；Utility驱动因素则更易被匹配。越难复制，付费意愿就越持久。
是否值得聚焦深耕？ 你要选择1-2个领域深耕，而非10个领域浅尝辄止。仅投入一半精力的驱动因素并非真正的承诺。

聚焦深耕。最终目标是1-2个Love驱动因素和1-2个Utility属性——而非冗长的列表。极致深耕一个驱动因素优于在六个领域略高于平均水平。要迫使用户做出选择，不要让他们保留所有想法。

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 willingness-to-pay change. For each, attack whether the company genuinely OWNS it or is merely wishing: is there evidence it is already true or a credible path to it; is it self-consistent with the product, price, and other signals; can competitors copy it; and is it worth concentrating on versus the alternatives? Be especially hard on Love claims — an assumed 'our customers love us' with no advocacy behind it is the classic self-flattering error. Force the company down to one or two Love drivers and one or two Utility attributes. Do not let them keep everything." 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 obvious 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 change until it is genuinely defended, honestly cut, or moved to "considered and set aside." Three rounds on one driver is not a reason to wave it through.

如果已安装「Rude Q&A」/

asb-rude-qa

这类唱反调的工具，可调用它并提供以下任务说明：*「质疑每个拟议的付费意愿调整。针对每个调整，质疑公司是否真正能深耕，还是只是一厢情愿：是否有证据证明它已真实存在或有切实的实现路径；是否与产品、定价及其他信号一致；竞争对手能否复制；与其他选项相比是否值得聚焦深耕？尤其要严格审查Love主张——没有拥护行为支撑的「我们的客户热爱我们」是典型的自我美化错误。迫使公司缩小至1-2个Love驱动因素和1-2个Utility属性。不要让他们保留所有想法。」*如果未安装该工具，则自行执行质疑工作，保持相同姿态：尖锐、具体、有用的问题，同时保持 collegial 的框架。质疑主张，而非个人。使用反向测试——如果主张的对立面显然是无稽之谈，那么该主张毫无意义（如「客户想要品质」——没人想要低品质，因此该主张空洞无物）。不要接受「视情况而定」或「我们以后再解决」这类回答。

在答案模糊时停留，在答案充分时继续。针对一个调整，直到它真正得到辩护、被诚实剔除，或被移至「已考虑并搁置」。针对一个驱动因素进行三轮质疑并非放行的理由。

Settle the Coercion plan

确定Coercion规划

From the Phase 2 findings, commit to: which coercion reliance you will drop (and the Love/Utility reason to stay you will build in its place), and which honest mechanics you will keep. Be concrete. "Stop holding data hostage; ship an export and win the stay on Utility instead" is a commitment; "be less coercive" is not.

基于第二阶段的发现，承诺：要摒弃的Coercion依赖（以及将用来替代它的Love/Utility留存理由），以及要保留的合理机制。要具体明确。「停止扣押数据；推出导出功能，转而依靠Utility留住客户」是明确的承诺；「减少强制手段」则不是。

Lock it in

锁定策略

When the strategy is settled, confirm it explicitly with the user — this is the one big state change the skill drives toward. Write the owned Love driver(s), the Utility attribute(s) to deepen, and the Coercion plan into the "Validated & committed strategy" section, set

committed: true

, advance

phase

done

, and remove the

⚠️ IN PROGRESS

note. It does not matter how many drivers survive — one strong, genuinely owned Love driver is an excellent result. What matters is that each is real, ownable, self-consistent, and worth concentrating on.

Then write the handoff — the work that comes after this skill and is not part of it. Name whichever the user is heading toward: turning the owned drivers into the case for a higher price (a separate price-raising exercise), turning a driver into marketing copy (positioning), or replacing dropped Coercion with the real reason to stay (retention and roadmap). This file is the input to that work; it is not that work.

当策略确定后，与用户明确确认——这是本工具推动的唯一重大状态变化。将已深耕的Love驱动因素、要强化的Utility属性及Coercion规划写入「已验证并确定的策略」部分，设置

committed: true

，将

phase

改为

done

，并移除

⚠️ 进行中

备注。最终保留的驱动因素数量无关紧要——一个强大、真正可深耕的Love驱动因素就是极佳的结果。重要的是每个驱动因素都真实可信、可深耕、一致且值得聚焦。

然后写入交接内容——本工具之后的工作，不属于本工具的范围。明确用户后续的工作方向：将已深耕的驱动因素转化为提价依据（独立的提价练习），转化为营销文案（定位工作），或用真实留存理由替代已摒弃的Coercion（留存及路线图工作）。该文件是这些工作的输入，而非工作本身。

Refusal and edge conditions

拒绝场景与边缘情况

No real customers yet. With no paying base to audit, the Phase 1 inventory is thin — you will have few real
```
[have]
```
s. Say so, keep it light, and let the weight fall on Phase 2, where the question becomes which desire to build toward, while flagging that every read is a hypothesis until real customers confirm it. Two adjustments follow. The fragility test has no base to run against — do not force it; ask it as a thought experiment about the customers you intend to win, and mark the answer hypothetical. And the Phase 3 ownership bar softens from "where is the evidence" to "is there a credible path," since you are committing which desire to build. Say so plainly.
"Just tell me what to charge." This skill does not set or raise the price. Map the desire and commit the strategy; hand the pricing decision off as the next task rather than guessing a number.
"Our customers love us" with nothing behind it. This is the most common self-flattering error and the reason the fragility test exists. Do not accept a claim of Love without advocacy evidence; if it is really Utility propped up by switching costs, say so — gently, but say it.
The user wants validation, not scrutiny. In Phase 3 especially, if the user is seeking a rubber stamp for a driver they cannot actually own, name that and hold the bar. The value of this phase is the friction.

尚无真实客户。没有付费客户群体可供审计，第一阶段的盘点内容会很单薄——几乎没有真实的
```
[have]
```
。要明确告知用户，保持宽松态度，重点转向第二阶段，即要打造的动机，同时标记所有结论为假设，需真实客户确认。需做出两项调整：脆弱性测试没有客户群体可测试——不要强制执行，可将其作为针对目标客户的思想实验，并标记答案为假设。第三阶段的深耕标准从「证据在哪里」放宽至「是否有切实的实现路径」，因为你要承诺的是要打造的动机。要明确告知用户这一点。
「直接告诉我定价多少」。本工具不设定或提高定价。梳理动机并确定策略，将定价决策作为后续任务转交，而非猜测数字。
「我们的客户热爱我们」但无支撑证据。这是最常见的自我美化错误，也是脆弱性测试存在的原因。不要接受无拥护行为支撑的Love主张；如果实际上是Utility加上转换成本，要温和但明确地指出。
用户想要验证而非审查。尤其在第三阶段，如果用户只是想为自己无法真正深耕的驱动因素寻求认可，要明确指出并坚守标准。本阶段的价值在于这种摩擦。