深思圈 / AI 创业 0-1 案例 + 增长打法

何时打开:你在做 0-1 创业 / 想找 PMF / 想看具体增长案例。本 wiki 把深思圈 102+ 篇案例按"创业判断 / PMF / 0-1 增长 / 1-10 增长 / 10-100 规模化"五块组织。

一句话核心:a16z PMF 三条路(顶级客户/指数曲线/dogfood)+ 红杉 Terrifying Questions 4 问 + Lovable 6 招打法 + Perplexity 5 大增长引擎(三年半 4.5 亿 ARR) + 0 → 月入 10 万美金 9 个月。

0. 完整创业周期里 5 块拆解

阶段	关键问题	代表方法
判断要不要做	a16z 供给驱动 / Founder-market fit	红杉 Terrifying Questions
找 PMF	灯泡时刻 / 冷启动率 > 关系率	a16z PMF 三条路
0-1 增长	第一个 10/100/1000 用户	Lovable 6 招 / buildinpublic
1-10 增长	5000-50000 用户 / ARR 起飞	Perplexity 5 大引擎
10-100 规模化	5000 万 → 10 亿 ARR	Snowflake 第一销售 0 → 40 亿

1. 判断要不要做 —— Founder-market fit

1.1 红杉 Terrifying Questions 4 问

详见深思圈 / AI 一级市场 VC 视角(a16z + 红杉 + YC) §2.1。

核心:

问题 1:我的公司有什么存在的权利? → Founder-market fit
案例:Nubank David Vélez 花数月研究巴西银行业

1.2 a16z 供给驱动型市场

详见深思圈 / AI 一级市场 VC 视角(a16z + 红杉 + YC) §1.1。

核心:

"如果你能为创作者提供变现的能力,你就会创造出今天不存在的作者和内容" —— Substack 投资逻辑

1.3 反共识建议(深思圈案例)

"1 年半融了 1 亿美金,这位创始人却给出了这些反共识的建议!"

(详见原档,通常涉及"反 VC 标准建议 / 反速度狂热 / 反招聘狂热")

2. 找 PMF

2.1 a16z PMF 三条路(Jason Rosenthal 2026-05)

详见深思圈 / AI 一级市场 VC 视角(a16z + 红杉 + YC) §1.3。

3 条:

和顶级客户一起做 —— 客户需求 = 你的 spec
站在指数曲线前面 —— 押新基础设施
自己做自己的第一个客户 —— dogfood

2.2 红杉 Terrifying Questions 2/3 问

问题	积极信号
2. 人们真的足够在乎吗?	冷启动客户命中率 > 关系客户 / 客户眼神发亮 / 主动参与 demo / 找到"设计伙伴"
3. 我的产品真的能改变行为吗?	灯泡时刻 / 短时间上手 / 粘性功能点

案例:DoorDash 与数百家小餐厅深聊 → 锁定"拒单又无法负担配送"的本地餐厅

2.3 PMF 失败信号(Jason)

"如果你靠 Growth hacks 和持续空投来维持活跃,而不是出于清晰的战略目的,这本身就是在承认你还没找到 PMF。"

3. 0-1 增长打法

3.1 Lovable 6 招(增长负责人首次公开)

详见深思圈 / AI Coding 公司案例(Cursor/Lovable/Bolt/Devin/Replit) §2:

6 个月 5000 万 ARR
10 个月百万用户
传统增长策略彻底失效

6 招(摘要):

不投流(传统 paid ads)
不做 SEO 关键词竞价
重 UGC + showcase + 社区
(详见原档)

3.2 buildinpublic(出海经典)

"出海会用到的爆款增长方式:#buildinpublic"

核心:

公开建设过程
每日推进 + 数据透明
信任建立 → 用户主动传播

3.3 9 个月做到月入 10 万美金(AI 视频)

"从 0 到月入 10 万美金:一个人如何在 9 个月内打造 AI 视频的现金印钞机"

(典型 indie hacker 路径)

3.4 一个读书 APP 0 到千万用户(3 年)

"一个读书 APP 如何 3 年内从 0 到千万用户?增长环路全揭秘"

3.5 Canva 0 → 1 SEO 技巧

"Canva 的 SEO 技巧从 0 到 1 大揭密|阶跃 Insights"

核心:

程序化 SEO
高频长尾关键词
自动化模板批量页

3.6 Webflow 无代码增长

"万字解析无代码领头羊 Webflow 的增长之路"

4. 1-10 增长引擎

4.1 Perplexity 5 大增长引擎(4.5 亿 ARR / 三年半)

"被早期投资人当场泼冷水,三年半后 Perplexity 做到 4.5 亿美元 ARR —— 五大增长引擎全拆解"

