stress-test
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/em:stress-test — Business Assumption Stress Testing
/em:stress-test — 商业假设压力测试
Command:
/em:stress-test <assumption>Take any business assumption and break it before the market does. Revenue projections. Market size. Competitive moat. Hiring velocity. Customer retention.
命令：
/em:stress-test <assumption>将任何商业假设在市场验证之前先进行“击穿”测试。包括收入预测、市场规模、竞争护城河、招聘速度、客户留存率等。
Why Most Assumptions Are Wrong
为什么大多数假设都是错误的
Founders are optimists by nature. That's a feature — you need optimism to start something from nothing. But it becomes a liability when assumptions in business models get inflated by the same optimism that got you started.
The most dangerous assumptions are the ones everyone agrees on.
When the whole team believes the $50M market is real, when every investor call goes well so you assume the round will close, when your model shows $2M ARR by December and nobody questions it — that's when you're most exposed.
Stress testing isn't pessimism. It's calibration.
创始人本质上是乐观主义者。这是优势——你需要乐观才能从零开始创立事业。但当商业模式中的假设被这种启动事业的乐观情绪放大时，它就会变成一种劣势。
最危险的假设是所有人都认同的假设。
当整个团队都相信5000万美元的市场是真实存在的，当每次投资者沟通都很顺利所以你认为融资会成功，当你的模型显示到12月能达到200万美元ARR却没人提出质疑——这时你面临的风险最大。
压力测试不是悲观主义，而是校准。
The Stress-Test Methodology
压力测试方法论
Step 1: Isolate the Assumption
步骤1：分离假设
State it explicitly. Not "our market is large" but "the total addressable market for B2B spend management software in German SMEs is €2.3B."
The more specific the assumption, the more testable it is. Vague assumptions are unfalsifiable — and therefore useless.
Common assumption types:
- Market size — TAM, SAM, SOM; growth rate; customer segments
- Customer behavior — willingness to pay, churn, expansion, referrals
- Revenue model — conversion rates, deal size, sales cycle, CAC
- Competitive position — moat durability, competitor response speed, switching cost
- Execution — team velocity, hire timeline, product timeline, operational scaling
- Macro — regulatory environment, economic conditions, technology availability
明确地陈述假设。不要说“我们的市场很大”，而要说“德国中小企业B2B支出管理软件的总可寻址市场规模为23亿欧元”。
假设越具体，就越容易测试。模糊的假设无法被证伪——因此毫无用处。
常见假设类型：
- 市场规模——TAM、SAM、SOM；增长率；客户细分
- 客户行为——付费意愿、流失率、拓展收入、推荐率
- 收入模型——转化率、交易规模、销售周期、CAC
- 竞争地位——护城河持久性、竞争对手响应速度、转换成本
- 执行能力——团队效率、招聘周期、产品上线时间、运营规模化
- 宏观环境——监管环境、经济状况、技术可用性
Step 2: Find the Counter-Evidence
步骤2：寻找反证
For every assumption, actively search for evidence that it's wrong.
Ask:
- Who has tried this and failed?
- What data contradicts this assumption?
- What does the bear case look like?
- If a smart skeptic was looking at this, what would they point to?
- What's the base rate for assumptions like this?
Sources of counter-evidence:
- Comparable companies that failed in adjacent markets
- Customer churn data from similar businesses
- Historical accuracy of similar forecasts
- Industry reports with conflicting data
- What competitors who tried this found
The goal isn't to find a reason to stop — it's to surface what you don't know.
针对每个假设，主动寻找证明其错误的证据。
思考：
- 谁尝试过这件事但失败了？
- 哪些数据与这个假设矛盾？
- 最坏的情况是什么样的？
- 如果一个精明的怀疑论者看待这个假设，他们会指出什么问题？
- 这类假设的基准成功率是多少？
反证来源：
- 在相邻市场失败的同类公司
- 类似业务的客户流失数据
- 类似预测的历史准确率
- 存在冲突数据的行业报告
- 尝试过此事的竞争对手的结果
我们的目标不是找到放弃的理由，而是发现未知的风险。
Step 3: Model the Downside
步骤3：建模下行风险
Most plans model the base case and the upside. Stress testing means modeling the downside explicitly.
For quantitative assumptions (revenue, growth, conversion):
| Scenario | Assumption Value | Probability | Impact |
|---|---|---|---|
| Base case | [Original value] | ? | |
| Bear case | -30% | ? | |
| Stress case | -50% | ? | |
| Catastrophic | -80% | ? |
Key question at each level: Does the business survive? Does the plan make sense?
For qualitative assumptions (moat, product-market fit, team capability):
- What's the earliest signal this assumption is wrong?
- How long would it take you to notice?
- What happens between when it breaks and when you detect it?
大多数计划只会建模基准情况和上行情况。压力测试意味着要明确建模下行风险。
针对量化假设（收入、增长、转化率）：
| 场景 | 假设值 | 概率 | 影响 |
|---|---|---|---|
| 基准情况 | [原始数值] | ? | |
| 熊市情况 | -30% | ? | |
| 压力情况 | -50% | ? | |
| 灾难性情况 | -80% | ? |
每个层级的核心问题：企业能存活吗？计划还合理吗？
针对定性假设（护城河、产品市场契合度、团队能力）：
- 这个假设错误的最早信号是什么？
- 你需要多久才能发现？
- 从假设失效到你察觉这段时间会发生什么？
Step 4: Calculate Sensitivity
步骤4：计算敏感性
Some assumptions matter more than others. Sensitivity analysis answers: if this one assumption changes, how much does the outcome change?
Example:
- If CAC doubles, how does that change runway?
- If churn goes from 5% to 10%, how does that change NRR in 24 months?
- If the deal cycle is 6 months instead of 3, how does that affect Q3 revenue?
High sensitivity = the assumption is a key lever. Wrong = big problem.
有些假设的影响更大。敏感性分析要回答：如果这个假设发生变化，结果会有多大改变？
示例：
- 如果CAC翻倍，现金流 runway会有什么变化？
- 如果流失率从5%上升到10%，24个月后的NRR会有什么变化？
- 如果销售周期从3个月变成6个月，会对第三季度收入产生什么影响？
敏感性高 = 该假设是关键杠杆。一旦错误 = 大问题。
Step 5: Propose the Hedge
步骤5：提出对冲方案
For every high-risk assumption, there should be a hedge:
- Validation hedge — test it before betting on it (pilot, customer conversation, small experiment)
- Contingency hedge — if it's wrong, what's plan B?
- Early warning hedge — what's the leading indicator that would tell you it's breaking before it's too late to act?
对于每个高风险假设，都应该有对冲方案：
- 验证对冲——在投入资源前先测试（试点、客户访谈、小型实验）
- 应急对冲——如果假设错误，备选方案是什么？
- 预警对冲——哪些领先指标能在为时已晚前告诉你假设正在失效？
Stress Test Patterns by Assumption Type
按假设类型划分的压力测试模式
Revenue Projections
收入预测
Common failures:
- Bottom-up model assumes 100% of pipeline converts
- Doesn't account for deal slippage, churn, seasonality
- New channel assumed to work before tested at scale
Stress questions:
- What's your actual historical win rate on pipeline?
- If your top 3 deals slip to next quarter, what happens to the number?
- What's the model look like if your new sales rep takes 4 months to ramp, not 2?
- If expansion revenue doesn't materialize, what's the growth rate?
Test: Build the revenue model from historical win rates, not hoped-for ones.
常见失误：
- 自下而上的模型假设100%的销售线索都会转化
- 未考虑交易延误、客户流失、季节性因素
- 假设新渠道在大规模测试前就会生效
压力测试问题：
- 你实际的销售线索历史赢单率是多少？
- 如果你的前3大交易推迟到下一季度，数据会变成什么样？
- 如果新销售代表需要4个月才能上手，而不是2个月，模型会变成什么样？
- 如果没有拓展收入，增长率会是多少？
测试方法： 基于历史赢单率而非预期值构建收入模型。
Market Size
市场规模
Common failures:
- TAM calculated top-down from industry reports without bottoms-up validation
- Conflating total market with serviceable market
- Assuming 100% of SAM is reachable
Stress questions:
- How many companies in your ICP actually exist and can you name them?
- What's your serviceable obtainable market in year 1-3?
- What percentage of your ICP is currently spending on any solution to this problem?
- What does "winning" look like and what market share does that require?
Test: Build a list of target accounts. Count them. Multiply by ACV. That's your SAM.
常见失误：
- 仅通过行业报告自上而下计算TAM，未进行自下而上验证
- 将总市场与可服务市场混淆
- 假设100%的SAM都是可触达的
压力测试问题：
- 你的理想客户画像（ICP）中实际存在多少家公司，你能说出它们的名字吗？
- 第1-3年你的可服务可获得市场（SOM）是多少？
- 你的ICP中有多少比例的公司目前正在为解决该问题付费？
- “获胜”是什么样的，需要占据多少市场份额？
测试方法： 列出目标客户清单，统计数量，乘以平均客户生命周期价值（ACV），这就是你的SAM。
Competitive Moat
竞争护城河
Common failures:
- Moat is technology advantage that can be built in 6 months
- Network effects that haven't yet materialized
- Data advantage that requires scale you don't have
Stress questions:
- If a well-funded competitor copied your best feature in 90 days, what do customers do?
- What's your retention rate among customers who have tried alternatives?
- Is the moat real today or theoretical at scale?
- What would it cost a competitor to reach feature parity?
Test: Ask churned customers why they left and whether a competitor could have kept them.
常见失误：
- 护城河是6个月就能复制的技术优势
- 网络效应尚未显现
- 数据优势需要你目前不具备的规模
压力测试问题：
- 如果资金充足的竞争对手在90天内复制了你最好的功能，客户会怎么做？
- 尝试过竞品的客户留存率是多少？
- 护城河是现在就存在，还是仅在规模扩大后才理论上存在？
- 竞争对手达到功能 parity需要多少成本？
测试方法： 询问流失的客户为什么离开，以及竞争对手是否能留住他们。
Hiring Plan
招聘计划
Common failures:
- Time-to-hire assumes standard recruiting cycle, not current market
- Ramp time not modeled (3-6 months before full productivity)
- Key hire dependency: plan only works if specific person is hired
Stress questions:
- What happens if the VP Sales hire takes 5 months, not 2?
- What does execution look like if you only hire 70% of planned headcount?
- Which single person, if they left tomorrow, would most damage the plan?
- Is the plan achievable with current team if hiring freezes?
Test: Model the plan with 0 net new hires. What still works?
常见失误：
- 招聘周期假设基于标准招聘流程，而非当前市场情况
- 未考虑上手时间（3-6个月才能达到全产能）
- 依赖关键招聘：只有招聘到特定人员计划才能生效
压力测试问题：
- 如果招聘销售副总裁需要5个月而不是2个月，会发生什么？
- 如果只招聘到计划人数的70%，执行情况会如何？
- 如果哪个人明天离职，会对计划造成最大的损害？
- 如果冻结招聘，当前团队能否完成计划？
测试方法： 假设净招聘人数为0来建模计划，哪些部分仍然可行？
Competitive Response
竞争对手响应
Common failures:
- Assumes incumbents won't respond (they will if you're winning)
- Underestimates speed of response
- Doesn't model resource asymmetry
Stress questions:
- If the market leader copies your product in 6 months, how does pricing change?
- What's your response if a competitor raises $30M to attack your space?
- Which of your customers have vendor relationships with your competitors?
常见失误：
- 假设行业领先者不会响应（如果你在获胜，他们一定会）
- 低估响应速度
- 未考虑资源不对称
压力测试问题：
- 如果市场领导者在6个月内复制你的产品，定价会如何变化？
- 如果竞争对手融资3000万美元进入你的领域，你会如何应对？
- 你的哪些客户与竞争对手有供应商合作关系？
The Stress Test Output
压力测试输出
ASSUMPTION: [Exact statement]
SOURCE: [Where this came from — model, investor pitch, team gut feel]
COUNTER-EVIDENCE
• [Specific evidence that challenges this assumption]
• [Comparable failure case]
• [Data point that contradicts the assumption]
DOWNSIDE MODEL
• Bear case (-30%): [Impact on plan]
• Stress case (-50%): [Impact on plan]
• Catastrophic (-80%): [Impact on plan — does the business survive?]
SENSITIVITY
This assumption has [HIGH / MEDIUM / LOW] sensitivity.
A 10% change → [X] change in outcome.
HEDGE
• Validation: [How to test this before betting on it]
• Contingency: [Plan B if it's wrong]
• Early warning: [Leading indicator to watch — and at what threshold to act]ASSUMPTION: [精确陈述]
SOURCE: [假设来源——模型、投资者推介、团队直觉]
COUNTER-EVIDENCE
• [挑战该假设的具体证据]
• [同类失败案例]
• [与假设矛盾的数据点]
DOWNSIDE MODEL
• Bear case (-30%): [对计划的影响]
• Stress case (-50%): [对计划的影响]
• Catastrophic (-80%): [对计划的影响——企业能否存活？]
SENSITIVITY
This assumption has [HIGH / MEDIUM / LOW] sensitivity.
A 10% change → [X] change in outcome.
HEDGE
• Validation: [在投入资源前的测试方法]
• Contingency: [假设错误时的备选方案]
• Early warning: [需要关注的领先指标——以及触发行动的阈值]