Anthropic 寫給創辦人的 AI 原生新創指南。主軸：2026 年的 AI 已經把寫 code、做研究、跑營運的門檻壓到極低，創辦人從「自己動手做」轉成「指揮 AI agents」。手冊把新創旅程重新分成 Idea / MVP / Launch / Scale 四階段，逐段拆解每階段該用什麼 AI 工具、會踩什麼坑。
文章結構
2026 的新創生命週期被 AI 重啟（lifecycle rebooted）
「成為創辦人」的定義在改變：從執行者變成 AI 編排者
Idea Stage：用 AI 驗證點子、做市場研究、寫第一版 pitch
MVP Stage：agentic coding 把工程團隊壓縮成一個人
Launch Stage：用 AI 跑增長、客服、營運自動化
Scale Stage：組織結構與 AI 編制的長期共存
同一份工作、新的規則 + 資源清單
逐段拆解
全部切換：
點擊段落左側的 EN/中 按鈕切換語言，淡入淡出 300ms。預設英文，鼓勵先讀原文。
Chapter 1 — The startup lifecycle, rebooted for 2026
第一章：2026 重啟的新創生命週期
AI is reshaping how startups are built. Founders who've never written a line of code are shipping production applications today, and the lean 10-person unicorn has gone from scrappy underdog story to deliberate plan of action.
AI 正在重塑新創的打造方式。今天，連一行 code 都沒寫過的創辦人也能推出正式上線的應用程式；而「10 人團隊估值十億美金」這種精簡組織，已經從少數異類的傳奇故事，變成被刻意設計出來的標準劇本。
新字：reshape, ship（出貨／上線）, production application, lean, unicorn, scrappy, underdog, deliberate, plan of action
In 2026, AI can write production code, conduct market research, synthesize competitive landscapes, draft investor materials, and automate operational workflows. By eradicating the once-steep learning curves that even experienced technical founders faced in integrating the tools, platforms, and systems needed to bring their idea to life, AI has above all leveled the playing field around who can launch a startup or build a product.
新字：conduct, synthesize, competitive landscape, draft, eradicate, steep learning curve, integrate, above all, level the playing field
句型解析
主句「AI has leveled the playing field」被一個超長的 By 分詞片語前置。閱讀技巧：先跳過 By 子句找到主句動詞 has leveled，再回頭看 By 提供的條件。level the playing field：把比賽場地弄平＝消除不公平的優勢。
In 2026, a good idea gets founders further than ever. Agentic coding compresses what used to take a team of engineers into work a founder can ship themselves.
新字：agentic, compress, used to take, ship themselves
The traditional startup growth arc assumes that the path from idea to scale is validate → raise → hire → build → raise again → grow → hire more → repeat. Now, AI has erased the expectation that each new phase in the startup lifecycle requires a bigger team, a different skill set, and a fresh funding round.
This playbook remaps the four core stages of the startup journey (Idea, MVP, Launch, and Scale) according to these new realities. We examine what each stage looks like when AI is core to your technical and organizational development, what the right tools are for each phase, and how founders using these tools are compressing timelines. If you're ready to map the shortest path between idea and exit, read on.
這份手冊依照這些新現實，把新創旅程的四個核心階段（Idea 點子、MVP 最小可行產品、Launch 上線、Scale 規模化）重新繪製。我們會檢視：當 AI 是技術與組織發展的核心時，每個階段長什麼樣子；每個階段對的工具是哪些；用這些工具的創辦人如何壓縮時間軸。如果你準備好為「從點子到 exit」找出最短路徑，請繼續讀下去。
新字：playbook, remap, journey, examine, core, organizational, timeline, exit（出場、退場）, read on
Chapter 2 — What it means to be a founder is changing
第二章：「成為創辦人」這件事正在改變
Founders used to be defined by what they could do: technical founders wrote code, non-technical founders ran business ops and closed deals. But the models, systems, and AI agents available to founders in 2026 have dissolved the wall between "people who can build" and "people with ideas worth building."
新字：define, ops（operations 縮寫）, close deals, dissolve, worth -ing
AI-native startups are fundamentally transforming what it means to be a founder. Now someone with no engineering background can build production software that brings their idea to life, while a technically adept founder with little business knowledge can easily produce a go-to-market strategy, a financial model, and a highly polished pitch deck.
AI 原生的新創正從根本上改變「當創辦人」的意義。現在，沒有任何工程背景的人能做出正式上線的軟體把點子變成現實；而技術很強但不太懂商業的創辦人，也能輕鬆產出 go-to-market（進入市場）策略、財務模型、高完成度的 pitch deck（募資簡報）。
Historically, founders spent the bulk of their time in execution mode: writing code, managing people, handling day-to-day operational work. In an AI-native startup, the founder role becomes much less individual contributor and much more orchestrator of agents—specialized AI assistants that can read files, run commands, execute code, and even browse the web. The founder's attention shifts up the stack toward the higher-order work: generating ideas and directing the systems (AI agents, tools, and whatever small team exists) that carry those ideas out.
過去創辦人大半時間都在「執行模式」：寫 code、管人、處理每天的雜事。在 AI 原生新創裡，創辦人的角色從「親自下海做事的人（individual contributor）」變成「指揮 agents 的編排者（orchestrator）」——這些 agents 是專門化的 AI 助理，能讀檔案、執行指令、跑程式碼、甚至上網瀏覽。創辦人的注意力往上層移動，集中在更高層次的工作：生點子，然後指揮整套系統（AI agents、工具、現有的小團隊）把點子落地。
新字：historically, the bulk of, execution mode, day-to-day, individual contributor, orchestrator, specialized, browse the web, shift up the stack, higher-order, carry out
文化脈絡
individual contributor (IC)：科技公司術語，指「自己動手做事」的工程師/設計師，相對於 manager。shift up the stack：stack 原指技術堆疊（前端、後端、資料庫），這裡引申為「往更抽象、更高層次的工作移動」。
The most revolutionary result of AI as central infrastructure, though, is to unblock non-technical founders with subject matter expertise. When the founding pool expands beyond people with engineering backgrounds, you get startups built by people with radically different lived experiences, solving real problems that the traditional tech-founder pipeline never prioritized (or perhaps even noticed).
The traditional startup model assumed you needed to hire engineers to build, salespeople to sell, and ops people to run the business. Headcount was treated as a sign of organizational momentum and product maturity.
Early-stage startups in 2026 are radically different. They're extremely lean by design, often just the founder alone or a team with a few others. By centering both technical and organizational development on AI as infrastructure, they can reach product validation, early revenue, or even profitability before scaling the team. There are three areas in particular where AI helps a startup function like a much larger org: research, agentic coding, and automating workflows for key business operations.
2026 年的早期新創長相完全不同。他們刻意極度精簡，常常只有創辦人一個人，或加上少數幾個夥伴。他們把技術與組織發展同時建在 AI 這個基礎設施上，因此能在團隊還沒擴張前，就達到產品驗證、初期營收、甚至獲利。AI 特別在三個領域，讓小新創能像大組織一樣運作：研究、agentic coding、關鍵業務營運的工作流自動化。
新字：early-stage, by design, center on, product validation, profitability, scale the team, function like
Conversational intelligence and research
對話式智慧與研究
Think: on-call expert for every domain.
Consider everything a founder needs to know in the first year that they almost certainly don't know going in: how do I set up payroll? How do I plan product development sprints? How do I draft a tight investor memo?
Early-stage startup questions like these all used to have the same answer, which was Find someone who knows. For a bootstrapped or pre-seed founder, this could consume time spent knowledge-gathering instead of building, or possibly requiring burning a chunk of early capital on a consultant. Now, they have AI as an on-call expert across every conceivable domain.
這類早期新創的問題，過去答案都一樣：去找一個懂的人問。 對 bootstrapped（自掏腰包）或 pre-seed（種子前）的創辦人來說，這要嘛吃掉本來該拿來開發的時間去到處問人，要嘛得燒掉一筆寶貴的早期資金請顧問。現在不用了，他們有 AI 作為「橫跨所有可想像領域」的隨叫專家。
devil's advocate：源自天主教，封聖儀式中專門「找該候選人毛病」的角色，引申為「故意唱反調以檢驗論點」。pre-mortem：mortem 是「驗屍」，pre- 是「事前」，由心理學家 Gary Klein 提出：在專案開始前先假設它已經失敗，請團隊反推為什麼會失敗，找出風險。
Agentic coding
代理式編程
Think: the engineer who's always available, never blocked.
Building software used to require a technical co-founder, a contract dev shop, or a long enough runway to hire an engineering team before you'd written a line of production code.
新字：available, blocked, co-founder, contract dev shop, runway
文化脈絡
blocked：工程圈黑話，「被卡住、無法繼續」，常見「I'm blocked on X」。dev shop：dev = development，shop 指「外包軟體開發公司」。runway：飛機跑道，創投圈引申為「公司在燒光錢前還剩多少時間」，通常用月為單位。
Agentic coding tools now allow every aspiring founder to describe what they want to build in plain language and direct AI to generate, test, debug, and refactor a production-grade codebase at the speed and scale of a full engineering team.
Agentic coding 工具現在讓每個想創業的人，可以用日常語言描述他想做什麼，然後指揮 AI 去生成、測試、除錯、重構一份正式上線等級（production-grade）的程式碼庫，速度與規模都跟一整支工程團隊一樣。
The timeline from "I have an idea" to "I have a product" has compressed. And the founder's role now centers on what to build and why, while AI handles the actual construction of real infrastructure that's ready for real users.
從「我有一個點子」到「我有一個產品」的時間軸被壓縮了。創辦人現在的角色集中在「要做什麼、為什麼要做」，而 AI 負責真正動手蓋出能讓真實使用者用的基礎設施。
新字：timeline, compressed, center on, construction, infrastructure
Workflow automation
工作流自動化
Think: on-demand, automated ops team.
Even when a founder can research like a consultant and build like an engineering team, there's still a whole category of work beyond strategic planning or product development that still has to get done. Scheduling meetings, updating the CRM, pulling weekly reports, keeping documentation current, publishing content, tracking compliance requirements, managing the connective tissue between the tools and systems the company runs on all have to happen, too. In a lean startup, this load falls mainly on the founder—and it's a significant tax on the time and attention that should be going toward higher-order decisions.
Workflow automation with AI tools offloads that tax. Recurring operational tasks can be configured to happen automatically so that the CRM updates when a deal moves, a weekly report compiles itself, and product documentation gets updated in sync with product changes. And, crucially, Claude Cowork integrates with the interconnected systems a startup runs on—your project management tool, your communication stack, your data sources—without needing someone to build and maintain those integrations. In Day Zero startups, that someone is almost always the founder.
用 AI 工具做工作流自動化，可以把這筆「稅」卸下來。重複性的營運任務可以設定成自動發生：成交一筆 deal 時 CRM 自動更新、週報自己編譯、產品文件跟著產品變更同步更新。更關鍵的是，Claude Cowork 能直接整合新創在跑的那一整套互相連動的系統——你的專案管理工具、你的溝通工具堆疊、你的資料來源——而你不需要再找一個人來蓋與維護這些整合。在 Day Zero（第零天）的新創裡，那個「人」幾乎永遠就是創辦人本人。
新字：offload, recurring, configure, compile, in sync with, crucially, integrate, interconnected, communication stack, data sources, Day Zero
文化脈絡
Claude Cowork：Anthropic 的產品名稱，定位是「跟你一起工作的 Claude」。stack：技術圈黑話，指「一整套互相搭配的工具」（如 Slack + Notion + Linear 是「溝通 stack」）。Day Zero：新創圈用語，「公司還沒正式開始的那一天」，比 Day One 更早，常指籌備期。
Timing and orchestration are everything
時機與編排，決定一切
Founders that effectively harnesses AI's research, automation, and agentic coding capabilities can build a startup that operates with far more leverage than its headcount suggests. They also get to dedicate the majority of their time and bandwidth to the work that actually matters.
有效駕馭 AI 的研究、自動化、agentic coding 三項能力的創辦人，能建立一間槓桿遠遠高於員工人數所暗示的新創公司。他們也能把大部分時間與心力，留給真正重要的事。
bandwidth：原指網路頻寬，矽谷黑話借來指「人的處理能力／剩餘精力」（"I don't have bandwidth for this"＝我沒空管這個）。harness：本意「給馬套韁繩駕馭」，引申「善用、駕馭」一股力量。
This work doesn't happen on autopilot; the founder orchestrating these AI tools needs to know how (and when) to apply them. The rest of this playbook is dedicated to exploring the goals and challenges founders will encounter as they follow the AI-native startup path, and how to effectively apply AI tools at each stage of the journey.
這些事不會自動發生（不是 autopilot 自動駕駛）；負責編排 AI 工具的創辦人得知道「怎麼用」、更要知道「什麼時候用」。這本手冊接下來的部分，會逐一探討創辦人走在 AI 原生新創路徑上會遇到的目標與挑戰，以及在旅程的每個階段該怎麼有效運用 AI 工具。
Every startup founder starts from the same place: a problem they can't stop thinking about. This is the startup phase where idea meets reality: startup success in 2026 requires the discipline of not building until the evidence justifies it.
The work in this stage is research, customer discovery, competitive analysis, and honest evaluation of disconfirming evidence, all before asking Claude Code to generate your first line of production code.
這個階段的工作是：研究、客戶探索（customer discovery）、競品分析，以及對「反證據（disconfirming evidence）」做誠實的評估——全部在你開口請 Claude Code 生成第一行正式程式碼之前完成。
customer discovery：精實創業（Lean Startup）術語，由 Steve Blank 提出，意思是「在做產品前，先去跟潛在客戶談，驗證假設」。disconfirming evidence：反向證據——主動找「能推翻自己假設的證據」，是科學方法核心。
Idea stage goal
點子階段的目標
While in the Idea stage, the founder's main goal is research-oriented validation: assembling solid evidence that a real problem exists (and that your proposed solution effectively addresses it) before committing resources to building.
Practically speaking, the Idea stage is a series of questions a founder has to answer in roughly this order:
實際操作上，點子階段就是一連串問題，創辦人大致照下面這個順序逐一回答：
Is this problem real, specific, and frequent enough to build around?
這個問題夠真實、夠具體、發生得夠頻繁，足以圍繞它做一間公司嗎？
新字：specific, frequent, build around
Who exactly has it, and is that a market?
究竟是誰有這個問題？這些人加起來夠成一個市場嗎？
Is anyone else solving it, and if so, how and how well?
已經有其他人在解這個問題嗎？如果有，他們怎麼解、解得多好？
What would a solution actually need to do in order to solve this problem, and does my idea do that?
真正能解決這個問題的解方，到底要做到哪些事？我手上的點子有做到那些事嗎？
The results of these inquiries add up to answer a single, ultimate question: Is this worth building?
這幾道題的答案加總起來，會指向一個最終問題：這值得做嗎？
新字：inquiry, add up to, ultimate
That means getting specific before you get moving. "People struggle with expense reporting" is an observation. "Finance managers at mid-market companies spend four-plus hours a week reconciling submissions because their current tools don't integrate with their accounting software" is a testable hypothesis.
The Idea stage exit condition is finding problem-solution fit. You've established qualitative evidence, primarily from real human conversations, that you're solving a real problem for real people before you start building the thing that solves it.
problem-solution fit：精實創業里程碑。比它更後的目標是 product-market fit (PMF)——產品做出來後跟市場真的對得上。順序是：problem-solution fit → MVP → product-market fit。
You're ready to leave the Idea stage when you can answer yes to all three of the following:
當你對下面三個問題都能答 yes，就可以離開點子階段：
1. Is the problem real and specific? Answering in the affirmative here requires that you can name exactly who experiences this problem, how often they encounter it, how severely it affects them, and what they currently do about it.
新字：in the affirmative, encounter, severely, affect
2. Does your solution address the actual problem? Not the problem you originally assumed, but the one the validation process revealed. Sometimes these are the same thing, but not always.
3. Do you have enough signal to justify building? You will never have certainty at this stage, and waiting for it is its own failure mode, but you need enough qualitative evidence that committing to an MVP is a reasoned decision over an act of faith.
新字：signal, certainty, failure mode, reasoned decision, act of faith
文化脈絡
signal：科技圈用語，「能告訴你方向對不對的證據訊號」，相對於 noise（雜訊）。act of faith：信仰縱身，多半帶貶意，指「沒證據就賭下去」。
Idea stage challenges
點子階段的挑戰
The Idea stage is where the most important work of your startup journey happens, because it's where the most consequential mistakes are made: getting something wrong now can quickly run your budding venture right off the rails. The majority of ideation phase challenges involve moving faster than your understanding justifies, though, so founders who proceed with thoughtfulness and deliberation will experience steady progress.
新字：consequential, budding venture, off the rails, ideation, proceed, thoughtfulness, deliberation, steady
文化脈絡
off the rails：本意「火車脫軌」，引申「事情失控、完全偏離正軌」。budding：bud 是花苞，budding 形容「剛萌芽、還在發芽階段」。
Mistaking building for validating
把「做出來」誤認為「驗證了」
The challenge: When technical blockers are lifted, an impassioned founder risks skipping the most important work in the startup journey: validating that their idea is genuinely a solution that people need and will use.
Even before the current era of agentic coding, 42% of startups failed because they built something nobody wanted. Now, though, agentic coding solutions like Claude Code have drastically collapsed the distance between "I have an idea" and "I have a product" and that failure rate is only going to climb.
While there's never been a better time to be a founder with a synapse-shakingly good idea, the rapidity and ease of spinning up a prototype that looks something like a product also, counterintuitively, presents a genuinely dangerous existential risk for the AI-native startup.
如果你有一個「讓神經元都顫抖那種等級的好點子」，現在是史上最好的當創辦人時機。但「快速、輕鬆就能弄出一個看起來像產品的原型」這件事，反直覺地，對 AI 原生新創構成了一種真正存亡級的風險。
Until very recently, building required real dev time and budget, and getting even a basic prototype together typically took months. Now that the hurdle of technical development is largely gone, though, AI makes it all too easy for a founder to jump straight into building without validating its utility in the real world.
Reaching problem-solution fit requires first validating your hypothesis then building, but many first-time (and even experienced) founders mistakenly believe that AI short-circuits that requirement, turning the flow into have an idea -> immediately build a prototype -> treat the existence of the prototype as validation. The prototype becomes a reason to believe the hypothesis was right all along, without ever testing whether it's actually true.
達到 problem-solution fit 的正確順序是：先驗證假設，再開發。但許多首次（甚至有經驗的）創辦人誤以為 AI 可以短路掉這個前置驗證，於是流程變成：有點子 → 立刻做原型 → 把「原型存在」這件事當成驗證。原型反過來變成「相信自己假設一直都對」的理由，卻從未測試這個假設是不是真的成立。
新字：short-circuit, treat ... as ..., all along
文化脈絡
short-circuit：本意電路短路，引申「跳過必要的中間步驟、走捷徑」，通常帶負面意涵。
A working prototype is easy to mistake as concrete evidence that you're solving a real problem, but it's not. Your prototype instead serves as a useful pressure-testing prop for conversations with potential users. These conversations themselves are the real evidence.
The challenge: When building is effortless and instant, you can scale execution far ahead of what business demands.
挑戰所在：當開發變得毫不費力、瞬間完成，你的執行規模會大幅超前真實業務需求。
新字：premature, effortless, scale execution
Scaling prematurely means committing to a product path before you've genuinely validated that the path is worth committing to.
過早規模化的意思是：在你還沒真正驗證「這條產品路徑值得投入」之前，就已經一路衝下去。
新字：commit to, path
This has always been a startup killer, but AI has made it dramatically easier for founders to fall into the premature scaling trap without noticing. Agentic coding assistants are so powerful that it's easy to scale execution far ahead of validating problem-solution fit without ever consciously deciding to stray off course.
這從來就是新創殺手，AI 只是讓人「在不知不覺中掉進過早規模化的陷阱」變得容易得多。Agentic coding 助手太能跑，導致創辦人很容易把執行衝到遠遠超前 problem-solution fit 的驗證——而且不會察覺自己已經偏離航道。
新字：dramatically, trap, consciously, stray off course
It will generate, test, debug, and refactor a codebase around a fundamentally flawed premise with exactly the same enthusiasm it brings to a great idea. The intelligence in the system is yours. The prime directive at this stage is keeping your sense-making ahead of your building, especially when building is so quick and feels so effortless.
AI 會用對待好點子完全相同的熱忱，去生成、測試、除錯、重構一份建立在「根本錯誤前提」上的程式碼庫。系統裡的智慧是你的——你才是負責判斷的那個。這個階段的最高指令是：讓你「搞清楚狀況」的速度，永遠跑在你「動手做」的速度前面。尤其是當動手做變得這麼快、這麼不費力的時候。
新字：fundamentally, flawed premise, enthusiasm, prime directive, sense-making
文化脈絡
prime directive：Star Trek（星艦迷航記）術語，星際聯邦的最高指導原則，引申為「凌駕一切的核心原則」。sense-making：認知科學／組織理論術語，指「在資訊不完整時，主動把片段拼成可理解的整體」。
Loss of objectivity
失去客觀
The challenge: Ask an AI tool for evidence supporting what you already believe, and it will find it. Confirmation bias now comes with a research engine.
挑戰所在：請 AI 工具幫你找「支持你既有信念」的證據，它就會找出來。確認偏誤（confirmation bias）現在配備了一台研究引擎。
新字：objectivity, confirmation bias
Confirmation bias has always been an occupational hazard in startups: founders are, by nature, passionate about their ideas. Now, AI tools have given confirmation bias a significant powerup. Ask AI to validate your startup idea and it will find supporting evidence; ask it to size your potential market and it will find the number that makes your TAM look fundable.
確認偏誤一直是新創的「職業病」：創辦人天生就會對自己的點子充滿熱情。AI 工具則讓這個偏誤獲得明顯加乘。請 AI 驗證你的新創點子，它會找到支持證據；請它估你的潛在市場，它會找到一個讓你的 TAM 看起來「可投資」的數字。
新字：occupational hazard, by nature, powerup, size a market, TAM, fundable
AI follows your direction, which means a founder who isn't asking hard questions can now construct an elaborate, well-researched-looking case for a bad idea faster than ever before, while feeling fully confident that they are, in fact, performing due diligence. The antidote is the same tool, only pointed in the opposite direction: AI will pressure-test an idea just as thoroughly as it validates one.
AI 依你的指示走。這意味著：一個不問刁鑽問題的創辦人，現在能用前所未有的速度，為一個爛點子建構出一個精緻、看起來研究過的論述，而且全程深信自己正在做「盡職調查（due diligence）」。解藥是同一把工具，方向反過來用：AI 對「壓力測試」一個點子的徹底程度，跟它驗證一個點子的程度一模一樣。
新字：elaborate, well-researched-looking, due diligence, antidote, pressure-test, thoroughly
文化脈絡
due diligence (DD)：金融／創投術語，「盡職調查」——投資前對標的做的詳盡核實。antidote：原意「解毒劑」，引申「解方／對策」。
When research and structured adversarial thinking surface evidence that your idea needs revision, this the signal to pivot.
Progressing your AI-native startup concept through the Idea stage can feel like it takes forever. You are a founder and you just want to build. But this all-important kickoff phase is fundamentally a research and validation exercise, which means reaching for the tools that help you think more rigorously before pulling all in on writing code. Here are ways to use Claude across its product surfaces (Chat, Claude Cowork, and Claude Code) for moving through the Idea stage as quickly as possible while doing proper due diligence.
把 AI 原生新創的概念推過點子階段，感覺好像永遠走不完。你是創辦人，你只想動手做。但這個關鍵起跑階段本質上是一場研究與驗證的練習——意味著在 all in 開始寫程式前，先伸手拿那些幫你嚴謹思考的工具。下面說明怎麼用 Claude 的三個產品面（Chat、Claude Cowork、Claude Code）盡快走完點子階段，同時做好應有的 due diligence。
新字：progress（動詞）, kickoff, fundamentally, reach for, rigorously, all in, product surface
Chat, Claude Cowork, or Claude Code: choosing the right Claude surface
Chat、Claude Cowork、Claude Code：選對 Claude 介面
AI makes it easier for startup founders to ship faster, automate tedious workflows, and operate at scale, but the surface you use matters. Here's when to use Chat, Claude Cowork, or Claude Code depending on the task at hand.
Chat is for quick exchanges without leaving the app you're already in. Use it for the constant small tasks of running a company: pulling the one-sentence takeaway from a dense investor memo, sanity-checking a claim before a board meeting, or making sense of a long Slack thread with your team.
Claude Cowork is for the knowledge work that actually takes time: pulling from many sources, making sense of it, and producing something finished, like a doc, deck, or spreadsheet. Think turning a folder of customer call transcripts into a themed findings doc for your next product review, building a competitive landscape from a dozen vendor sites before a fundraise, or a standing Monday-morning task that pulls metrics from your connected tools and drops a weekly KPI brief into a shared folder.
Claude Code is the agentic coding environment for the engineers on your team: direct codebase access, Plan Mode, git integration, and local, IDE, or sandboxed cloud environments. It's where a lean team ships features across a growing codebase, migrates legacy code from the MVP days, and moves from prototype to production without waiting on more headcount.
AI 讓創辦人更容易快速出貨、把繁瑣工作流自動化、用小團隊撐大規模——但你選哪個介面有差。下面說明依手上任務該用 Chat、Claude Cowork、還是 Claude Code。
Codebase access, diffs, git, dev environments 程式碼庫存取、diff、git、開發環境
三個介面底下其實是同一個 Claude；變的是「圍繞它的工作環境」。
Defining and pressure-testing the problem hypothesis
定義並壓力測試問題假設
Your own domain expertise and up-front research have already generated a hypothesis. The first job is to sharpen it until it's actually testable. Claude is particularly useful here for forcing specificity: who exactly has this problem, how often, and what do they currently do about it? A problem statement that can't answer those questions precisely isn't ready to validate.
新字：domain expertise, up-front, sharpen, force specificity, problem statement
Exercise: Work with Claude to sharpen your problem statement until it's a testable hypothesis. For example, "Contract review takes too long" is not meaningfully testable. But "In-house legal teams at mid-market companies spend 3+ days per contract review cycle because redlines are managed across email threads rather than a single version-controlled document" is very testable.
練習：跟 Claude 一起把你的問題陳述磨成「可驗證假設」。例如：「合約審閱花太久」不能有意義地驗證；但「中型企業的內部法務團隊，每個合約審閱週期要花 3 天以上，因為紅線（redlines）是散在 email 線程裡管的，不是放在單一版控文件裡」就很可驗證。
Your next move is to ask Claude to argue against your idea, and to find disconfirming evidence to your hypothesis. This can surface negative market signals, failed competitors, customer behavior patterns, and structural obstacles that a supportive synthesis would have quietly deprioritized.
The goal is to arrive at customer discovery having already stress-tested your assumptions against the strongest available counterarguments so that informational user interviews are genuinely open-ended rather than a search for confirmation.
Note: Using Claude as structured devil's advocate is a core use case at every stage of the AI startup life cycle.
備註：把 Claude 當「結構化的魔鬼代言人」用，是 AI 新創生命週期每一個階段的核心使用情境。
Market research and mapping the competitive landscape
市場研究與競爭態勢圖
Sizing up your competitors. There's a startup-specific phenomenon called competitor neglect: the tendency to focus so intensely on your own vision and execution that you systematically underweight what others are doing in the same space. Fortunately, AI offers the antidote: ask Claude to make the most compelling argument for why a competitor in this solution space would succeed while you do not.
盤點你的競爭對手。新創有一種特定現象叫「競爭對手忽視」（competitor neglect）：太專注在自己的願景與執行，導致系統性地低估其他人在同一個賽道做的事。AI 提供解藥：請 Claude 為「同樣解方空間裡的某個競爭對手」，建構出「他會成功而你不會」最有說服力的論述。
Claude can analyze why their approach is actually better, why customers would choose them, why your potential differentiators may not be as defensible as you think.
Claude 能分析：他們的做法為什麼「其實更好」、客戶為什麼會選他們、你以為的差異化點為什麼可能沒你想的那麼可守。
新字：approach, differentiator, defensible
文化脈絡
defensible：創投術語，「可防禦的」——能擋住競爭者複製的優勢，例如網路效應、專利、規模、品牌。VC 常問 "What's your moat?"（你的護城河是什麼）。
Exercise: Ask Claude to map your competitive landscape by tier: direct competitors, indirect competitors, potential acquirers, and adjacent players who could move into your space. Then ask it to argue for why each tier poses a genuine threat to your success, not just the version of the threat that's easiest to dismiss.
練習：請 Claude 依層級畫出你的競爭態勢圖：直接競爭者、間接競爭者、可能的併購者、可能切進你賽道的相鄰玩家。然後請它論述「為什麼每一層都是真正的威脅」——不是那種容易被你打發掉的版本。
新字：tier, indirect, acquirer, adjacent player, pose a threat, dismiss
Market research. Claude Code can synthesize publicly available customer feedback to surface recurring complaints and unmet needs. Bonus: doing this is essentially free qualitative research on your competitors' customers.
新字：synthesize, recurring, unmet needs, qualitative research
Exercise: Direct Claude Cowork to synthesize competitor reviews across your key sources and identify the top complaints that existing solutions haven't resolved. If your hypothesis addresses one or more of them, that's strong evidence of problem-solution fit. If it doesn't, that's worth knowing too.
練習：指揮 Claude Cowork 跨你選定的主要來源綜合競品評論，找出「現有解方還沒解掉的最大抱怨」。如果你的假設正好命中其中一個或多個，這是 problem-solution fit 的強證據。如果沒命中，這件事本身也值得知道。
新字：direct（動詞）, synthesize, top complaints, address, worth knowing
Claude Cowork can also extract relevant information and figures from dense industry reports, analyst filings, and market research documents; next, these clean, synthesized inputs become ideal context for Claude's analysis work.
Claude Cowork 也能從密度高的產業報告、分析師申報、市場研究文件中抽出相關資訊與數字；接著這些乾淨、整合過的輸入就成為 Claude 後續分析工作的最佳脈絡。
Exercise: Build TAM/SAM/SOM models from publicly available data and pressure-test the assumptions behind them. Identify whether the market is expanding, consolidating, or mature; this context influences how you think about timing and differentiation. Map the buyer landscape: who holds budget, who influences decisions, and whether those are the same person.
新字：consolidate, mature, differentiation, buyer landscape, hold budget
文化脈絡
TAM/SAM/SOM：估市場規模的三層套疊。TAM＝Total Addressable Market（全球理論最大值）；SAM＝Serviceable Available Market（你的產品實際服務得到的子集）；SOM＝Serviceable Obtainable Market（短期內你拿得下的部分）。VC pitch deck 必備。
Trend analysis
趨勢分析
Finally, use Claude to listen for early indicators that tell you whether you're entering at the right moment. Track subreddits and LinkedIn groups where conversations about your problem are already happening and the exact language users reach for when describing their issues. Ask Claude to identify analogous markets where a similar problem was solved, and extract what worked and what didn't. Surface regulatory, technological, or demographic trends that could accelerate or threaten the opportunity.
最後，用 Claude 監聽早期指標，告訴你「進場時機對不對」。追蹤已經在討論你的問題的 subreddit 和 LinkedIn 社團，記下使用者描述問題時實際使用的字眼。請 Claude 找出「類似問題曾經被解決」的類比市場，抽出哪些有效、哪些沒效。浮出可能加速或威脅這個機會的法規、技術、人口結構趨勢。
Exercise: Ask Claude to identify three external trends—regulatory, technological, or demographic—that could significantly affect your market in the next two years, and to assess whether each one is a tailwind or a headwind for your specific hypothesis.
練習：請 Claude 找出三個「未來兩年可能顯著影響你市場」的外部趨勢（法規／技術／人口結構），並評估每一個對你的具體假設是順風（tailwind）還是逆風（headwind）。
Note: The market research and competitive mapping work in this section isn't a one-time exercise. You are going to continue making discoveries and evolving your thinking through the MVP and Launch stages, so it's important to repeat these exercises whenever your hypothesis evolves.
The quality of what you learn by talking to potential users for your product is determined by (1) the quality of the questions you ask and (2) whether you are posing these to the right people. Claude is particularly helpful for conducting customer discovery, including who to talk to, what to ask, and how to make sense of what you hear.
A precise target profile is infinitely more valuable than a long contact list, including specific job titles, company types, team structures, and seniority levels most likely to experience the problem acutely. From there, identify where those people are actually reachable—the communities, events, LinkedIn groups, and Slack workspaces where they congregate—and build a prioritization framework for who to reach out to first based on how close they are to the problem.
With your targets defined, use Claude to build the interview framework itself: the right questions, in the right order, structured to surface what people actually do rather than what they think they would do. A rookie founder mistake is asking a generic, open-ended question about the future ("would you use something like this?") instead of specifically querying the relevant past ("tell me about the last time you dealt with this problem.")
目標定好之後，用 Claude 建出訪談框架本身：對的問題、對的順序、結構上要能浮出「人實際做了什麼」而不是「他們以為自己會做什麼」。菜鳥創辦人的標準錯誤是問一個籠統、開放、關於未來的問題（「你會用這種東西嗎？」），而不是具體詢問相關的過去（「跟我說說你上次處理這個問題的情況。」）
新字：framework, surface, rookie, generic, open-ended, query, relevant past
Claude can flag where your draft questions are leading the respondent, too broad, or otherwise likely to generate noise instead of signal. Claude can also help you in designing follow-up questions to probe deflections or drill down on vague answers to important questions.
Claude 能標出你的草擬題目哪裡在「誘導受訪者」、哪裡太寬、或哪些可能產出雜訊而不是訊號。Claude 也能幫你設計後續追問題：探下去看「閃避」、或對重要問題的模糊回答深挖。
If your hypothesis involves more than one persona, Claude can also design different question sets for each. A finance manager and a CFO have different relationships to the same problem, and a single interview framework will flatten that distinction.
Exercise: Draft your interview questions by hand first, ask Claude to audit them. Ask it specifically to flag any question that is leading, future-facing, too broad, or likely to produce a socially desirable answer rather than an honest one. Then ask it to suggest a follow-up probe for the two or three moments in the interview most likely to generate deflection.
練習：先自己手寫一輪訪談題目，然後請 Claude 審。明確要它標出：誘導性的、面向未來的、太寬的、容易讓人給「社交期望答案」而非誠實答案的題目。再請它針對訪談中「最可能出現閃避」的兩三個時刻，建議追問題。
After each conversation, use Claude to debrief: feed it your notes and ask it to identify what confirmed your hypothesis, what challenged it, and what was genuinely surprising. Once you've gathered a batch of interviews, run your full set of interview notes through Claude Cowork to surface recurring themes, contradictions, and the strongest signals in both directions. Then take that synthesized output back to Claude and ask it to flag where your own read of the data might be pattern-matching to what you want to hear rather than what's actually there.
每場對話結束後，用 Claude 做事後檢討（debrief）：把筆記餵給它，請它找出哪些確認了你的假設、哪些挑戰了它、哪些是真正出乎意料。累積到一批訪談後，把整套訪談筆記丟給 Claude Cowork，浮出反覆出現的主題、矛盾、以及雙向最強的訊號。然後把那份綜合輸出再餵回 Claude，請它標出「你自己對資料的讀法，可能在 pattern-match 到你想聽的，而不是實際存在的東西」的地方。
Exercise: After every five interviews, direct Claude Cowork to synthesize your notes and produce two lists: the evidence that supports your hypothesis, and the evidence that challenges it. If the first list is significantly longer than the second, ask Claude whether that asymmetry reflects what's actually in the data—or what you were hoping to find.
練習：每做完五場訪談，指揮 Claude Cowork 綜合筆記，產出兩份清單：支持假設的證據、挑戰假設的證據。如果第一份明顯比第二份長，問 Claude：這個不對稱是反映「資料中真的有的內容」，還是反映「你想找到的東西」。
新字：asymmetry, reflect
Customer outreach and scheduling
客戶接觸與排程
Use Claude Cowork to automate the operational lift around building a contact list, running outreach, and scheduling user interviews.
用 Claude Cowork 把「建聯絡名單、跑外聯、排訪談」這些營運層的舉重活自動化。
新字：outreach, operational lift
Claude Cowork can use the target profile you defined with Claude (including job titles, company types, and seniority levels) to research and compile a structured list of prospects and verified contact information. It then drafts personalized outreach emails at scale, tailoring each one to the individual's role and context.
Claude Cowork 能拿你跟 Claude 一起定義的目標輪廓（含職稱、公司類型、年資層級），去研究並編出一份結構化的潛在對象清單，附驗證過的聯絡資訊。接著批量起草個人化的外聯郵件，每一封都依照對方角色與情境調整。
新字：compile, prospect, verified, personalized, at scale, tailor
As responses come in, it connects to Gmail and Google Calendar via MCP to manage the thread, handle scheduling requests, and get interviews on the calendar. The workflow continues as Claude Cowork generates follow-up drafts on a defined cadence (a day-seven follow-up for contacts who haven't responded, for instance) and updates your tracking sheet as each step completes so you always know where every prospect stands in the pipeline.
Exercise: Give Claude Cowork your validated interview target profile and ask it to build a prospect list, draft a personalized outreach sequence, and set up a tracking sheet with columns for outreach status, follow-up cadence, and interview completion. Then let it run the coordination while you focus on preparing for the conversations themselves.
練習：把你驗證過的訪談目標輪廓給 Claude Cowork，請它建出潛在對象清單、起草一套個人化外聯序列、設一張追蹤表（欄位：外聯狀態、追蹤節奏、訪談完成度）。然後讓它跑協調工作，你專心準備對話本身。
新字：outreach sequence, coordination
Design your final solution concept
設計你最終的解方概念
You've done the validation work: the problem is real, you know who has it, and you have a solution concept that the evidence supports. Use Claude to develop and challenge your solution concept from every angle: What are the gaps? What alternatives exist? What would have to be true for this solution to work at scale? This is an important reality checkpoint: does this design actually address the problem the validation process revealed, and not the problem you originally assumed going in?
驗證工作做完了：問題是真的、你知道誰有這個問題、你有一個被證據支持的解方概念。用 Claude 從每個角度發展並挑戰這個解方：缺口在哪？有什麼替代方案？要讓這個解方規模化運作，什麼前提必須成立？這是個重要的現實檢查點：這個設計是否真的對到「驗證過程浮出的那個問題」，而不是你一開始預設的那個問題？
新字：gaps, alternatives, at scale, reality checkpoint, going in
Exercise: Present your solution concept to Claude and ask it to identify the three assumptions your design depends on most heavily. Then ask what would have to be true for each assumption to hold, and what the consequences are if any one of them doesn't.
Now for the fun part: with a validated hypothesis and a stress-tested solution concept, you're finally ready to build something.
現在來到有趣的部分：手上有了驗證過的假設、壓力測試過的解方概念，你終於準備好動手做東西了。
新字：lightweight, stress-tested
This is the moment in the Idea stage where Claude Code enters the picture. Even if you've been tinkering all along, now is the point where you generate your official lightweight prototype: the minimum surface area needed to put your idea in front of a real human and get a genuine reaction.
這是點子階段裡 Claude Code 正式登場的時刻。就算你一路上都在小修小弄，現在這個點是「產出官方輕量原型」的時刻——剛好夠把點子放到真實人類面前、引發真實反應的最小表面積。
新字：enter the picture, tinker, surface area
文化脈絡
surface area：產品術語，「使用者實際會接觸到的範圍」。最小化 surface area = 砍掉所有非核心功能，只留下足以驗證的部分。
You're not building a real-world product (yet); you're constructing a functional sample of your idea to use in customer and investor conversations. Real users reacting to something they can actually touch will tell you things that a dozen problem-solution discovery interviews couldn't. Before, you were establishing that the problem you're solving is real; now, you are asking potential users to engage with the proposed solution.
Exercise: Define the single core interaction your solution depends on. Direct Claude Code to build only that. When you have it, put it in front of five people from your validated target profile and ask them to try it out. What you learn in those five conversations determines whether you keep building, or go back to the drawing board.
練習：定義你的解方仰賴的「單一核心互動」。指揮 Claude Code 只做那一塊。做出來後，把它放到五個來自驗證過目標輪廓的人面前，請他們試用。這五場對話學到的東西，決定你是繼續做，還是回畫板重來。
新字：single core interaction, try out, go back to the drawing board
文化脈絡
go back to the drawing board：本意「回到繪圖板」（工程師畫設計圖的地方），引申「整個重新設計、重來」。
Reaching the end of the Idea stage is a giant leap ahead in the AI startup race because now you're not betting on a hunch; you're executing against evidence. Now comes the MVP stage, where the founder's guiding question goes from "Is this worth building?" to "What exactly should we build first?" and AI's primary role shifts from research partner to construction crew.
走到點子階段的終點，是 AI 新創競賽裡的一大躍進——因為你不再是賭直覺，而是依據證據在執行。接著進入 MVP 階段，創辦人引導性問題從「這值得做嗎？」變成「我們究竟該先做哪一塊？」；AI 的主要角色，也從「研究夥伴」轉變成「施工隊」。
Plenty of founders treat the MVP stage as a construction phase, but the MVP stage is still fundamentally an evidence-gathering exercise. The difference is that you are now gathering evidence about the solution instead of the problem space; specifically, whether a real, identifiable group of people finds it valuable enough to use it, return to it, pay for it, and/or tell others about it.
新字：plenty of, construction phase, fundamentally, evidence-gathering, identifiable
MVP stage goals
MVP 階段目標
As the founder of an AI-native startup, your goal is to translate a validated problem concept into a working product that real users will actually use. This is not the full version with every roadmap feature but the smallest, most focused iteration of your idea that puts a real solution in front of real users and generates real evidence of product-market fit.
作為 AI 原生新創的創辦人，你的目標是把驗證過的問題概念，轉成一個真實使用者真的會用的可運作產品。這不是包含全部 roadmap 功能的完整版，而是「能把真實解方放到真實使用者面前、產生 product-market fit 真實證據」的最小、最聚焦版本。
新字：translate（轉換）, validated, working product, iteration
At the same time, how you build now determines what's possible later. This means that the MVP stage has a second, equally important goal of moving fast without accruing the type of technical debt that compounds—and will haunt you the moment real users arrive in meaningful numbers.
And finally, investing in persistent context from day one is what keeps AI a force multiplier instead of a source of entropy. In an AI-native startup, your codebase is something you collaborate with AI on session after session, which makes legibility foundational. Founders who skip specs, architectural decisions, and context files (like CLAUDE.md) hit a predictable wall where every new session requires re-explaining the codebase and AI-generated changes drift from the original vision.
最後一條：從第 1 天就投資在「持久化的脈絡」——這是讓 AI 維持「戰力放大器」而不是「混亂來源」的關鍵。在 AI 原生新創裡，你的程式碼庫是你跟 AI 一個 session 接一個 session 共筆出來的，所以「可讀性（legibility）」是地基。跳過規格、架構決策、context 檔（像 CLAUDE.md）的創辦人，會撞到一面可預期的牆：每個新 session 都得重新跟 AI 解釋程式碼庫，而且 AI 生成的改動會逐漸偏離原本願景。
新字：persistent context, force multiplier, entropy, session after session, legibility, foundational, spec, drift
文化脈絡
force multiplier：軍事術語，「戰力倍增器」——讓部隊戰力大幅放大的因素。商業界引申「能放大團隊產出的工具」。entropy：物理熵，「失序的程度」，工程引申「系統會自然走向混亂」。CLAUDE.md：Claude Code 自動讀取的專案脈絡檔。
MVP stage exit criteria
MVP 階段離場條件
The MVP stage exit condition is genuine evidence of product-market fit: proof that a specific, identifiable group of users has found the product valuable enough to return to it (retention), pay for it (revenue), or tell others about it (referral).
MVP 階段的離場條件是 product-market fit 的真實證據：證明一群具體、可識別的使用者，覺得這個產品有價值到願意回來用（retention 留存）、付錢（revenue 營收）、告訴別人（referral 轉介）。
新字：retention, revenue, referral
MVP stage challenges
MVP 階段的挑戰
In the MVP stage, a founder's prime directives are speed and judgment. The challenges here center on whether you can build the right thing, the right way, fast enough to matter, without cutting corners that will cost you later.
The challenge: Because AI essentially removes every natural bottleneck that once controlled what reaches production, speed is guaranteed. But when speed is the only variable that founders factor into their MVP build, they risk accruing technical debt they'll struggle to pay off.
挑戰所在：AI 本質上拆掉了「過去控制什麼能上 production 的每一個自然瓶頸」，所以速度是保證的。但當創辦人只把「速度」這一個變數放進 MVP 開發決策時，會累積出之後難以清償的技術債。
新字：bottleneck, variable, factor in, pay off
Some technical debt is appropriate at the MVP stage, with the understanding that it must be managed before scaling. It builds gradually and can be cleared over time or in a dedicated sprint. AI technical debt, however, compounds.
在 MVP 階段欠一些技術債是合理的，前提是「規模化前要清掉」這個共識。一般技術債是緩慢累積，可以隨時間或安排專門 sprint 清掉。但 AI 技術債會複利。
Without specs and architectural constraints written down somewhere the AI can read, each session re-derives foundational decisions from scratch, and those decisions drift. You end up with a codebase that has no coherent mental model behind it, not because any single piece is bad, but because the pieces were never designed to fit together. That's a real problem, and it does tend to surface late.
新字：re-derive, from scratch, drift, coherent, mental model, fit together, surface（動詞）
Falling for false product-market fit
誤把假性 PMF 當真
The challenge: AI tools can generate impressive early numbers, but these are not a guarantee that the market needs your product.
挑戰所在：AI 工具能催出亮眼的早期數字，但這些不能保證市場真的需要你的產品。
新字：fall for, false, impressive, guarantee
Early momentum is one of the most psychologically powerful experiences a founder can have. After weeks or months of validation work and careful, disciplined building, shipping a product feels like confirmation that you were right all along.
新字：momentum, psychologically, disciplined, ship a product, confirmation
Agentic coding tools can help you reach this moment faster than ever before, but early traction is not the same as product-market fit. Launch energy is generated from ephemeral forces, like your founder's friends, prospective buyers at your investor's other portfolio companies, or a Hacker News headline that drives a spike. Unfortunately, none of these reliably predicts what happens at week six or week twelve when that initial boost has faded.
The challenge: When building feels effortless and nearly free, there's always one more cool feature to add or one more edge case to handle. This scope creep can do more harm than good.
Scope creep has always been a startup risk. The difference now is that the traditional forcing function against it—the real cost of engineering time—no longer exists in the same way when adding a feature takes an afternoon instead of a sprint.
The challenge here is that each individual addition is defensible. Of course the product should handle that edge case; of course users will want that workflow. These don't feel like scope creep in the moment because each one takes so little effort to build with agentic coding, but as your product sprawls beyond its original boundaries you risk losing direction and momentum.
The antidote is a written scope definition created before building begins, describing what the product does, what it deliberately does not do, and the specific evidence from real users that would justify adding something new. This moves the decision point from "should we build this?" to "a critical mass of users have told us they can't get value from the product without this?"
新字：antidote, scope definition, deliberately, justify, decision point, critical mass
文化脈絡
critical mass：核物理術語「臨界質量」，引申「達到某個自我維持的最低量」。
Insecure by inexperience
因經驗不足而不安全
The challenge: Founders using AI tools to rush applications to market without first understanding fundamental security principles end up exposing their users to preventable risks.
挑戰所在：用 AI 工具趕著把應用送上市的創辦人，如果沒先搞懂基本資安原則，會把使用者暴露在可預防的風險裡。
新字：insecure, inexperience, rush ... to market, expose, preventable
The hard truth is that agentic coding tools generate code that works, not code that is inherently secure. Functional code is easy, because either the feature works or it doesn't. Security vulnerabilities are invisible until they're exploited, which means there's no natural feedback loop to alert a first-time founder that something is wrong. Shipping a live MVP to real users, however, means real data, real exposure, and real consequences if something goes wrong.
硬道理：agentic coding 工具生成的程式碼是「能跑的」，不是「天生安全的」。功能型程式碼很好判斷，因為要嘛 work、要嘛不 work。但資安漏洞在被利用之前是看不見的——意味著沒有自然的回饋迴路告訴首次當創辦人的人「有東西不對勁」。把一個 live MVP 出貨給真實使用者，意味著真實資料、真實暴露面，以及出事時的真實後果。
Slighting security isn't brand new to AI-native projects. Bootstrapped startups in every era often delayed security considerations until late in the build, sometimes waiting until the verge of production launch. A security review before any user touches your app or solution is the minimum responsible threshold for releasing a minimum viable product into the world.
輕忽資安在 AI 原生專案出現之前就有了。每個時代的 bootstrapped 新創常常把資安考量延到開發後期，有時候拖到接近 production 發布才處理。「在任何使用者碰到你的 app/解方之前先做一輪資安審查」是把 MVP 放到世界上負責任的最低門檻。
新字：slight（動詞，輕忽）, brand new, the verge of, threshold, release
How Claude can help MVP stage founders
Claude 怎麼幫到 MVP 階段創辦人
Define your architecture before you build. Before Claude Code writes a line of production code, use Claude to define and document the architectural decisions that will govern everything built in this stage: the patterns to follow, the dependencies to avoid, the tradeoffs being made and why. This output will serve as a focused architectural context document and establish the guardrails that Claude Code will operate inside.
動工前先定義架構。在 Claude Code 寫第一行 production code 之前，用 Claude 定義並寫下「會主宰這個階段所有產出」的架構決策：要遵循的模式、要避開的依賴、做了哪些 trade-off、為什麼。這份輸出會作為一份聚焦的架構脈絡文件，並建立 Claude Code 在裡頭運作的護欄。
Without this context, each session starts from scratch and Claude Code is forced to infer its own structural assumptions. Letting Claude Code build without guardrails produces a codebase that will be functional but structurally incoherent, and iterating on and scaling incoherent codebases is ultimately a waste of time and tokens. Sooner or later there's a point where the code inevitably collapses, forcing you to rebuild from scratch.
沒有這份脈絡，每個 session 都從零開始，Claude Code 被迫自己推導結構假設。讓 Claude Code 無護欄地蓋，會產出「能跑但結構不一致」的程式碼庫——對不一致的程式碼庫做迭代與擴大規模，最終就是浪費時間與 token。早晚會到一個點，code 不可避免地崩塌，逼你從零重蓋。
Exercise: Before opening Claude Code, open Claude and describe what you're building: the core problem it solves, the users it serves, and the scale you realistically expect in the next six months. Ask it to help you define the architectural principles that should govern your MVP build, the dependencies to avoid given your constraints, and the tradeoffs you're consciously accepting at this stage.
練習：開 Claude Code 之前，先開 Claude，描述你在蓋什麼：要解的核心問題、服務的使用者、未來 6 個月實際預期的規模。請它幫你定義 MVP 開發該遵循的架構原則、在你的限制條件下要避開的依賴、以及這個階段你刻意接受的 trade-off。
Next, save this output as CLAUDE.md markdown file(s). This is your architectural context document: the first artifact of your build, and the one every subsequent session depends on. CLAUDE.md files serve as project-level instructions for Claude Code, providing project-specific context and instructions that are automatically read by the Agent SDK when it runs in a directory. Functionally, they are persistent "memory" for your project.
Scope creep without friction is one of the defining failure modes of AI-era MVPs. Just as you defined and documented your product's application architecture, you also need to define your MVP's scope before a single feature gets built.
無摩擦的 scope creep 是 AI 時代 MVP 的代表性失敗模式。就像你定義並記下了產品的應用架構一樣，你也得在任何功能蓋下去之前先定義 MVP 範圍。
新字：enforce, friction, failure mode, defining
Claude can help you create a scope document that describes what your MVP product does, what it deliberately does not do, and feature amendment criteria: what specific evidence from real users would justify adding something new at this point.
Claude 能幫你做一份範圍文件，描述：MVP 產品做什麼、刻意不做什麼、以及功能修訂條件——「現階段，要有哪種具體真實使用者證據，才能 justify 加新東西」。
新字：amendment, criteria, justify
When new feature ideas surface—and they surely will—you use Claude to pressure-test whether it's genuine signal from users or founder enthusiasm dressed up as product thinking.
當新功能點子浮出來——而且一定會浮出來——用 Claude 壓力測試它是「來自使用者的真實訊號」，還是「創辦人熱情偽裝成產品思考」。
新字：surface（出現）, dressed up as
Build your MVP with Claude Code
用 Claude Code 蓋你的 MVP
Once architecture and scope are defined, Claude Code becomes the primary MVP build tool. Use it to generate, debug, and iterate on your codebase, but treat each session as an execution of product decisions you have already made, not as an opportunity to throw in some new ones.
Start each Claude Code session by (1) revisiting your scope document and (2) providing the model with your CLAUDE.md architectural context document. End each session by updating it with any decisions the session surfaced. The goal is a codebase whose structure you can explain, not just a codebase that runs.
Exercise: Create a simple session template for your Claude Code work that includes the architectural context document, the specific task for this session, and any constraints or patterns to observe. At the end of each session, add a brief log entry to the context document that details what was built, what decisions were made, and what assumptions the session introduced. Five minutes of documentation per session is cheap insurance against architectural drift that compounds into an unmanageable codebase.
As an AI-native startup founder, your responsibility is to know what's in your codebase, understand any potential exposure vectors, and not ship obvious vulnerabilities to real users who are trusting you with their data.
作為 AI 原生新創創辦人，你的責任是：知道你的程式碼庫裡有什麼、搞懂可能的「暴露途徑」、不要把明顯漏洞出貨給「願意把資料託付給你」的真實使用者。
新字：responsibility, exposure vector, vulnerability
Claude can do a useful first-pass security review of AI-generated code and can help identify common vulnerabilities. It's a good habit to build into the loop before shipping. It is not a substitute for security tooling, however, or, at higher stakes, a human reviewer—and founders who treat it as one are the ones who end up in the breach stories.
Claude 能對 AI 生成的程式碼做一輪有用的初步資安審查，幫你抓常見漏洞。把它編進出貨前迴路是好習慣。它不能取代專門資安工具——在風險更高的情境，也不能取代真人審查。把它當成替代品的創辦人，就是出現在資安漏洞新聞裡的那些人。
Claude Code Security goes further: it scans codebases for security vulnerabilities and suggests targeted patches for human review, surfacing issues that traditional methods can miss.
Claude Code Security 走得更深：它掃描程式碼庫找資安漏洞、提出「給人類審的」針對性修補建議，浮出傳統方法可能漏掉的問題。
新字：scan, targeted, patch, surface
Note: At the time of this ebook's publication, Claude Code Security is a limited beta release so check current availability before building it into your workflow.
Exercise: Before deploying to any real users, run your core application code through Claude with a specific brief: review for authentication and session handling, data exposure in API responses, input validation and injection risks, and dependencies with known vulnerabilities. Treat each finding seriously and assess whether it requires a fix, with human review for anything that touches authentication, secrets, or data handling.
練習：在部署給任何真實使用者前，用一份具體 brief 把你的核心應用碼丟給 Claude 審：身份驗證與 session 處理、API 回應裡的資料暴露、輸入驗證與注入風險、含已知漏洞的依賴項。把每一條發現認真看待，評估是否需要修；任何碰到認證、密鑰、資料處理的部分都要再加人類審查。
injection：注入攻擊（如 SQL injection、XSS、command injection），OWASP Top 10 經典漏洞家族。
Build your measurement framework before launch
在發布之前就把衡量框架建好
The founders who mis-identify early traction as product-market fit are typically the same ones who started tracking data after launch, using metrics chosen to assess what was working rather than to surface what wasn't. The antidote is to establish your measurement framework before the first user shows up.
Use Claude to define which metrics matter for your specific product, what the benchmarks are, and what patterns in the data would constitute genuine product-market fit versus flattering noise. Specifically: set your retention benchmarks, your activation criteria, and your Day 7 and Day 30 targets before releasing your MVP.
用 Claude 定義：對你的具體產品而言哪些指標重要、基準（benchmark）是什麼、資料裡哪種模式才算真 PMF、哪種只是「悅耳的雜訊」。具體說：在發 MVP 前，先設好 retention benchmark、activation 條件、Day 7 和 Day 30 目標。
新字：benchmark, constitute, flattering noise, activation criteria, Day 7 / Day 30 target
Next, define what a false positive looks like for your specific product: signups without activation, revenue without retention, or initial enthusiasm without repeat usage, for example. When the data arrives, ask Claude to make the adversarial case against your own traction: what would a skeptic say about these numbers?
接著，定義「對你的產品而言，假陽性（false positive）長什麼樣」：例如，註冊但未 activation、有營收但無 retention、有初始熱情但無回購使用。資料進來後，請 Claude 對你的 traction 做對抗式論述：一個懷疑論者會怎麼看這些數字？
Once real users are in the product, the operational layer expands fast. Claude Cowork handles the important-but-tedious work like building and maintaining user contact lists, running outreach sequences, scheduling feedback sessions, triaging bug reports, and tracking iteration cycles. The same MCP integrations that managed discovery logistics in the Idea stage apply here.
Keep a human in the collection loop for nuanced exploration of user feedback. A user saying, for example, "this is great but I wish it could also...," requires interpretation: Is it a core need or a nice-to-have? Is it specific to this customer or representative of a segment? Is the missing feature the real problem, or is something upstream in the onboarding? No tool can answer those questions.
新字：nuanced, interpretation, core need, nice-to-have, representative, segment, upstream, onboarding
文化脈絡
upstream / downstream：本意「上游 / 下游」（河流），軟體圈引申「更接近源頭的環節 vs 更接近使用者的環節」。onboarding：新使用者首次進入產品時的引導流程。
Exercise: Configure Claude Cowork to run your MVP-stage feedback loop: draft outreach to your early user list, schedule feedback sessions, design structured intake process for bug reports and feature requests, and write up a weekly synthesis of what's come in. Review the synthesis yourself first; after that, you can ask Claude to analyze the information to catch any significant points you may have overlooked.
練習：把 Claude Cowork 設定來跑你的 MVP 階段回饋迴路：起草給早期使用者名單的外聯、安排回饋場次、為 bug 報告與功能請求設計結構化的收件流程、寫每週綜合報告。先自己看綜合報告；之後請 Claude 分析資訊，抓你可能漏看的重要點。
新字：intake process, synthesis, overlook
Iterate toward evidence, not toward completeness
朝「證據」迭代，不要朝「完整」迭代
The MVP stage ends when you have genuine evidence of product-market fit, no matter how "finished" the product feels. Declaring that you've achieved product-market fit and are now ready to move on from the MVP phase to the Launch stage is ultimately a judgement exercise that combines founder intuition with collected evidence. There are some useful litmus tests, though:
新字：iterate, completeness, declare, intuition, litmus test
文化脈絡
litmus test：本意「石蕊試紙測試」（化學測酸鹼），引申「快速判定的單一決定性測試」。
The Sean Ellis test: Ask your active users: "How would you feel if you could no longer use this product?" If more than 40% answer "very disappointed," that's a meaningful PMF indicator.
Sean Ellis 測試：問你的活躍使用者：「如果你不能再用這個產品，會有什麼感覺？」如果超過 40% 答「非常失望」，那是一個有意義的 PMF 指標。
新字：active user, indicator
文化脈絡
Sean Ellis：「growth hacking」這個詞的發明者，曾任 Dropbox、Eventbrite、LogMeIn 早期成長負責人。這個 40% 門檻是他從多家公司資料歸納出來的經驗法則。
The effort test: Pre-product-market fit, retention requires constant intervention, including frequent outreach, incentives, personal follow-up, and a heroic founder energy expended to keep users engaged. Post product-market fit, the product starts doing that work on its own. When things begin pulling instead of pushing, that shift in effort is one of the clearest signals that something real has changed.
Ultimately, no single data point confirms product-market fit because it's a pattern that has to hold across multiple iteration cycles before you can definitively call it.
What if, even after investing all this work, you just can't seem to arrive at product-market fit? The fact that your results don't confirm the direction you started from is not failure, it's the system working: the MVP stage is designed to surface this information before you over-invest in the wrong answer.
When the data doesn't support your current direction, use Claude to work through what that data is telling you.
當資料不支持你目前的方向，用 Claude 一起穿過去這些資料在說什麼。
Exploring alternative customer segments. Perhaps the users who aren't converting were never the right target to begin with. Often the right audience is already in your data, just underweighted.
Adjusting your product's value prop. Maybe you have the correct audience but your MVP is just not resonating with users. An adjustment to onboarding, messaging, or core feature emphasis can potentially fix this without changing what you've built.
value proposition (value prop)：「我為誰、解決什麼問題、為什麼選我而非別人」一句話的核心承諾。
Stay open to the possibility that the disconnect may run deep enough to require a more fundamental change.
保持開放：「斷層」可能深到需要做更根本的改變。
新字：disconnect, run deep, fundamental
Exercise: If you've completed three or more iteration cycles without meaningful movement toward your product-market fit benchmarks, use Claude to run a diagnostic before deciding what to do next. Feed it your retention data, your user feedback, and your original problem hypothesis, and ask it three questions:
練習：如果你做完三個以上迭代週期，PMF 基準沒有實質進展，在決定下一步前，用 Claude 跑一次診斷。把 retention 資料、使用者回饋、原始問題假設餵給它，問它三個問題：
新字：diagnostic, run
Is there a segment in this data responding differently than the rest?
資料裡有沒有某個 segment 的反應跟其他人不一樣？
Is the gap between designed value and experienced value a positioning problem or a product problem?
「設計出來的價值」與「體驗到的價值」之間的落差，是定位問題還是產品問題？
新字：positioning
What would have to be true for the current product to find genuine PMF, and is that scenario realistic given what you're seeing?
什麼條件必須為真，目前的產品才能找到真 PMF？這個情境，依你現在看到的資料，務實嗎？
新字：scenario, realistic
Let the answers determine whether you adjust, pivot, or return to the Idea stage.
讓答案決定你要「微調、pivot、還是回到點子階段」。
新字：adjust, pivot, return to
Chapter 5 — Launch Stage
第五章：發布階段
If the MVP stage was about proving your product deserves to exist, the Launch stage is about proving your business deserves to grow.
如果 MVP 階段是「證明你的產品值得存在」，發布階段就是「證明你的事業值得成長」。
新字：deserve, prove
Launch stage goals
發布階段目標
In the Launch stage, startup founders must turn early traction into a repeatable, sustainable growth engine. Beyond making your product production-ready, you also must harden the infrastructure underneath it while simultaneously building an actual company around your product.
Startups are naturally founder-centric during the Idea and MVP stages because you need the full situational awareness and tight feedback loops. Now, though, founders who still try to personally hold every thread become a Launch stage bottleneck. The goal isn't to remove yourself from the company, but to build operational systems that free your attention for the decisions only a founder can make.
在 Idea 和 MVP 階段，新創天然以創辦人為中心，因為你需要完整的全局意識（situational awareness）與緊密的回饋迴路。但現在，仍然想要親手抓住每一條線的創辦人，會變成發布階段的瓶頸。目標不是「把你自己從公司移除」，而是建出能釋放你注意力的營運系統，讓你能專注做只有創辦人能做的決策。
新字：founder-centric, situational awareness, thread, bottleneck, free your attention
Launch stage exit criteria
發布階段離場條件
The Launch stage exit condition has three elements:
發布階段的離場條件有三個元素：
1. Growth is repeatable and channel-driven. You're not just retaining users, you're acquiring them predictably through specific channels with understood unit economics: CAC, LTV, and payback period are numbers you know and can defend.
1. 成長是可重複的、由渠道驅動的。你不只是在留存使用者，你能透過特定渠道可預測地獲取他們，而且 unit economics 你都懂：CAC（獲客成本）、LTV（終身價值）、payback period（回收期）都是你知道而且能 defend 的數字。
新字：channel-driven, acquire, unit economics, CAC, LTV, payback period, defend
2. The product can handle production workloads. Infrastructure is hardened, security and compliance are in order, and reliability holds under real production conditions (not just the conditions you tested for).
2. 產品能扛 production 工作量。基礎設施已硬化、資安與合規上軌道、可靠性在真實 production 條件下站得住（不只是你測過的那些情境）。
新字：workload, compliance, reliability, hold under
3. Operations run without founder bottlenecks. Processes exist and automation is in place. You are no longer the person personally handling support, triage, sprint planning, or reporting.
Finding product-market fit is the hardest problem in the early startup lifecycle. Now, the founder's challenge becomes keeping it. The Launch stage is where companies that found real product traction may still fall apart if the organization that surrounds and supports the product can't keep up. These are the failure modes to watch for.
The challenge: The MVP codebase built for speed and validation ran well enough to prove the product worked, but production traffic, new features, and growing complexity are now exposing the shortcuts.
挑戰所在：當初為了速度與驗證蓋的 MVP 程式碼庫，跑得夠好到證明產品能用。但現在 production 流量、新功能、不斷增加的複雜度，把那些抄過的捷徑一個一個暴露出來。
新字：come due, shortcut, expose, complexity
文化脈絡
come due：金融用語，「到期」（如帳單、貸款到期）。technical debt 借用金融比喻，所以 comes due 是承接這個比喻。
At MVP, accumulating some technical debt was a reasonable tradeoff for velocity. In the Launch phase, that debt starts accruing interest, and the longer it goes unaddressed, the more expensive it is to fix.
The solution consists of a systematic architectural audit to identify structural weaknesses, targeted refactoring to address the worst of them, and a meaningful expansion of test coverage so that the next round of feature work doesn't reintroduce the same problems.
新字：systematic, architectural audit, structural weakness, targeted, refactoring, test coverage, reintroduce
The founder becomes the bottleneck
創辦人變成瓶頸
The challenge: At MVP, the founder being in every loop was an asset. At Launch, as support volume grows, product decisions stack up, and operational complexity multiplies, that same instinct becomes the constraint.
新字：asset, support volume, stack up, multiply, instinct, constraint
The transition from doing the work to designing the systems that do the work is one of the hardest shifts in the startup lifecycle. Because there's rarely a clear moment when it happens, the risk is to miss it entirely and stay in builder mode while the organization stalls around you. Telltale signs that this is happening include decisions that should take an hour now take a week for you to get around to them, support requests that pile up because only you know the answer, and operational tasks that only happen when you personally remember to do them.
The remedy is an all-out audit of everything you're personally handling, from the tiniest task to the most high-stakes decisions, in order to identify what can be systematized, what can be delegated, and what genuinely still merits founder time and attention.
The challenge: Keeping security and compliance measures simple was OK for MVP but now, with real users, real data, and potentially enterprise contracts on the table, it becomes a liability.
At MVP, with a handful of beta users and no sensitive data in production, security vulnerabilities were theoretical risks. The hypothetical, however, becomes very real exposure risk the moment your product enters production with real users depending on it. Furthermore, compliance requirements that didn't apply to a prototype definitely apply the moment you're handling customer data, processing payments, or selling into regulated industries.
新字：handful of, sensitive data, theoretical, hypothetical, exposure risk, regulated industry
The remedy is a systematic security and compliance review before production scale arrives, not after, and treat everything that surfaces as a required remediation—not a suggestion—before the next wave of users arrives.
解藥是：在 production 規模到來「之前」而不是「之後」，做一次系統性的資安與合規審查；浮出來的每一條，都當「必須處理的修補項」而不是「建議」——在下一波使用者來之前清掉。
新字：production scale, surface, remediation, wave of users
Expansion before you're ready
沒準備好就擴張
The challenge: New markets and funding opportunities look like growth opportunities. They can also be where product-market fit goes to die.
挑戰所在：新市場與募資機會看起來像「成長機會」。它們也可能是 product-market fit 的墳場。
新字：expansion, opportunity
The initial traction you've built is real, but it's also specific to your early audience. Expanding too early into a market that's meaningfully different from your original one introduces new user behaviors, compliance requirements, payment infrastructure, and baseline expectations that your product wasn't designed around. Suddenly there are too many new variables and you lose the ability to interpret your own data clearly. You also run the risk of neglecting your original user base while chasing a new and unproven audience.
新字：specific to, expand, baseline expectations, variable, interpret, neglect, user base, chase, unproven
How Claude can help Launch stage founders
Claude 怎麼幫到發布階段創辦人
All three forms of Claude are in full use in the Launch stage, and they support each other: each tool produces outputs that become inputs for the other two. The results compound organically, and a founder using all three tools together gets more than the sum of their parts.
發布階段 Claude 三種介面全開、互相支援：每一個工具產出的東西，會變成另外兩個的輸入。結果有機地複利，三個一起用的創辦人，拿到的比「三者加總」更多。
新字：in full use, support each other, compound, organically, the sum of their parts
This is what makes the ultra-lean startup model structurally possible. When Claude Code builds the product, Claude Cowork builds the company around it, and Claude helps operationalize this product and organizational knowledge, a small team can run like a company nx its size.
這就是讓「超精簡新創模型」結構上可行的原因。當 Claude Code 蓋產品、Claude Cowork 在產品周圍蓋公司、Claude 把產品與組織知識落實成可運作的流程——一個小團隊能跑得像「n 倍規模」的公司。
新字：ultra-lean, structurally, operationalize, organizational knowledge, nx its size
Remediate technical debt before it compounds
在技術債開始複利前清掉
Your MVP codebase works, but it also needs a systematic remediation pass in search of any technical debt that could become a structural liability.
First, use Claude Code to run a full architectural audit: identify where the codebase is brittle, any shortcuts that will become expensive to maintain, and where test coverage is thin enough that the next round of feature work will reintroduce the same problems.
第一步，用 Claude Code 跑完整的架構審計：找出程式碼庫哪裡脆（brittle）、哪些捷徑會變成維護貴的負擔、哪裡測試覆蓋率薄到下一輪功能開發會把舊問題帶回來。
新字：architectural audit, brittle, expensive to maintain, thin
Feed Claude Code's audit findings back to Claude to triage and sequence the remediation work: what needs to be fixed before the next release, what can wait a sprint, and what represents acceptable ongoing debt given your current stage. This is also the moment to document the architectural decisions you made during the MVP stage (the ones that lived in your head because there was no time to write down). Getting them into a CLAUDE.md now ensures that every future Claude Code session starts from a shared understanding of how the system was designed and why.
把 Claude Code 的審計發現餵回 Claude，做分流與排序：哪些必須在下次發版前修、哪些可以等一個 sprint、哪些是當前階段可接受的常駐負債。這也是把 MVP 階段「只活在你腦袋裡因為沒時間寫」的架構決策落字的時候。把它們寫進 CLAUDE.md，能確保未來每個 Claude Code session 都從「系統怎麼設計、為什麼這麼設計」的共同理解開始。
Exercise: Direct Claude Code to audit your MVP codebase and produce a prioritized list of structural weaknesses, test coverage gaps, and refactoring candidates. Then feed that list to Claude and ask it to sequence the remediation work across your several sprints: any significant issues that you need to address first, things that can be handled in parallel with feature development, and things that can wait.
練習：指揮 Claude Code 審計 MVP 程式碼庫，產出一份排序過的清單：結構弱點、測試覆蓋缺口、refactoring 候選。然後把這份清單給 Claude，請它把修補工作排進接下來幾個 sprint：先處理的重大問題、可以跟新功能開發並行的、可以等的。
新字：prioritized, gap, candidate, in parallel
Build the systems that replace founder attention
蓋出能取代創辦人注意力的系統
Building the operational systems that free your attention to handle responsibilities only the founder can tackle requires knowing exactly where your attention is going. Use Claude Cowork to run a structured audit of your current operational load, documenting every recurring task, every decision that lands on your desk, and every workflow that only happens because you personally remember to do it. Then have Claude Cowork categorize this inventory into what can be automated entirely, what needs a human but not necessarily you, and what genuinely requires founder judgment.
要蓋出能釋放你注意力、讓你專心處理「只有創辦人能扛的責任」的營運系統，先得確切知道「你的注意力現在花到哪去」。用 Claude Cowork 對你目前的營運負擔做一次結構化審計：每一個重複性任務、每一個落到你桌上的決策、每一個只因「你親自記得才會發生」的工作流，全部記下。然後請 Claude Cowork 把這份清單分類：能完全自動化的、需要人但不必是你的、真正需要創辦人判斷的。
新字：tackle, operational load, recurring task, land on your desk, categorize, inventory
Once the audit is complete, use Claude Cowork to design the workflow logic for the automation candidates: what triggers each workflow, what the decision rules are, what the output looks like, and where it goes when it's done.
審計做完後，用 Claude Cowork 為自動化候選項設計工作流邏輯：每個工作流由什麼觸發、決策規則是什麼、輸出長什麼樣、做完去哪裡。
新字：workflow logic, trigger, decision rule, output
Make security and compliance a product workstream
把資安與合規變成產品工作流的一條
Use Claude Code to surface code-level issues that frequently come up in SOC 2, GDPR, or HIPAA audits and standards that your target market requires. This will surface both vulnerabilities and compliance gaps. Feed those findings to Claude to help you prioritize the remediation work and design the controls, audit logging, and access management that enterprise buyers will ask for before they sign. Note: AI scans are an aid but not a substitute for qualified compliance review.
用 Claude Code 浮出 SOC 2、GDPR、HIPAA 審計，以及你的目標市場要求的標準中，常出現的「程式碼層級問題」。這會同時浮出資安漏洞與合規缺口。把這些發現給 Claude，幫你排序修補工作，並設計 controls、審計日誌、存取管理——這些是企業買家簽合約前會問的東西。備註：AI 掃描是輔助，不是合格合規審查的替代品。
Next, build the compliance workstream into your development cycle rather than running it as a one-time project; compliance documentation needs to be continually maintained and updated. For founders approaching enterprise contracts or international markets, this is also the moment where the Claude Code security scan can help you prepare for an independent security assessment.
接著，把合規工作流嵌進你的開發週期，不要把它當一次性專案；合規文件需要持續維護與更新。對準備接企業合約或國際市場的創辦人，這也是 Claude Code 資安掃描能幫你準備「獨立資安評估」的時機。
Exercise: Run a code-level security review with Claude Code oriented to the frameworks your target market requires. Feed the output to Claude and ask it to produce two things: a prioritized security remediation sequence and a list of the documentation and controls you'll need to produce to satisfy a compliance review from a prospective enterprise buyer.
練習：用 Claude Code 做一輪程式碼層級資安審查，導向你目標市場要求的框架。把輸出給 Claude，請它產兩樣：排序好的資安修補序列、以及為滿足「潛在企業買家的合規審查」要準備的文件與 controls 清單。
新字：oriented to, framework, satisfy
Stand up the product management processes you've been skipping
把你一直跳過的產品管理流程立起來
The Launch stage requires a set of lightweight, repeatable processes that can run without requiring founder intervention to trigger or function. Use Claude to design how your product timeline and work cycles will be structured, what a spec needs to include before Claude Code touches a feature, how bug reports get triaged and routed, and what your weekly metrics report covers and how it's distributed.
發布階段需要一組輕量、可重複、不必創辦人介入就能觸發、就能運作的流程。用 Claude 設計：產品時間軸與工作週期怎麼安排、規格在 Claude Code 動到某個功能前要包含什麼、bug 報告怎麼分流與路由、每週指標報告涵蓋什麼、怎麼分送。
Once process design is done, use Claude Cowork to build and run the operational layer: scheduling sprint ceremonies, routing incoming bug reports to the right place, compiling weekly metrics from your connected data sources, and maintaining the feedback loop that keeps user signals flowing into product decisions.
流程設計做完後，用 Claude Cowork 蓋並跑營運層：排 sprint 儀式、把進來的 bug 報告路由到對的地方、從你串好的資料源編每週指標、維護「讓使用者訊號流進產品決策」的回饋迴路。
Exercise: Ask Claude to design a lightweight product management operating system: a defined sprint cadence, a minimum spec template, a bug triage decision tree, and a weekly metrics brief that pulls from your actual data sources. Then set up Claude Cowork to implement and run the system's recurring operational elements, like scheduling, routing, and report compilation, to happen on schedule without you.
練習：請 Claude 設計一套輕量產品管理 operating system：固定的 sprint 節奏、最小規格模板、bug 分流決策樹、從實際資料源拉的每週指標 brief。然後設定 Claude Cowork 實作並跑該系統的重複營運元素——排程、路由、報告編譯——按時自動發生，不需要你。
During the Scale phase, the founder's role re-centers from builder to public-facing executive. The product is still central, but your personal day-to-day work becomes increasingly about the company itself. Your attention must expand to new Scale-stage activities like analyst briefings and IPO roadshows even as you strive to maintain the lean, AI-centered structural advantage.
在規模化階段，創辦人的角色從「builder」重新對焦到「對外的高階主管」。產品仍是核心，但你個人每天的工作會越來越圍繞「公司本身」。你的注意力必須擴張到 Scale 階段的新活動，例如 analyst briefing（分析師簡報）與 IPO roadshow（上市路演）；同時你還要設法維持那個「精簡、以 AI 為中心」的結構優勢。
The work of scaling technical infrastructure keeps on going, and is now joined by the work of scaling the organization itself and maturing it into a business.
擴大技術基礎設施的工作繼續進行，同時加入兩個新工作：擴大組織本身、把它養成一間真正的公司。
新字：keep on going, mature into
At the scale stage you're looking at going from thousands of users to millions, and from one market to many. At every prior stage, growth was something you could feel your way through by being close to users and adjusting course based on data from tight feedback loops plus a healthy dose of founder instinct. Now, though, the goal is to build systematic growth that's sustained by mature organizational operations.
新字：prior, feel your way through, adjust course, healthy dose, instinct, systematic, sustain
For an AI-native startup, your goal should be to build a defensible moat through accumulated depth, stemming from the expertise you've built into your product, your product's depth of integration with the other tools and platforms your users rely on, and the proprietary system data and workflows. The founders who've been building consistently in one direction, on consistent infrastructure, now have something genuinely hard to replicate.
對 AI 原生新創而言，目標是透過「累積出來的深度」建出可防禦的護城河（moat）：來自你建進產品的領域專業、產品跟使用者依賴的其他工具/平台的整合深度、以及專屬的系統資料與工作流。一路在同一個方向、同一套基礎設施上持續建造的創辦人，現在手上有「真的難以複製的東西」。
At this stage, public investors, analysts, regulators, enterprise procurement teams, and acquirers apply greater pressure–along with greater skepticism–because the stakes are higher now. Your product and org have to withstand external scrutiny: not just the capabilities of what you've built, but the governance, compliance posture, financial controls, and strategic narrative that surround it.
The exit condition at Scale is no longer a single milestone but a threshold event: the company is sustainable even as the founder is, increasingly, not directly running day-to-day operations. You've demonstrated systematic growth; built organizational governance and compliance infrastructure that satisfies the most demanding external reviewers; and have a solid answer to the question, "If a well-funded incumbent copied your product today, would your users stay?"
In practice, this threshold will typically take one of three forms: sustainable profitability at a scale that no longer requires external capital, IPO-readiness, or acquisition. All three require that your growth is systematic and auditable, your product moat stands up under scrutiny, and your organization is operationally mature and sustainable.
新字：in practice, sustainable profitability, external capital, IPO-readiness, acquisition, auditable, stand up under scrutiny
When this is true, congratulations are in order: your startup has gone from being a bet to being a business.
當這些都成立，恭喜：你的新創已經從「一場賭注」變成「一門生意」。
新字：congratulations are in order, bet, business
Scale stage challenges
規模化階段的挑戰
Delegating the operational layer. The challenge: Scale-stage operational systems have to run reliably and sustainably without being babysat. For a founder who has been hands-on since day one, that transition can be as much a psychological challenge as a structural one.
Your Launch stage work was creating the systems; in the Scale phase, it becomes (1) maturing these systems until they are fully trustworthy and (2) then actually trusting them.
This is harder than it sounds. Even if you're a founder who delegates well it's not always obvious what to hand off and what to keep on your plate. Hand off too much, too fast—especially to AI-automated systems—and critical decisions get made without crucial context that only the founder can provide. Hold on too long, though, and you can become a bottleneck.
這比聽起來難。就算你是個善於委派的創辦人，「什麼該交出去、什麼該留在自己盤子上」並不總是一目瞭然。交太多太快——尤其是交給 AI 自動化系統——關鍵決策會在「只有創辦人能提供的關鍵脈絡」缺席的情況下做出。但抓太久不放，你又會變成瓶頸。
新字：hand off, on your plate, hold on, bottleneck
文化脈絡
on your plate：「你盤子上」，引申「歸你處理的事」。
The fundamental challenge here is identifying the institutional knowledge that lives only in the founder's head or undocumented workflows, and then codifying it into systems that are documented, auditable and transferable.
The challenge: Customers no longer evaluate only your product; they want to know that your organization can be a dependable infrastructure partner.
挑戰所在：客戶不再只評估你的產品；他們想知道「你的組織能不能當一個可靠的基礎設施夥伴」。
新字：evaluate, dependable, infrastructure partner
Technical challenges during the first three startup stages centered on the codebase: building the right solution without accruing technical debt and then hardening security and compliance for real users. Having reached the Scale phase, the challenge now becomes everything built around the codebase; creating the support infrastructure, documentation, and reliability guarantees that signal maturity.
新字：center on, harden, support infrastructure, reliability guarantee, signal maturity
Larger-scale customers and institutional buyers signing multi-year contracts want these before they'll sign, and they'll also hold you to them once they do. The same AI infrastructure that got you this far, though, helps you build dedicated support functions with defined response times and documentation that a new customer's engineering team can actually use.
大型客戶與機構買家簽多年合約前會要這些；簽完還會用它們究責。但同一套帶你走到這一步的 AI 基礎設施，能幫你建出「有明確回應時間的專責支援職能」、以及「新客戶工程團隊真的用得上」的文件。
新字：institutional buyer, multi-year contract, hold you to, dedicated, response time
Scaling organizational functions
擴大組織職能
The challenge: A Scale-stage company generally needs organizational infrastructure like hiring, payroll, accounting, and legal operations, regardless of how many people are running it.
新字：organizational function, hiring, payroll, accounting, legal operations, regardless of
At Launch, systematizing operations meant automating the workflows consuming founder attention. A Scale-stage startup now needs to grow an even broader, and in some ways more consequential, array of operational functions such as financial reporting, compliance monitoring, contract management, and customer support, to name a few.
Idea, MVP, and Launch stage growth often originates from founder-led selling, from a well-timed Product Hunt post to personal relationships with early customers. Organic growth like this works only to a certain point, though, and most startups hit this limit in the Scale phase. Signs include flattening user curves, rising customer acquisition costs, and a pipeline that only moves when the founder is personally involved.
Scale-stage growth requires building a dedicated growth engine to reach new and broader audiences for your product. Most startup founders, though, probably have never had to run things like marketing, sales, and analyst relations programs before. A legit GTM motion requires not just establishing new systems and processes, but also creating a brand voice and story for how you want to talk about your product. Because, at this stage in the startup lifecycle, you're going to need one to reach not only individual new users, but also entire target audiences like investors and enterprise buyers.
analyst relations：跟產業分析機構（Gartner、Forrester、IDC）打交道的職能，影響企業客戶選擇。motion：B2B 用語，「一整套銷售動作模式」（例：product-led growth motion vs enterprise sales motion）。
Fortunately, the GTM function doesn't have to be large to be effective, and the same AI infrastructure that built the product can bootstrap bringing it to market.
好消息是：GTM 職能不必很大才能有效，蓋出產品的同一套 AI 基礎設施，能 bootstrap「把它推到市場」這件事。
新字：effective, bootstrap
How Claude can help Scale stage founders
Claude 怎麼幫到規模化階段創辦人
Early startup stages use Claude as foundational infrastructure for the product itself: a research partner for validating the idea, the engineering team that designs and builds the prototype, and the AI operational layer that makes a single-founder startup possible. AI-native startup founders who reach the Scale stage can now use Claude, Claude Code, and Claude Cowork to keep scaling the same way they built.
早期階段，Claude 是「產品本身」的基礎設施：驗證點子的研究夥伴、設計與建造原型的工程團隊、讓「單一創辦人新創」可能的 AI 營運層。走到 Scale 階段的 AI 原生新創創辦人，現在能繼續用 Claude、Claude Code、Claude Cowork，以「蓋它的同一種方式」繼續擴大規模。
新字：foundational, single-founder
Handing off day-to-day tasks to Claude Cowork
把日常任務交給 Claude Cowork
Start the Scale stage with a clear-eyed view of where you most need to invest your time and attention now, which can be a challenge for first time founders who've never built a business before. Claude can help by building the list of things only you should be doing at this stage, which could include things like product narrative decisions, board relationships, enterprise deals, and founder-to-founder conversations. Anything not on that list is a candidate for delegation or Claude Cowork automation.
進 Scale 階段時，先用清楚的眼睛看「現在我的時間與注意力最需要投在哪」。對從沒蓋過公司的首次創辦人來說，這本身就是挑戰。Claude 能幫忙做「現階段只有你能做」的清單：產品敘事決策、董事會關係、企業合約、創辦人之間的對話。不在這份清單上的東西，都是委派或 Claude Cowork 自動化的候選。
新字：clear-eyed, narrative, board relationships, founder-to-founder, candidate for, delegation
Exercise: Use Claude to produce a bottleneck map of your current operational layer: every workflow, decision, and approval currently routed through you. Now, ask Claude to extrapolate what happens to each one when you're unavailable for a week. The workflows that stall are the ones where you are still hands-on enough to derail progress.
練習：用 Claude 畫一張目前營運層的「瓶頸地圖」：所有目前路由經過你的工作流、決策、簽核。然後請 Claude 推斷「你消失一週」時每一個會怎樣。會卡住的那些就是「你還插太深、足以讓進度脫軌」的工作流。
How do these map to the inventory of founder priorities and responsibilities you made with Claude?
這些怎麼對應到你跟 Claude 一起做的「創辦人優先序與責任」清單？
新字：map to, inventory, priority, responsibility
Next, it's time to pressure-test that the systems you've already built are actually ready to scale with your business as it grows.
接著，壓力測試你已經蓋出的系統，是否真的準備好隨業務成長一起擴大。
新字：pressure-test, scale with
Exercise: Use Claude to map your current workflows, and then ask it what happens to each one when you're unavailable for a week. The workflows that stall are the ones where handoff criteria, escalation paths, or exception handling still need tightening. Claude can help analyze the failure points and recommend appropriate fixes so you can update or replace Claude Cowork automations as necessary.
練習：用 Claude 畫出目前的工作流，然後問它「你消失一週」時每一個會怎樣。會卡住的那些就是 handoff criteria（交接標準）、escalation path（升級路徑）、或例外處理還需要收緊的地方。Claude 能幫你分析失敗點、建議合適修補，讓你按需要更新或替換 Claude Cowork 自動化。
新字：handoff criteria, escalation path, exception handling, tighten, failure point
Scale technical operations into enterprise-grade infrastructure
把技術營運擴大到企業級基礎設施
As you scale, buyers need reassurance that your product and your organization can be trusted as long-term infrastructure. Technical work still goes on inside the codebase as always, but now there is technical work around the codebase to handle, too.
新字：enterprise-grade, reassurance, long-term, around the codebase
The first step is to convert institutional knowledge into a system that scales. Use Claude to draft and maintain the written infrastructure that enterprise procurement expects to see, including product documentation, support playbooks, and SLAs.
第一步是把機構知識轉成一個能規模化的系統。用 Claude 起草並維護「企業採購預期會看到」的書面基礎設施：產品文件、支援 playbook、SLA。
新字：convert, written infrastructure, procurement, support playbook, SLA
In parallel, direct Claude Code to audit and harden the codebase against the specific reliability and security standards that enterprise contracts require, and to build out the technical support infrastructure that Discord-based community support never had to provide: logging, monitoring, incident response tooling, and the observability layer that makes SLAs actually enforceable.
同時，指揮 Claude Code 依「企業合約要求的可靠性與資安標準」審計並硬化程式碼庫，並蓋出「Discord 社群型支援從來不需要」的技術支援基礎設施：logging、監控、事件回應工具、以及讓 SLA 真正可執行的 observability 層。
Claude Cowork then runs the operational layer of enterprise support itself: ticket routing, escalation workflows, documentation updates triggered by product changes, renewal tracking, and the reporting cadences that enterprise customer success relies on. Together, these three give a small team the support posture of a much larger organization, which is exactly what signing a multi-year enterprise contract requires you to demonstrate.
Claude Cowork 再跑企業支援的營運層本身：工單路由、升級工作流、由產品變更觸發的文件更新、續約追蹤、企業客戶成功倚賴的報告節奏。三者合起來，讓小團隊展現「比實際大很多的組織」的支援姿態——這正是簽多年企業合約要你展示的東西。
Exercise: Pick your three most demanding prospects or identify three ideal customers for your product that you'd love to sign. Ask Claude to produce a gap analysis: what documentation, SLAs, and support infrastructure would an enterprise procurement team at each of these accounts expect to see before signing a multi-year contract, and where do you currently fall short? Use the output to sequence the technical and documentation work across Claude Code and Claude Cowork.
練習：選你三個最難搞的潛在客戶，或想像三個你最想簽的理想客戶。請 Claude 做一份缺口分析：每一家的企業採購團隊，簽多年合約前會期待看到什麼文件、SLA、支援基礎設施？你目前哪裡不足？用輸出在 Claude Code 與 Claude Cowork 之間排技術與文件工作。
新字：demanding, prospect, ideal customer, gap analysis, fall short
Build a real GTM function
蓋出真正的 GTM 職能
Founder hustle got you this far, but scaling your startup requires creating and implementing an actual go-to-market strategy. AI can help you build, then and run, that complete GTM engine.
Claude can assist with building foundational GTM resources from scratch: market segmentation, messaging architecture, analyst relations strategy, sales playbooks, and the investor-facing metrics narratives that matter once you're talking to public investors, enterprise buyers, and Wall Street analysts. Each of these audiences has its own vocabulary and evaluates you against its own standards; Claude's job is to translate your product's value props into a product marketing approach that's relevant for each audience segment.
Now, Claude Cowork can become your tactical execution layer: content pipelines, outbound sequences, analyst briefing logistics, newsroom and PR cadences, CRM hygiene, pipeline reporting, and the many recurring cycles that turn GTM strategy into actual commercial motion.
Where the GTM motion requires product marketing infrastructure—interactive demo environments, integration documentation, sandbox tenants, API references, technical one-pagers—Claude Code can build it for you. Buyers expect to evaluate your product technically and, in the Scale phase, a Loom video and a sales deck no longer suffice. This is also the infrastructure that lets your GTM motion run asynchronously: a well-built demo environment closes deals while you're in board meetings.
Turning domain expertise and institutional knowledge into AI context
把領域專業與機構知識轉成 AI 脈絡
Many ultra-lean startup founders are building highly specific apps or tools for a real-world problem they experience or observe first-hand in a particular sector. Agentic AI now makes it possible for founders who have never written a line of code to use their domain expertise to build products that solve sophisticated problems. Claude, Claude Code, and Claude Cowork each play a part in converting founder knowledge into compounding product specificity.
許多超精簡新創創辦人，做的是「為特定產業中親身經歷或觀察到的真實問題」的高度特定 app 或工具。Agentic AI 現在讓「從沒寫過一行 code」的創辦人也能用自己的領域專業，做出解決精細問題的產品。Claude、Claude Code、Claude Cowork 各自在「把創辦人知識轉成複利型產品特異性」這件事上扮演角色。
Using Claude to capture, organize, and refine founder knowledge puts domain expertise somewhere the product can reach. Through extended conversations, projects, and memory, a founder can share everything they know—industry jargon, regulatory gotchas, edge cases, frustrations, reasons why the obvious answers to this problem don't work—into a structured, searchable context. Skills can then codify recurring workflows (e.g., "how I audit a commercial lease," "how I triage a patient intake form") into reusable routines Claude runs the same way every time. Over months, this becomes a proprietary knowledge substrate that no generalist AI can match.
用 Claude 捕捉、整理、refine 創辦人知識，把領域專業放到「產品能取得的地方」。透過延伸對話、專案、記憶，創辦人能把所有他知道的東西——產業黑話、法規 gotcha、邊界情況、挫折、為什麼這個問題的明顯解答其實不 work——分享成一個結構化、可搜尋的脈絡。Skills 接著能把重複工作流（例：「我怎麼審商業租約」、「我怎麼為病患入院表分流」）codify 成「Claude 每次都用同樣方法跑」的可重用 routines。幾個月後，這就變成「通用型 AI 比不過的專屬知識基底（substrate）」。
Externalizing your domain knowledge with Claude becomes invaluable for encoding industry-specific edge cases into your product: a generalist AI medical billing tool breaks on 340B drug program claims, for example, but yours has specific logic for them. Claude Code helps you translate common frustrations experienced by other professionals in your field into validation logic, prompt refinements, or an MCP integration with a niche industry system your competitors haven't heard of. As a result, your app or tool's depth and breadth both continually compound in a way that competitors simply can't replicate.
用 Claude 把領域知識外部化，對「把產業特定的邊界情況編碼進產品」變得無價：例如，通用型 AI 醫療帳務工具會在 340B 藥物計畫請款上壞掉，但你的有專門邏輯處理。Claude Code 幫你把「同領域其他專業人員體驗到的常見挫折」翻譯成驗證邏輯、prompt 微調、或跟「對手沒聽過的小眾產業系統」做 MCP 整合。結果是：你的 app 或工具的深度與廣度都持續複利，方式是競爭對手單純複製不了的。
340B drug program：美國聯邦藥物折扣計畫，讓醫療機構以折扣價買藥服務低收入患者。請款規則複雜，是醫療帳務系統的經典坑。
Exercise: Identify one edge case your competitor would definitely get wrong in your vertical. Work with Claude Code to build a dedicated test case for it (not a unit test) based on a scenario you've actually seen. Every time a similar edge case surfaces, add it. Your test suite becomes a map of your moat.
練習：找出你 vertical（垂直領域）裡，競爭對手肯定會搞錯的一個邊界情況。跟 Claude Code 一起，依「你真實看過的情境」做一個專門測試案例（不是單元測試）。每次有類似邊界情況浮出，就加進去。你的 test suite 變成你護城河的地圖。
新字：vertical, dedicated test case, unit test, scenario, test suite
Compound accumulated user data into a defensible advantage
把累積的使用者資料複利成可防禦的優勢
As users interact with your product, they generate behavioral signals (i.e., which outputs they accept and which they reject), which informs the product roadmap. Over time, you'll learn the specific patterns, preferences, and edge cases of your particular user base. This is what we mean by compounding value: each improvement makes the product more useful, which drives more usage, which creates more feedback, which drives more improvement.
This data is time-locked, context-specific, and impossible for a copycat to recreate: you simply can't buy the behavioral fingerprint of thousands of users who've been refining their workflows inside your product.
Claude can help audit whatever user interaction data you've collected, identify the highest-signal behavioral patterns within it, and design the feedback loop that turns ongoing usage into systematic model improvement.
Claude 能審計你已經收集的使用者互動資料、找出其中訊號最強的行為模式、設計能把「持續使用」轉成「系統性模型改進」的回饋迴路。
新字：highest-signal, behavioral pattern, ongoing
Exercise: Feed Claude a summary of your product's interaction data: what you've been collecting, how long you've been collecting it, and what you know about how users engage with your product over time. Ask it to identify the three highest-signal behavioral patterns in that data and design a feedback loop that turns each one into systematic model improvement. Then ask it to help you draft a one-page moat narrative to inform product marketing: the story of how your data flywheel works, how long it's been spinning, and why a well-resourced competitor starting today couldn't replicate it in under two years.
練習：給 Claude 一份你產品互動資料的摘要：你在收什麼、收多久了、你知道使用者隨時間怎麼互動。請它找出資料中訊號最強的三個行為模式、設計能把每一個變成系統性模型改進的回饋迴路。然後請它幫你起草一頁「護城河敘事」用於產品行銷：你的資料 flywheel 怎麼運作、轉了多久、為什麼今天才開始的資金雄厚競爭對手在 2 年內複製不了。
新字：feedback loop, moat narrative, data flywheel, spin, well-resourced
文化脈絡
flywheel：飛輪，Jim Collins 在《Good to Great》提出的比喻——一旦轉起來、慣性會幫你維持。Amazon 因 Jeff Bezos 的「flywheel diagram」聞名。AI 圈的「data flywheel」＝資料越多→模型越好→使用者越多→資料更多。
Create workflow lock-in
創造工作流綁定
Compounding data network effects make your product harder to replicate, but user workflow lock-in makes your product harder to leave. The longer users run your product inside their daily operations, the more deeply it gets embedded in how they actually work. They've built automations on top of it, trained people to use it, and connected it to their data sources and other tools. The prompts they've developed, the workflows they've refined, and the outputs they've standardized have all been shaped around what your product does and how it does it. At this point, switching goes from product decision to full scale operational project.
新字：network effect, lock-in, embed, on top of, standardize, switching
文化脈絡
lock-in：「轉換成本」造成的綁定，越深越難換走。SaaS 商業模式核心之一。
The first step in creating workflow lock-in is asking Claude to map your current customer base by integration depth. For each customer segment, identify what workflows they've built on top of your product and which integrations they depend on. This shows where your product is sticking, and where it needs to go deeper.
創造工作流綁定的第一步是請 Claude 以「整合深度」畫出你目前的客戶基礎。對每個 customer segment，找出他們在你產品上蓋了哪些工作流、依賴哪些整合。這顯示你的產品在哪裡「黏住」、在哪裡需要再深一點。
新字：map by, integration depth, stick
The more integrations you offer, the more surface area a customer has to construct workflows that rely on your product. Claude Code helps you quickly spin up native integrations with the data pipelines, project management tools, and other systems that your target users depend on. Claude Code can also build the APIs, webhooks, and SDKs that let customers not just use your product, but build on top of it—the deepest form of lock-in.
你提供的整合越多，客戶就有越多「能蓋出依賴你產品的工作流」的表面積。Claude Code 幫你快速 spin up 跟目標使用者依賴的資料管線、專案管理工具、其他系統的原生整合。Claude Code 也能蓋出 API、webhook、SDK，讓客戶不只「用」你的產品，還能「在它之上蓋東西」——最深的綁定形式。
新字：surface area, spin up, native integration, webhook, SDK, build on top of
Exercise: Ask Claude to help you build a workflow integration audit for your top ten customers. For each one, document the automations they've built, the integrations they depend on, the team workflows that run through your product, and your estimate of their switching cost. Then ask Claude to identify the patterns across the group: what types of integration create the deepest lock-in for your specific product, and what you could build or enable to deepen integration for customers who are currently at the surface.
練習：請 Claude 幫你為前 10 大客戶做一次工作流整合審計。對每一家，記下他們蓋的自動化、依賴的整合、跑過你產品的團隊工作流、以及你估的「他們的 switching cost」。然後請 Claude 找出整組的模式：對你這個特定產品而言，哪一類整合製造最深 lock-in、對目前還在表層的客戶你能蓋或啟用什麼來加深整合。
In the AI area, the founder's job hasn't changed: find a real problem, build something that solves it, and scale it into a company that matters. What's changed is the path to get there. Across the four stages—Idea, MVP, Launch, and Scale—AI compresses quarters into weeks.
在 AI 領域，創辦人的工作沒變：找一個真實問題、做出能解決它的東西、把它做大成一間有份量的公司。改變的是「抵達那裡的路徑」。橫跨四個階段——Idea、MVP、Launch、Scale——AI 把「季」壓縮成「週」。
新字：matter, quarter, compress
Validation cycles that used to take months now take afternoons. A working prototype no longer requires a co-founder with the right stack; it requires a clear problem and a few focused sessions with a coding agent. Launch readiness compresses from a pre-launch scramble into a continuous workstream. And at scale, the operational weight that used to force early hires into firefighting roles can increasingly be handed off to AI, freeing your team to spend their attention on the judgment calls that become your moat.
Real-world examples of startups built with Claude across various industries and stages.
跨產業、跨階段，用 Claude 打造新創的真實案例。
How three YC startups built their companies with Claude Code：檢視 HumanLayer (F24)、Ambral (W25)、Vulcan Technologies (S25) 如何用 Claude 快速從原型推到市場、用 agentic coding workflow 擴大 AI 驅動平台。
GC AI：創辦人用領域專業，蓋出符合「企業內部法務團隊實際工作方式」的 Claude 驅動法律平台：公司專屬 playbook、跨職能 stakeholder、可變動的風險容忍門檻。
Carta Healthcare：用 Claude 驅動其臨床抽象化平台，每年處理 22,000 件手術案例，把資料抽象化時間降低 66%。
Anything：由 Claude + Agent SDK 驅動，已幫助 150 萬使用者把點子轉成可運作軟體產品，無須寫 code，包含一位「不會工程、自己蓋出、現在已賣完整招募平台」的非技術型創辦人。Anything 的 AI agent 處理整個 build 工作，讓 solopreneur 能 double down 在領域專業上。
Cogent：應用型 AI lab，蓋出能自動化關鍵企業資安任務的 agents。新創用 Claude 作為 agents 的推理層，agents 自動跨整個漏洞生命週期做「調查、優先序排、修補」。
Airtree：用 Claude Cowork 作為其營運基礎設施的核心，把過去散在十幾種工具與團隊裡的資料整起來。現在當一個人用 skills 蓋出工作流自動化，組織裡每個人都能用它去做「to-do list 上一直沒辦的事」。
Duvo：蓋 AI agents 跨 ERPs、supplier portal、試算表、email、甚至電話跑採購、供應鏈、品類管理流程。Duvo 完全建在 Claude 上，用 Agent SDK 編排跨工作流。
Zingera：為居家照護機構打造 24/7 自動化營運的 AI agent 平台。新創用 Claude 的結構化工具呼叫橫跨 EMR 與多個溝通管道編排，用 Claude 的脈絡式推理打造「能給細緻、患者個人化結果」的 agents，而非「pattern-match 到最常見回應」。
Kindora：由一位非營利組織高階主管打造的 AI 驅動平台，用 Claude Sonnet 蓋出「為慈善機構與資助者智慧配對」的急需工具。把幾千筆配對過濾到少數值得追的後，Kindora 的 MCP connector 讓非營利組織直接在 Claude 裡用其開發票工具。
Wordsmith：由律師轉技術長創立，為企業內部法務團隊提供可靠的 AI 驅動法律科技。Claude 是 Wordsmith 合約審閱、協議起草、文件審閱能力的推理引擎，新創的工程團隊用 Claude Code 打造與演化平台本身。
Ch1-2. AI has leveled the playing field around who can launch a startup. The founder's role shifts from individual contributor to orchestrator of agents. Three areas — conversational intelligence, agentic coding, and workflow automation — let a small team operate with leverage far beyond its headcount.
Ch3 Idea. The goal is research-oriented validation, not building. Exit when you can answer yes to three questions: is the problem real and specific, does your solution address the actual problem, do you have enough signal to justify building. Watch for mistaking building for validating, premature scaling, and loss of objectivity from confirmation bias supercharged by AI.
Ch4 MVP. Translate a validated problem into a working product without accruing AI technical debt. Define architecture before building, define and enforce scope, ship a security review before any user touches it, build the measurement framework before launch. PMF signals: Sean Ellis 40% test and the effort shift from pushing to pulling.
Ch5 Launch. Turn early traction into a repeatable, channel-driven growth engine. The founder stops doing the work and starts designing the systems that do the work. Remediate technical debt, stand up product management processes, make security and compliance a continuous workstream.
Ch6 Scale. Build a defensible moat through accumulated depth: domain expertise codified as AI context, compounding behavioral data, and workflow lock-in via integrations. Convert institutional knowledge into systems that are documented, auditable, and transferable.
Ch7. The job hasn't changed: find a real problem, solve it, scale it. What's changed is the path. The bottlenecks are no longer what you can build, but what you choose to build.
句型：長 By 分詞前置（「By eradicating ..., AI has leveled ...」）；對照平行句（「what you can build vs what you choose to build」）；條件強調倒裝（「Hold on too long, though, and you can become a bottleneck」）。