(深思圈深度文章,5 大引擎详见原档)

4.2 1 年 15 倍增长(欧洲 AI 客服)

"1 年 15 倍增长,硅谷顶级 VC 投资 2000 万美金,这家来自欧洲的公司如何在拥挤的 AI 语音客服赛道杀出重围"

4.3 6 个月 10 倍增长(Software 3.0 先驱)

"6 个月 10 倍增长,揭秘这家公司如何一步步成为 Software 3.0 时代的先驱"

5. 10-100 规模化

5.1 Snowflake 第一销售 0 → 40 亿

"Snowflake 第一位销售大揭秘:从 0 到 40 亿美元的增长方法论"

5.2 1-100 模式:收购半死不活年入 10 亿

"不做 0 到 1,专做 1 到 100:这家公司靠收购"半死不活"的产品年入 10 亿"

含义:并不是所有创业都要做 0-1,1-100 同样赚大钱。

5.3 0 → 8 亿:23 岁销售天才获客密码

"从零到 8 亿美元:一个 23 岁销售天才的获客密码"

6. 完整 GTM 指南

6.1 0-1-10-100 GTM 实战指南

"从 0 到 1 再到 10,最系统的 GTM 打法指南(附实战案例)"

典型 GTM 节点:

0-1:Founders 亲自做销售 / 50 个种子客户
1-10:第一个销售雇佣 / 销售流程标准化
10-100:销售团队扩张 / 渠道伙伴 / 大客户

6.2 入选 a16z Top50 增长负责人方法论

"入选 A16Z Top50 AI 产品的增长负责人分享方法论,YC 校友分享创业和做产品的心路历程,Magineer 第二期产品精选"

7. 关键案例库(按增长里程碑)

7.1 月入级

案例	月入
金融分析套壳应用(复刻 Cal AI)	4 万美金
AI 视频(一个人 9 个月)	10 万美金
Pretext(2 娃妈)	2100 万围观

7.2 ARR 级

案例	ARR / 时间
Readdy.ai	500 万 / 4 个月
Lovable	5000 万 / 6 个月
Perplexity	4.5 亿 / 三年半

7.3 估值级

案例	估值
逆袭独角兽(被 YC 拒 2 次)	10 亿(25 岁)
AI 法律独角兽	7 亿(25 岁电竞)
AI 客服华人	15 亿
Cursor	500 亿

8. 创业方法论 4 大趋势

深思圈 / AI 创业 0-1 案例 + 增长打法 source:AI 时代的创业指南:四个全新趋势

(深思圈整理 / 详见原档)

典型:

AI 让单人创业变独角兽可能
审美 > 模型(小红书共识)
平民化(Pretext)
长期主义(Dan Koe)

9. Founder Mode 升级

"Founder Mode 已经不够用了 —— AppSumo 前 CEO:AI 时代,创始人要从「做引擎」升级到「设计引擎」"

含义:

旧:Founder Mode = Brian Chesky / 亲力亲为
新:设计引擎 = AI Agent + 多 Agent 编排 + 系统化协作

详见 newtype 心法 · 超级个体方法论 §Life OS + 时间管理 / 个人 OS / Life OS(跨作者主题综合)

10. 跨作者交叉点

主题	深思圈本 wiki	姊妹 wiki
创业方法论整体	一级 VC 案例视角	创业方法论(从 0 到 1)(跨作者主题综合) / 一堂 / 五步法完整体系(关键假设 + 业务里程碑 + 五步法 5 进阶 + 落地) / 王凯 AI 时代创业方法论与商业判断框架
PMF + 5 步法	红杉 4 问 + a16z 3 路	一堂 / 五步法完整体系(关键假设 + 业务里程碑 + 五步法 5 进阶 + 落地)(Truman 5 步法)
精益创业 / MVP	a16z 反 Growth hack	精益创业 / MVP / 关键假设(跨作者主题综合) / 一堂 / 情报调研 + 精益实验完整体系
需求分析	DoorDash / Nubank 案例	需求分析 / JTBD / 产品内核(跨作者主题综合) / 一堂 / 需求分析完整体系(拆推评算 4 阶 + JTBD)
增长打法 / GTM	Lovable / Perplexity / Snowflake	AI 自媒体与内容工程化(跨作者主题综合)(AI 自媒体增长)
机会预判	a16z 供给驱动	机会预判 / 商业预判 / 终局视角(跨作者主题综合) / 一堂机会预判方法论

11. 怎么用 —— 按阶段的 0-1 路径

你在哪	主用	起点
想判断要不要做	红杉 4 问 + a16z 供给驱动	Founder-market fit / 愿意投 10 年?
找 PMF	a16z PMF 三条路 + 红杉 2/3 问	顶级客户 / 指数曲线 / dogfood
0-1 增长	Lovable 6 招 + buildinpublic + 程序化 SEO	不投流 / 重社区 / 透明
1-10 ARR 起飞	Perplexity 5 大引擎 + 1 年 15x	增长引擎组合
10-100 规模化	Snowflake / 0 → 8 亿	销售标准化 / 大客户
想做 1-100 不做 0-1	收购半死不活 10 亿	收并购路径

通用纪律:

供给驱动 + Founder-market fit —— 判断起点
PMF = 真实用户持续用 —— 不是 TVL/粉丝数/融资额
不靠 Growth hacks 续命 —— 那是承认没 PMF
传统增长策略失效(Lovable 反共识) —— 新一代 AI 公司不投流
Founder Mode 升级"设计引擎" —— AI 时代创始人新角色
0-1 和 1-100 都可以赚大钱 —— 不必硬选 0-1

12. 引用清单

深思圈作者全集入口 —— 全集入口
主要 source:sources/learning/深思圈/ 含 "PMF" / "创业" / "增长" / "0 到 1" / "GTM" 等 ~102+ 篇
深思圈 / AI 一级市场 VC 视角(a16z + 红杉 + YC) —— a16z + 红杉 + YC 视角
深思圈 / AI Coding 公司案例(Cursor/Lovable/Bolt/Devin/Replit) —— Lovable / Readdy.ai 详情
创业方法论(从 0 到 1)(跨作者主题综合) —— 综合创业方法论
一堂 / 五步法完整体系(关键假设 + 业务里程碑 + 五步法 5 进阶 + 落地) —— Truman 5 步法
王凯 AI 时代创业方法论与商业判断框架 —— 王凯反"融资=成功"
精益创业 / MVP / 关键假设(跨作者主题综合) —— 精益创业 / MVP
需求分析 / JTBD / 产品内核(跨作者主题综合) —— 需求分析 / JTBD

来源与关联资料

2026-10-17 增补：从可展示功能走到能持续交付的产品

来源为深思圈对 Alfred Lin 斯坦福分享的中文转述。保留方法及观点归属；历史收入、估值和杠杆数字未独立核验，不用来论证成功概率。

热情要落到一条能执行的路线

一个功能能让人看见可能性，却还不能说明用户愿意持续使用。Alfred Lin 所强调的热情与冷静执行并存，可以落实为三个阶段：功能证明某件事做得到；产品路线说明优先服务谁、接下来补哪些关键环节；持续交付则要求团队稳定兑现这些承诺。不能只用演示反响替后两步验收。

阶段	应当留下的证据	常见误判
功能	用户能完成一个具体动作，失败条件可说明	演示惊艳便以为完整问题已解决
产品路线	明确目标用户、重复需求与本轮取舍	收集很多点子，却没有决定先解决什么
持续交付	有人负责结果，承诺可跟进，反馈能改变下一轮安排	靠个人热情补洞，把偶尔成功当作稳定能力

上述表格是本库的应用推导。它补充已有PMF与客户访谈方法，不替代付款、留存或真实替代行为的验证。功能很小也可能有价值；关键在于它是否稳定解决了用户关心的问题，而不是功能数量是否足够多。

把信念与观察连起来

坚定判断应有来自客户、现场和反复实践的依据。可以在每轮复盘时写下：最初相信什么、看到什么支持或反驳证据、因此调整了哪项承诺。若只能引用名人判断或团队热情，证据仍不足；若每次反馈都改变全部方向，也难以累积学习。

何时用。 在演示受到欢迎、团队准备扩大投入或产品路线不断摇摆时，用这张表检查当前到底完成了哪一步。可以保留长期方向，同时根据具体观察修改短期计划；这不是保证增长的公式。与创业与投资中已有的转向与反馈讨论互相参照，不重复复制其案例。

2026-10-17 Addition: Move from a demonstrable feature to a product you can deliver consistently

The source is Shensiquan’s Chinese account of Alfred Lin’s Stanford talk. Methods and viewpoints retain their attribution. Historical revenue, valuation and leverage figures have not been independently verified and are not used to argue for a probability of success.

Turn enthusiasm into an executable roadmap

A feature can demonstrate a possibility without showing that users will keep using it. Alfred Lin’s emphasis on combining enthusiasm with disciplined execution can be applied across three stages: a feature proves that something can be done; a product roadmap identifies whom to serve first and which essential gaps to address next; consistent delivery requires the team to fulfill those commitments reliably. A positive reaction to a demo cannot serve as acceptance evidence for the latter two stages.

Stage	Evidence to retain	Common misjudgment
Feature	Users can complete a specific action, and its failure conditions can be explained	Assuming an impressive demo solves the whole problem
Product roadmap	Target users, recurring needs and the current trade-offs are explicit	Collecting many ideas without deciding what to solve first
Consistent delivery	Outcomes have owners, commitments can be tracked and feedback changes the next round of work	Filling gaps through personal enthusiasm and mistaking occasional success for reliable capability

The table is this knowledge base’s proposed application. It supplements existing product-market fit and customer-interview methods without replacing evidence of payment, retention or actual switching behavior. A small feature can be valuable. What matters is whether it reliably solves a problem users care about, rather than how many features it includes.

Connect conviction to observation

Strong judgments should be grounded in customers, field observations and repeated practice. At each review, record what you initially believed, what supporting or contradicting evidence you observed and which commitment changed as a result. Celebrity opinions and team enthusiasm alone remain insufficient evidence. Changing the entire direction after every piece of feedback also makes cumulative learning difficult.

When to use it. When a demo is well received, the team is considering a larger commitment or the roadmap keeps shifting, use the table to identify which stage has actually been completed. Retain a long-term direction while adjusting near-term plans to specific observations; this is not a formula that guarantees growth. Read alongside the existing discussion of pivots and feedback in Startups and investing, without duplicating its cases.

2026-10-19 增补：先明确内容给谁看，再把承诺与反馈接起来

为什么有内容产量仍不一定有增长？深思圈对 YouTube 策略师 Oscar 的 Distribution 播客访谈所作的中文整理，强调先回答 who（目标观众是谁），再选择制作方式。这一案例的流程启发，是把受众定义、内容承诺与反馈连接起来；成功案例本身不足以确立普遍因果关系。

从目标受众的任务开始。把理想客户画像（ICP）落成“这个人遇到什么问题、为什么愿意点开、看完能做什么”。大量不相关观看不能直接证明内容带来了产品使用；认知内容与客户教程也不必承担同一种转化任务。
拍摄前先写清楚承诺。先确定点子、标题与缩略图共同表达的价值，再编排脚本和素材。这样可以在昂贵制作前检查内容是否有明确对象。标题制造了好奇，正文就要兑现，更强的包装无法补足根本不存在的信息。
同时看点击和观看后的兑现。点击弱时先检查选题与包装，点击后很快流失时检查开头、内容与承诺是否一致。这些是待验证的诊断方向，不能单凭一个数字定位原因；受众构成与分发环境也可能变化。
每轮只明确改变一个因素。记录原版本、改变项、观察窗口与对应受众，先尝试标题或缩略图中的一个，再比较反馈。受访者给出的点击率、标题字符数和实验天数是情境中的经验，不能直接拿来考核所有频道；点击提升也要检查是否牺牲观看质量与真实产品任务。

是否拆分品牌认知频道与 how-to（使用教程）频道，要看两类观众的任务是否明显不同。访谈转述以娱乐或行业故事吸引潜在用户、以教程服务已在使用的人；同一订阅人群对两类内容长期反应不同时，可以考虑拆开，并先评估维护能力。这不是要求每个小团队立刻经营两个频道。

“七小时信任法则”、LLM 引用来源排名、观看量与引用关系、预算带来的固定收益等说法，本次未取得独立核验，不作为通用规则。可以实践的部分是：明确受众、让承诺可以检查、让反馈能指向下一轮改进。

来源：深思圈对 Oscar 访谈的中文整理。

October 19, 2026 addition: define the audience, then connect the promise to feedback

Why does producing more content not necessarily produce growth? Shensi's Chinese account of a Distribution podcast interview with YouTube strategist Oscar emphasizes answering “who is the audience?” before choosing how to produce content. The workflow lessons connect audience definition to a testable content promise and feedback. Successful cases alone do not establish a universal causal relationship.

Start with the audience's task. Turn the ideal customer profile, or ICP, into concrete questions: what problem does this person face, why would they click, and what could they do after watching? Large numbers of irrelevant views do not directly establish product use. Awareness content and customer tutorials need not perform the same conversion task.
Write the promise before filming. Establish the value communicated by the idea, title, and thumbnail together, then plan the script and material. This lets the team check for a clear audience before expensive production. If a title creates curiosity, the content must deliver; stronger packaging cannot supply information that is absent.
Examine both clicks and delivery after the click. When clicks are weak, examine topic selection and packaging first. When viewers leave quickly after clicking, examine whether the opening and content match the promise. These are diagnostic hypotheses to test, not causes established by a single number. Audience composition and distribution conditions can also change.
Specify one factor to change in each round. Record the original version, change, observation window, and audience. Try changing either the title or the thumbnail before comparing feedback. The interviewee's click-through rates, title lengths, and test durations are contextual experience, not performance standards for every channel. A gain in clicks should also be checked for losses in viewing quality or meaningful product tasks.

Whether to separate a brand-awareness channel from a how-to channel depends on whether the two audiences have substantially different tasks. The account describes entertainment or industry stories attracting potential users while tutorials serve existing users. If the same subscriber base consistently responds differently to the two formats, separation may be worth considering after assessing the team's capacity to maintain both. This does not require every small team to operate two channels immediately.

Claims about a “seven-hour trust rule,” rankings of sources cited by LLMs, the relationship between views and citations, and fixed returns from particular budgets were not independently verified here and are not presented as general rules. The actionable elements are defining an audience, making the promise testable, and using feedback to guide the next iteration.

Source: Shensi's Chinese account of the Oscar interview.

2026-10-23 增补：历史评分快速初筛，实际试用保留

小团队可以让 Agent 根据过去的人工判断缩小候选范围，但不能把自动排序当成最终验证。深思圈对 Garry Tan 与 Paul Copplestone 对谈的转述中，Garry 把上一次黑客松手工评分、排名交给 Agent，生成可复用的代码与 Markdown；随后仍亲自试用，并与筛出的五到十位作者交谈。它提供的是一次流程案例，不证明自动评分普遍准确，也不构成招聘筛选规则。

本库应用：保留原始人工判断依据、自动排序结果及人工复核后的变化，检查被筛掉的候选中是否有新类型被旧标准忽略。把“节省了浏览多少候选”与“最后选得是否合适”分开看。来源也提到公开衡量标准可能被针对性迎合，即古德哈特问题：当指标成为目标，它可能不再忠实代表原本想衡量的价值。因此即使排序稳定，也要继续实际使用、听取反馈，并在任务变化时重审标准。

创业基本功、真实用户反馈在本页已有覆盖，不再重复追加；这里只补“历史判断生成初筛工具—保留人工体验—检查指标被迎合”的案例及边界。来源中的产出倍数、公司收入、模型记忆准确率和科学突破预测未独立核验，不纳入本节结论。

来源：https://www.woshipm.com/ai/6483135.html

October 23, 2026 Addition: Use Historical Scores for Shortlisting, Retain Direct Evaluation

A small team can use an agent to narrow candidates using past human judgments, while retaining direct evaluation. In Shensi’s account of Garry Tan’s conversation with Paul Copplestone, Tan feeds an earlier hackathon’s manual scores and rankings to an agent to produce reusable code and Markdown. He still tries the products and talks to five to ten shortlisted builders. This is a workflow example, not evidence that automated scoring is generally accurate or a hiring-screening rule.

Application in this knowledge base: retain the rationale behind the original judgments, the automatic ranking and changes after human review. Check whether older criteria exclude promising new kinds of candidates. Evaluate browsing time saved separately from the suitability of the eventual choice. The source also raises the risk that published metrics invite people to optimize for them, the Goodhart problem: when a measure becomes a target, it can stop representing the underlying value. Stable rankings therefore still need direct use, feedback and renewed criteria when the task changes.

This article already covers startup fundamentals and real user feedback. The addition is limited to the sequence of building a first-pass filter from past judgments, retaining human experience and checking for metric gaming. Unverified productivity multiples, company revenues, memory-retrieval accuracy and scientific forecasts are excluded from the conclusion.

Source: https://www.woshipm.com/ai/6483135.html

English edition

Shensi: Startup Cases, Product-Market Fit and Growth Playbooks

When to read this: You are starting a company, looking for product-market fit, or comparing specific growth cases. This synthesis organizes Shensi's collection of more than 102 cases into five stages: deciding whether to start, finding product-market fit, initial growth, growth from one to ten, and scaling from ten to one hundred.

Core reference points: a16z's three paths to product-market fit—working with leading customers, getting ahead of an exponential curve, and being your own first customer—alongside Sequoia's four “Terrifying Questions,” Lovable's reported six-part growth playbook, Perplexity's reported five growth engines and $450 million in annual recurring revenue after three and a half years, and a solo AI-video business reportedly reaching $100,000 in monthly revenue in nine months.

This is a complete English edition of the previously published synthesis. Company metrics, valuations, growth multiples and case headlines retain their historical status as claims in that collection; translating them does not independently verify them or make them current figures. Where the published note supplies only a headline or refers readers to a longer source, this edition preserves that limitation rather than inventing the missing explanation. ARR means annual recurring revenue. Product-market fit, abbreviated PMF, means a product meeting a market's demand; go-to-market, or GTM, concerns how the product reaches and wins customers.

0. Five Parts of the Startup Journey

Stage	Key question	Representative approach
Deciding whether to start	Supply-driven markets and founder-market fit	Sequoia's Terrifying Questions
Finding product-market fit	The light-bulb moment; stronger response from cold prospects than personal connections	a16z's three paths to PMF
Initial growth, from zero to one	The first 10, 100 and 1,000 users	Lovable's six-part playbook and building in public
Growth from one to ten	From 5,000 to 50,000 users; ARR begins to accelerate	Perplexity's five growth engines
Scaling from ten to one hundred	From 50 million to one billion in ARR	The Snowflake first-sales-hire case, described as growth from zero to $4 billion

The stages and numbers reproduce the historical framework. The table combines examples with different measures and scales; it is not a single benchmark that every company must follow.

1. Deciding Whether to Start: Founder-Market Fit

1.1 Sequoia's Four Terrifying Questions

The companion note on Shensi's venture-capital landscape, section 2.1, contains the broader discussion.

The question highlighted here is: What gives my company the right to exist? The note connects this to founder-market fit. Its example is Nubank founder David Vélez spending months studying Brazil's banking industry.

The source overview names four questions but does not spell out all four in this section. Questions two and three appear below; this edition does not invent the missing fourth question.

1.2 a16z and Supply-Driven Markets

The companion venture-capital landscape note, section 1.1, discusses the investment logic around Substack: enabling creators to earn money can bring into existence creators and content that do not yet exist.

This is the supply-driven-market argument recorded in the collection, rather than a claim that every new monetization tool creates a viable market.

1.3 Contrarian Advice in the Shensi Cases

One archived headline describes a founder who raised $100 million in a year and a half but offered advice that ran against conventional wisdom.

The published synthesis points to the longer source and characterizes the likely themes as questioning standard venture-capital advice, speed obsession and aggressive hiring. It does not reproduce the actual advice in detail; those possible themes should not be mistaken for a verified account of the interview.

2. Finding Product-Market Fit

2.1 a16z's Three Paths, Attributed to Jason Rosenthal in May 2026

The companion venture-capital landscape note, section 1.3, provides the related discussion. The three paths recorded here are:

Build with leading customers. Their needs become the product specification.
Get ahead of an exponential curve. Make a bet on emerging infrastructure.
Be your own first customer. Use the product yourself—often called dogfooding.

2.2 Questions Two and Three in Sequoia's Framework

Question	Positive signals recorded in the note
Do people care enough?	A stronger response from cold prospects than relationship-based prospects; visible excitement; active participation in demos; finding design partners
Can my product actually change behavior?	A light-bulb moment, a short path to getting started, and features that encourage continued use

The DoorDash example describes conversations with hundreds of small restaurants, leading the founders toward local restaurants that were turning away orders yet could not afford delivery.

These are case signals for further investigation, not thresholds that establish PMF on their own.

2.3 A PMF Warning Attributed to Jason Rosenthal

The source argues that relying on growth hacks and ongoing airdrops to sustain activity, without a clear strategic purpose, can amount to admitting that product-market fit has not yet been found.

The distinction is between activity sustained by the underlying product and activity repeatedly supported by incentives. It is the source's diagnostic argument, not a universal prohibition on incentives.

3. Growth From Zero to One

3.1 Lovable's Reported Six-Part Playbook

The note on Shensi's AI coding companies, section 2, contains the fuller account. The historical summary reports 50 million in ARR in six months, one million users in ten months, and a claim that traditional growth strategies had stopped working in this setting.

Although the heading calls this a six-part playbook, the published summary enumerates only the following elements:

Avoid traditional paid advertising.
Do not bid on SEO keywords, using the source's terminology.
Emphasize user-generated content, showcases and community.
Consult the longer source for the remaining details.

The edition retains that incomplete enumeration. It does not infer three additional tactics or treat this company's account as a rule for every AI startup. The wording about SEO and bidding also remains the source summary's wording rather than a newly standardized marketing taxonomy.

3.2 Building in Public

An archived growth article presents #buildinpublic as a method for products expanding internationally. The summary identifies three elements:

Share the building process publicly.
Make progress regularly and show the data transparently.
Build trust that can lead users to share the product themselves.

3.3 A Solo AI-Video Business Reportedly Reaching $100,000 a Month in Nine Months

The collection includes a case headlined as one person building an AI-video business from zero to $100,000 in monthly revenue in nine months. The published note labels it a typical independent-builder path but provides no detailed operating sequence in this section.

The amount and time frame are case-headline claims, not a forecast for another builder.

3.4 A Reading App Reportedly Reaching Ten Million Users in Three Years

Another case headline asks how a reading app grew from zero to ten million users over three years and promises a breakdown of its growth loops. This section of the published synthesis contains the headline only, rather than the loops themselves.

3.5 Canva's Early SEO Tactics

The Canva case is presented as an account of moving SEO from zero to one, associated with Jieyue Insights. Its summarized tactics are:

Programmatic SEO.
Frequently searched long-tail keywords.
Automated production of template pages at scale.

3.6 Webflow's No-Code Growth

The collection includes a long-form analysis of Webflow's growth as a leading no-code product. The published overview supplies the case title without reproducing its detailed explanation.

4. Growth Engines From One to Ten

4.1 Perplexity's Reported Five Engines

The historical headline describes Perplexity receiving a dismissive reaction from an early investor, then reaching a reported $450 million in ARR three and a half years later. It promises five growth engines.

The published synthesis directs readers to the full Shensi article for those five engines. They are not listed here, so this edition does not manufacture them.

4.2 Reported Fifteenfold Growth in One Year for a European AI Customer-Service Company

Another case headline describes a European business standing out in a crowded AI voice customer-service market, growing fifteenfold in a year and receiving a $20 million investment from a leading Silicon Valley venture firm. The published summary does not identify the company or give the underlying measurements in this section.

4.3 Reported Tenfold Growth in Six Months for a Software 3.0 Pioneer

The collection also includes a case promising an explanation of how a company grew tenfold in six months and became a pioneer of Software 3.0. This section preserves the headline-level reference without adding a company identity or mechanism absent from the public note.

5. Scaling From Ten to One Hundred

5.1 Snowflake's First Sales Hire: The Reported Path From Zero to $4 Billion

An archived headline presents the growth methodology of Snowflake's first salesperson as a journey from zero to $4 billion. The overview does not specify the precise metric behind that headline here; it should not automatically be read as a directly comparable ARR series.

5.2 The One-to-One-Hundred Acquisition Model

A case headline describes a company that bypasses starting products from scratch and instead acquires struggling products, reportedly generating one billion in annual revenue. The published headline does not specify the currency in this instance, and this edition does not add one.

The original takeaway is that starting from zero to one is not the only entrepreneurial path: improving and scaling existing products can also be economically significant. The headline's revenue claim does not establish how repeatable or attractive a particular acquisition would be.

5.3 From Zero to $800 Million: A Young Salesperson's Customer-Acquisition Case

Another archived headline describes the customer-acquisition methods of a 23-year-old salesperson associated with growth from zero to $800 million. The overview provides no further operating details or metric definition here.

6. A Go-to-Market Guide

6.1 GTM Across Zero-to-One, One-to-Ten and Ten-to-One-Hundred

A referenced guide is described as a systematic account of moving from zero to one and then to ten, with practical cases. The published synthesis summarizes typical GTM transitions as follows:

Zero to one: founders sell directly and work toward roughly fifty seed customers.
One to ten: make the first sales hire and standardize the sales process.
Ten to one hundred: expand the sales team, work with channel partners and serve larger accounts.

These are stages suggested by the summary, not required customer counts or a hiring schedule for every company.

6.2 Growth-Leader and YC Alumni Accounts

The collection references an issue of Magineer's product selections featuring a growth leader from a product listed in a16z's Top 50 AI products, alongside YC alumni discussing entrepreneurship and product building. The overview records it as a source of methods, without spelling out the full playbook in this section.

7. Case Library by Milestone

The following tables preserve the historical examples and figures in the public source. Some case names are descriptive labels rather than identified companies. They use different measures and should not be treated as a ranked or normalized dataset.

7.1 Monthly-Revenue-Level Examples

Case	Figure reported in the original table
A financial-analysis wrapper app, described as replicating Cal AI	$40,000 a month
A solo AI-video business after nine months	$100,000 a month
Pretext, described as a mother of two's project	21 million people watching or following the story; this is an attention figure, not monthly revenue

The original places Pretext under a monthly-revenue heading, but its cell records attention rather than income. This edition retains the example while making that mismatch explicit.

7.2 ARR-Level Examples

Case	Reported ARR and time frame
Readdy.ai	5 million in four months
Lovable	50 million in six months
Perplexity	450 million in three and a half years

The original table omits currency symbols in these cells. Its preceding Perplexity case explicitly uses dollars. No missing currency is silently supplied for the other rows.

7.3 Valuation-Level Examples

Case label in the collection	Reported valuation or accompanying detail
A founder who became a unicorn after being rejected by YC twice	One billion; founder aged 25
An AI legal unicorn associated with a former esports player	700 million; age 25
An AI customer-service company associated with a Chinese founder	1.5 billion
Cursor	50 billion

These cells reproduce the historical magnitude without assigning an omitted currency or independently verifying the valuations. The labels in the first three rows do not provide enough detail to identify the companies reliably.

8. Four Trends in Startup Methods

The source collection includes an article described as a guide to four new trends in entrepreneurship in the AI era. The public summary presents the following themes:

AI may make a one-person unicorn possible.
Aesthetic judgment can matter more than the model, described as a view shared on Xiaohongshu.
Broader access to building, illustrated by Pretext.
Long-term commitment, associated with Dan Koe.

These are the summary's themes and aspirations, not a verified prediction of outcomes or a complete reproduction of the original article.

9. An Extension of Founder Mode

A case associated with AppSumo's former CEO argues that Founder Mode is no longer sufficient: founders should move from building the engine toward designing the engine in the AI era.

The summary contrasts an earlier image of Founder Mode, associated with Brian Chesky and direct hands-on involvement, with a newer role coordinating AI agents, multi-agent orchestration and systematic collaboration.

The related notes on newtype's independent-operator mindset and on time management and Life OS provide the companion discussions. This is the source's proposed shift in the founder's role, not a claim that founders no longer need direct customer or operational knowledge.

10. Connections Across Authors

Topic	Perspective in this Shensi synthesis	Related public notes
Startup methods overall	Cases viewed through leading venture investors	General startup methodology; Yitang's complete five-step method; Wang Kai's startup methodology
PMF and the five-step method	Sequoia's questions and a16z's three paths	Yitang's five-step method, associated with Truman
Lean startup and MVPs	a16z's warning against using growth hacks to sustain activity without PMF	Lean startup and MVP; Yitang's research and lean experiments
Demand analysis	DoorDash and Nubank cases	Demand analysis and jobs to be done, or JTBD; Yitang's complete demand-analysis guide
Growth playbooks and GTM	Lovable, Perplexity and Snowflake	AI-enabled content and self-media engineering
Anticipating opportunities	a16z's supply-driven-market perspective	Opportunity forecasting; Yitang's opportunity-forecasting note

The public links collected at the end of this edition preserve the original article's available cross-references.

11. How to Use the Framework by Stage

Where you are	Main references	Starting question or activity
Deciding whether to start	Sequoia's four questions and a16z's supply-driven-market view	Founder-market fit; willingness to commit ten years
Finding PMF	a16z's three paths and Sequoia's questions two and three	Leading customers, exponential infrastructure curves, or using your own product
Initial growth	Lovable, building in public and programmatic SEO	Community, transparency and the case's preference against paid acquisition
ARR acceleration from one to ten	Perplexity's five-engine case and the reported fifteenfold-growth case	Combining growth engines
Scaling from ten to one hundred	Snowflake and the zero-to-$800-million sales case	Standardizing sales and working with large accounts
Improving existing products rather than starting from scratch	The struggling-product acquisition case	An acquisition-led path

The original proposes six general disciplines:

Begin with the supply-driven opportunity and founder-market fit.
Look for real users continuing to use the product, rather than substituting total value locked, follower counts or money raised for PMF.
Do not rely on growth hacks simply to keep activity alive; the source treats that as a warning that PMF may be missing.
Re-examine traditional growth tactics. The Lovable case favors community over paid acquisition, but its claim that traditional strategies have failed is not evidence that no AI company should advertise.
Consider the founder's role in designing a working system, not just performing every task personally.
Recognize that both building from scratch and improving existing products can create value; there is no obligation to choose zero-to-one entrepreneurship.

These are the synthesis's organizing lessons. They remain starting points for examining a specific product, rather than guaranteed growth recipes.

12. References in the Historical Synthesis

The published note points to Shensi's author overview as the collection entry, and to a source collection of roughly 102 or more items tagged with terms such as PMF, entrepreneurship, growth, zero to one and GTM. That archive count describes the collection behind the note, not the number of fully reproduced cases on this page.

Its main companion notes cover:

Shensi's venture-capital landscape: a16z, Sequoia and YC perspectives.
Shensi's AI coding companies: more detail on Lovable and Readdy.ai.
General startup methodology.
Yitang's complete five-step method, associated with Truman.
Wang Kai's startup methodology and his argument against treating fundraising as success.
Lean startup and the minimum viable product.
Demand analysis and jobs to be done.

Public reference links are retained in the final section. Local archive paths and private note identifiers are not needed for the English reader and are not introduced into this edition.