startup-pitch
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseStartup Pitch
创业项目Pitch
Build investor-ready pitch content in multiple formats. Uses a structured 7-element framework combined with a problem-solution-insight foundation to produce pitch narratives that are clear, compelling, and fundable.
构建符合投资者要求的多格式Pitch内容。采用结构化的7要素框架,结合「问题-解决方案-洞察」的底层逻辑,生成清晰、有吸引力、可获得融资的Pitch叙事。
How It Works
运行逻辑
INTAKE → RESEARCH (2 parallel waves) → PITCH CONSTRUCTION → REVIEW & PRACTICEThe process: understand the company deeply, research the investor audience and competitive framing, then construct the pitch. Typical runtime: 15-20 minutes in Claude Code (parallel agents), 30-40 minutes in Claude.ai (sequential).
INTAKE → RESEARCH (2 parallel waves) → PITCH CONSTRUCTION → REVIEW & PRACTICE流程:深入理解公司情况,调研目标投资者受众和竞争定位,然后构建Pitch。典型耗时:在Claude Code中运行(并行Agent)需15-20分钟,在Claude.ai中运行(串行)需30-40分钟。
Core Philosophy
核心原则
Three principles govern every output this skill produces:
- Clarity over sophistication. "80% accurate and 100% clear beats the reverse." If a grandmother can't understand what you do, investors won't either. Eliminate jargon, acronyms, and marketing language.
- Lead with what's impressive. You earn each additional minute of investor attention. Don't bury traction after 5 sections of problem setup — put the strongest signal right after "what you do."
- Make investors talk. A pitch isn't a monologue. The more investors talk, the more they convince themselves. Structure the narrative to invite conversation, not shut it down.
本Skill生成的所有输出都遵循三大原则:
- 清晰优先于晦涩高深。「80%的准确率+100%的清晰度远好于反过来的情况」。如果你的外婆都听不懂你在做什么,投资者也不会懂。删掉行业黑话、缩写和营销话术。
- **亮点前置。**你需要一步步争取投资者的注意力,不要把业务成果放在5页问题阐述之后,要把最强的信号紧跟在「你做什么」的介绍之后。
- **引导投资者发言。**Pitch不是独角戏,投资者说得越多,就越容易说服自己。叙事结构要引导对话,而不是堵住对话的可能性。
Language
语言设置
Default output language is English. If the user writes in another language or explicitly requests one, use that language for all outputs instead.
默认输出语言为English。如果用户用其他语言提问,或是明确要求其他语言,则所有输出改用对应语言。
Phase 1: Intake
第一阶段:信息收集
Short and focused — 1-2 rounds of questions. The goal is enough context to build a compelling pitch.
简短聚焦,仅需1-2轮提问,目标是获取足够的上下文来构建有吸引力的Pitch。
Recommended Prior Work
推荐前置工作
A pitch built on validated data is significantly stronger than one built on self-reported answers. If you haven't already, consider running startup-design first — it provides market research, competitive analysis, business model, financial projections, and a validation scorecard that become the foundation of a much more credible pitch.
Not required. startup-pitch works standalone. But the quality difference is noticeable.
基于验证过的数据构建的Pitch,远好于基于自报答案的Pitch。如果你还没有做过相关准备,建议先运行startup-design工具:它可以提供市场调研、竞品分析、商业模式、财务预测和验证计分卡,这些内容会成为可信度更高的Pitch的基础。
这不是必需要求,startup-pitch可独立运行,但使用前置数据的质量差异会非常明显。
Check for Prior Work
前置工作检查
Before asking questions, check if prior sessions have been completed. Look for these files in the working directory or subdirectories:
From startup-design:
- — product description and context
00-intake/brief.md - — market size, TAM/SAM/SOM
01-discovery/market-analysis.md - — competitor profiles
01-discovery/competitor-landscape.md - — customer personas, pain points
01-discovery/target-audience.md - — business model summary
02-strategy/lean-canvas.md - — positioning framework
02-strategy/positioning.md - — revenue projections
05-financial/revenue-model.md - — idea scorecard
06-validation/scorecard.md
From startup-competitors:
- — competitive landscape
competitors-report.md - — per-competitor profiles
battle-cards/ - — pricing analysis
pricing-landscape.md
From startup-positioning:
- — positioning document
positioning-doc.md - — positioning statements, elevator pitch
positioning-statement.md - — alternatives map
competitive-alternatives.md - — messaging hierarchy
messaging-implications.md
If these files exist, read them and extract the pitch building blocks: product description, problem/solution, traction, team, market size, business model, positioning, competitive landscape. Tell the user: "I found data from a previous session. I'll use it to build your pitch."
Skip redundant intake questions. Go straight to pitch-specific questions if prior data is sufficient.
提问前,先检查是否已完成过往会话。在工作目录或子目录中查找以下文件:
来自startup-design的文件:
- — 产品描述和上下文
00-intake/brief.md - — 市场规模、TAM/SAM/SOM
01-discovery/market-analysis.md - — 竞品档案
01-discovery/competitor-landscape.md - — 用户画像、痛点
01-discovery/target-audience.md - — 商业模式概要
02-strategy/lean-canvas.md - — 定位框架
02-strategy/positioning.md - — 营收预测
05-financial/revenue-model.md - — 创意计分卡
06-validation/scorecard.md
来自startup-competitors的文件:
- — 竞争格局
competitors-report.md - — 单竞品档案
battle-cards/ - — 定价分析
pricing-landscape.md
来自startup-positioning的文件:
- — 定位文档
positioning-doc.md - — 定位陈述、电梯Pitch
positioning-statement.md - — 替代方案图谱
competitive-alternatives.md - — 信息传递层级
messaging-implications.md
如果存在这些文件,读取并提取Pitch构建模块:产品描述、问题/解决方案、业务成果、团队、市场规模、商业模式、定位、竞争格局。告知用户:「我找到了过往会话的数据,我将基于这些内容为你构建Pitch。」
跳过冗余的信息收集问题,如果前置数据足够,直接进入Pitch专属问题环节。
What to Ask (if no prior data exists)
提问内容(无前置数据时)
Round 1 — The essentials (all required for a pitch):
- What does your company do? (2 sentences max — this becomes the opening)
- What problem are you solving and for whom?
- What's your unique insight? (What do you know that others don't?)
- What traction do you have? (users, revenue, growth rate — with timeframes). If none: say so honestly, we'll build the pitch around insight and team instead.
- What's your business model? (one sentence — how do you make money?)
- Who's on the team? (names, roles, key accomplishments — not titles)
- How much are you raising and what will you do with it?
Round 2 — Sharpening (only if needed):
- What's your market size? (or enough data to calculate it)
- Who are your main competitors? What's your advantage?
- What milestones will you hit in 18-24 months with this funding?
Pitch-specific questions:
- Who is the audience? (VCs, angels, accelerator, demo day, specific fund?)
- What formats do you need? (10-min narrative, 2-min verbal, email pitch, all of them?)
Don't over-interview. A founder with clear answers to Round 1 has enough to build a strong pitch.
第一轮——核心信息(构建Pitch的必填项):
- 你的公司是做什么的?(最多2句话,将作为Pitch开篇)
- 你在为谁解决什么问题?
- 你的独特洞察是什么?(你知道哪些其他人不知道的信息?)
- 你目前取得了哪些业务成果?(用户量、营收、增长率,需附带时间范围)如果还没有成果:如实说明,我们会围绕洞察和团队构建Pitch。
- 你的商业模式是什么?(一句话说明你怎么赚钱)
- 团队成员有哪些?(姓名、角色、核心成就,不是职位头衔)
- 你计划融多少钱,资金用途是什么?
第二轮——优化补充(仅必要时提问):
- 你的市场规模是多少?(或是足够用来计算市场规模的数据)
- 你的主要竞品是谁?你的优势是什么?
- 拿到融资后,你在18-24个月内会达成哪些里程碑?
Pitch专属问题:
- 受众是谁?(VC、天使投资人、加速器、Demo Day、特定基金?)
- 你需要哪些格式的Pitch?(10分钟叙事版、2分钟口述版、邮件Pitch,还是全部?)
不要过度提问,创始人如果能清晰回答第一轮的问题,就足够构建一个优质的Pitch了。
The 2-Sentence Test
两句话测试
Before moving to research, crystallize the company description into exactly 2 sentences + one specific example. This is the foundation of the entire pitch.
Test: send it to a smart friend — could they paraphrase it back correctly? If not, simplify further.
Anti-pattern: "We leverage AI-powered machine learning to optimize cross-functional synergies in the B2B SaaS vertical." Better: "We help sales teams find which leads will actually buy. Our tool analyzes email replies and tells reps exactly who to call next — last month one customer closed 40% more deals."
进入调研阶段前,把公司描述提炼为恰好2句话+1个具体案例,这是整个Pitch的基础。
测试方法:把这句话发给一个聪明的朋友,他们能准确复述出来吗?如果不能,继续简化。
反模式:「我们利用AI-powered machine learning优化B2B SaaS领域的跨职能协同效应。」 正面示例:「我们帮助销售团队找到真正会买单的线索。我们的工具分析邮件回复,明确告诉销售下一步应该联系谁,上个月有一个客户的成交率提升了40%。」
Output
输出
Save to — consolidated context for pitch construction. Project name: kebab-case (e.g., ).
{project-name}/intake.mdai-sales-assistantCreate with: project name, skill name (), start date, language, requested formats, target audience, research mode (Live / Knowledge-Based), and a phase checklist. Update it after each phase completes.
{project-name}/PROGRESS.mdstartup-pitch保存到——Pitch构建的合并上下文。项目名使用短横线命名法(例如)。
{project-name}/intake.mdai-sales-assistant创建,包含:项目名、Skill名()、开始日期、语言、请求的格式、目标受众、调研模式(实时/基于知识库),以及阶段检查清单。每个阶段完成后更新该文件。
{project-name}/PROGRESS.mdstartup-pitchPhase 1.5: Research Depth Assessment
1.5阶段:调研深度评估
After intake, assess market complexity and present the Research Depth recommendation to the user.
Reference: Readfor the complexity scoring matrix, tier definitions, wave configurations, and the user communication template.references/research-scaling.md
信息收集完成后,评估市场复杂度,向用户给出调研深度建议。
参考: 阅读了解复杂度评分矩阵、层级定义、调研波次配置,以及用户沟通模板。references/research-scaling.md
Process
流程
- Score three factors from the intake: market breadth (1-3), known competitors (1-3), geographic scope (1-3)
- Sum the scores (range 3-9) and map to a tier: Light (3-4), Standard (5-7), Deep (8-9)
- Present the Research Depth table to the user (see for the exact template)
research-scaling.md - Wait for user response: light, deep, or ok to accept the recommendation
- Record the selected tier in PROGRESS.md
The selected tier determines the number of agents per wave and search rounds per agent in Phase 2. See for exact wave configurations per tier.
research-scaling.md- 从收集的信息中给三个因素打分:市场广度(1-3分)、已知竞品数量(1-3分)、地域覆盖范围(1-3分)
- 计算总分(范围3-9分),对应到不同层级:Light(3-4分)、Standard(5-7分)、Deep(8-9分)
- 向用户展示调研深度表格(详见的标准模板)
research-scaling.md - 等待用户回复:light、deep,或是ok接受推荐的层级
- 在PROGRESS.md中记录选择的层级
选中的层级将决定第二阶段中每波调研的Agent数量和每个Agent的搜索轮次,详见中每个层级对应的调研波次配置。
research-scaling.mdPhase 2: Research
第二阶段:调研
Two parallel research waves exploring investor audience and competitive/market framing. Together they provide the raw material for a pitch that resonates with the target audience.
两个并行的调研波次,分别调研投资者受众和竞争/市场定位,两者共同为构建能打动目标受众的Pitch提供原始素材。
Environment Detection
环境检测
Check if the tool is available:
Agent- Agent tool available (Claude Code): Spawn all agents within each wave in parallel. This is faster.
- Agent tool NOT available (Claude.ai, web): Execute research sequentially, following the same templates. Same depth, just slower.
检查是否可以使用工具:
Agent- Agent工具可用(Claude Code): 每个波次的所有Agent并行启动,速度更快。
- Agent工具不可用(Claude.ai、网页端): 串行执行调研,遵循相同的模板。深度一致,仅速度更慢。
Web Search
网页搜索
If WebSearch is unavailable, fall back to Knowledge-Based Mode: use training data, mark findings with [Knowledge-Based — verify independently], and reduce confidence ratings by one level. Note the mode in PROGRESS.md.
Reference: Readbefore starting any wave. It defines source quality tiers, cross-referencing rules, and how to handle data gaps.references/research-principles.md
如果WebSearch不可用,回退到知识库模式:使用训练数据,给结论标注**[Knowledge-Based — verify independently]**,并将可信度评级降低一级。在PROGRESS.md中记录该模式。
参考: 启动任何调研波次前阅读,其中定义了来源质量层级、交叉验证规则,以及数据缺口的处理方法。references/research-principles.md
Wave 1: Audience & Narrative Intelligence
第一波调研:受众与叙事洞察
Reference: Readfor agent templates.references/research-wave-1-audience-narrative.md
Two agents (or two sequential blocks):
A1: Investor & Audience Intelligence — Research the target audience (VC firms, angels, accelerators). What are they investing in? What thesis do they follow? What metrics matter at this stage? What are red flags for them? What's the current fundraising climate in this space? Build an audience profile that shapes how the pitch is framed.
A2: Comparable & Narrative Research — Find comparable companies that pitched successfully in this space. What story did they tell? What analogies worked? What "X for Y" framing resonated? What market trends can the pitch ride? Find the narrative hooks — the facts, trends, or insights that make investors lean forward.
Complete Wave 1 before starting Wave 2. Pass key findings (audience expectations, comparable narratives) as context.
参考: 阅读获取Agent模板。references/research-wave-1-audience-narrative.md
两个Agent(或两个串行模块):
A1: Investor & Audience Intelligence —— 调研目标受众(VC机构、天使投资人、加速器)。他们正在投资什么赛道?遵循什么投资逻辑?这个阶段他们看重什么指标?他们忌讳什么?当前这个领域的融资环境如何?构建受众画像,指导Pitch的定位方向。
A2: Comparable & Narrative Research —— 找到同领域成功完成Pitch的可比公司。他们讲了什么故事?哪些类比效果好?哪些「X for Y」的定位获得了认可?Pitch可以借力哪些市场趋势?找到叙事钩子——能让投资者产生兴趣的事实、趋势或洞察。
完成第一波调研后再启动第二波,将核心结论(受众预期、可比叙事)作为上下文传递给第二波。
Wave 2: Competitive Framing & Why Now
第二波调研:竞争定位与时机合理性
Reference: Readfor agent templates.references/research-wave-2-competitive-framing.md
Two agents (or two sequential blocks):
B1: Competitive Framing for Pitch — How competitors position themselves to investors. What narratives have worked for funded competitors? Where are the gaps in their stories that this pitch can exploit? What objections will investors raise based on the competitive landscape? Build a "pitch-aware" competitive frame.
B2: Why Now & Market Timing — Research the timing thesis. What technology shift, behavioral change, or regulatory move makes this the right moment? Find data to support the "why now" — trend charts, adoption curves, policy changes. Assess whether the timing narrative is genuinely strong or forced.
参考: 阅读获取Agent模板。references/research-wave-2-competitive-framing.md
两个Agent(或两个串行模块):
B1: Competitive Framing for Pitch —— 调研竞品如何向投资者定位自己。获得融资的竞品用了哪些有效叙事?他们的故事里有哪些缺口可以被本次Pitch利用?基于竞争格局,投资者会提出哪些异议?构建「适配Pitch」的竞争框架。
B2: Why Now & Market Timing —— 调研时机逻辑。有哪些技术变革、行为变化或监管调整使得现在是做这件事的最佳时机?找到支撑「为什么是现在」的数据:趋势图表、 adoption 曲线、政策变化。评估时机叙事是真实可信的还是强行捏造的。
Post-Research Checkpoint
调研后检查点
After both waves complete, before synthesis, briefly present what the research found to the user: the investor audience profile, the strongest narrative hooks, the competitive framing angle, and the "why now" thesis. Ask: "Does this align with your pitch vision? Anything to adjust before I build the pitch?"
Keep it to one message — this is a quick alignment check, not a full report.
两个波次都完成后,合成内容前,向用户简要展示调研结论:投资者受众画像、最强的叙事钩子、竞争定位角度,以及「为什么是现在」的逻辑。提问:「这和你预期的Pitch方向一致吗?在我构建Pitch前有没有需要调整的地方?」
仅发送一条消息即可,这是快速对齐检查,不是完整报告。
Phase 3: Pitch Construction
第三阶段:Pitch构建
Reference: Readfor the complete framework, including the integration matrix. Reference: Readreferences/pitch-frameworks.mdfor synthesis protocol and output templates.references/research-synthesis.md
Build the pitch using the integrated framework. The construction combines a problem-solution-insight foundation with a structured 7-element approach — see the integration matrix in for how they connect.
pitch-frameworks.md参考: 阅读获取完整框架,包括整合矩阵。 参考: 阅读references/pitch-frameworks.md获取合成规则和输出模板。references/research-synthesis.md
使用整合框架构建Pitch,构建过程结合「问题-解决方案-洞察」的底层逻辑和结构化的7要素方法,两者的关联详见中的整合矩阵。
pitch-frameworks.mdThe Foundation: Problem → Solution → Insight
底层逻辑:问题 → 解决方案 → 洞察
Every pitch must communicate three things clearly:
- Problem — The initial conditions. What's broken? Who suffers?
- Solution — The experiment. What are you building to fix it?
- Insight — Why this will work. What non-obvious truth powers this?
The insight is what separates a pitch from a product description. Without it, you're just another company doing X.
每个Pitch都必须清晰传达三点内容:
- 问题——现状是什么?哪里有问题?谁在受影响?
- 解决方案——你做了什么产品来解决这个问题?
- 洞察——为什么这个方案能成?支撑这个方案的非显而易见的真相是什么?
洞察是Pitch和产品描述的核心区别,没有洞察,你只是无数个做同类产品的公司之一。
The 8 Elements (Pitch Order)
8个要素(Pitch顺序可调整)
The pitch is constructed using these elements, but the ORDER depends on what's most impressive about the company:
- What You Do — 2 sentences + specific example. Impossible to misunderstand.
- [Lead with strength] — Whatever is most impressive goes here: traction, team, insight, or market.
- Traction — Metrics WITH timeframes. "0 to 1,000 users in 8 weeks" not "1,000 users."
- Unique Insight — What do you know that others don't?
- Business Model — One clear model. Not a menu of options.
- Market Size — Bottom-up math. "50,000 customers × $50K ACV = $2.5B" not "$50B TAM."
- Team — Specific accomplishments, not titles.
- The Ask — Amount + milestones + timeframe.
Pitch由这些要素构成,但顺序取决于公司最亮眼的点是什么:
- What You Do——2句话+具体案例,不可能产生误解。
- [亮点前置]——最亮眼的内容放在这里:traction、团队、洞察或是市场。
- Traction——附带时间范围的指标,「8周内从0增长到1,000个用户」,而不是「1,000个用户」。
- Unique Insight——你知道哪些其他人不知道的信息?
- Business Model——单一清晰的模式,不是一堆可选方案。
- Market Size——自下而上的计算,「50,000个客户 × $50K ACV = $2.5B」,而不是「$50B TAM」。
- Team——具体成就,不是职位头衔。
- The Ask——融资金额+里程碑+时间范围。
Pitch Ordering Logic
Pitch排序逻辑
Determine the lead element based on founder strengths:
- Strong traction? → Lead with traction right after "What You Do"
- Impressive team? → Lead with team credentials
- Breakthrough insight? → Lead with the insight that creates an "aha" moment
- Huge market? → Lead with market opportunity
The default order for pre-traction companies: What You Do → Insight → Problem → Solution → Market → Business Model → Team → Ask.
根据创始人的优势决定前置的要素:
- 强traction?→「What You Do」之后立刻放traction
- 团队背景亮眼?→前置团队资历
- 有突破性洞察?→前置能带来「aha」时刻的洞察
- 市场空间巨大?→前置市场机会
还没有traction的公司默认顺序:What You Do → Insight → Problem → Solution → Market → Business Model → Team → Ask。
Construction Rules
构建规则
- No jargon. If the user's pitch contains industry jargon, flag it and provide plain-language alternatives.
- Specific > generic. Replace every vague claim with a specific fact, number, or example.
- Show, don't tell. For the Solution section: describe what a user SEES and DOES — the concrete experience, not abstract features. "The rep opens the dashboard, sees 3 leads highlighted in green with a confidence score. They click one, see the email thread summary, and call. 30 seconds from login to action." This is far more powerful than "Our AI-powered platform surfaces high-intent leads."
- Test the 2-sentence description. If someone hearing it for the first time couldn't explain it back, simplify.
- **无行业黑话。**如果用户的Pitch包含行业黑话,标注出来并提供通俗表述的替代方案。
- **具体 > 通用。**把每个模糊的表述替换成具体的事实、数字或案例。
- **展示,而非告知。**对于解决方案部分:描述用户看到和操作的具体体验,不是抽象的功能。「销售打开仪表盘,看到3个标绿的高置信度线索,点击其中一个就能看到邮件线程摘要,然后拨打电话,从登录到行动仅需30秒。」这比「我们的AI-powered platform挖掘高意向线索」要有说服力得多。
- **测试两句话描述。**如果第一次听到的人没法复述出来,继续简化。
⏸ PAUSE — User Review
⏸ 暂停——用户审核
Present the pitch narrative structure to the user before generating final deliverables. Show: the opening (2 sentences + example), the ordering rationale, and the key narrative arc. Ask: "Does this story feel right? Is the ordering correct? Anything that's missing or should change?"
生成最终交付物前,先向用户展示Pitch叙事结构,包括:开篇(2句话+案例)、排序逻辑、核心叙事弧。提问:「这个故事符合你的预期吗?顺序对吗?有没有遗漏或是需要修改的内容?」
Output Files
输出文件
Every deliverable file must start with a standardized header: followed by . Every deliverable must end with Red Flags, Yellow Flags, and Sources sections.
# {Title}: {product}*Skill: startup-pitch | Generated: {date}*Generate all requested formats. If the user didn't specify, generate all of them.
{project-name}/pitch-full.md- Opening (2 sentences + example)
- Complete narrative following the ordered elements
- Speaker notes for each section (what to emphasize, where to pause, where to invite conversation)
- Transition sentences between sections
- Closing and ask
{project-name}/pitch-5min.md- All 8 elements, trimmed to core claim + one supporting proof point
- Speaker notes focused on pacing
{project-name}/pitch-2min.md- Word-for-word script
- The 2-sentence opener + strongest proof point + insight + ask
- Delivery notes (pace, emphasis, pauses)
{project-name}/pitch-1min.md- Two versions: formal (investor event) and casual (networking)
- What You Do + Insight + Ask only
{project-name}/pitch-email.md- Subject line candidates (3 options)
- Email body: hook → what you do → traction/insight → why now → ask → close
- Follow-up email template
- Personalization notes per investor type
{project-name}/pitch-appendix.md- Top 10 likely investor questions with prepared answers
- Objection handling (competitive threats, market risks, team gaps)
- Known weaknesses with honest answers and mitigation plans
- Financial and competitive backup (if available from prior sessions)
每个交付物文件都必须以标准化头部开头:,接下来是。每个交付物末尾必须包含Red Flags、Yellow Flags和Sources部分。
# {Title}: {product}*Skill: startup-pitch | Generated: {date}*生成所有请求的格式,如果用户没有指定,默认生成全部格式。
{project-name}/pitch-full.md- 开篇(2句话+案例)
- 遵循排序后的要素的完整叙事
- 每个部分的演讲备注(要强调什么、哪里暂停、哪里引导对话)
- 章节之间的过渡句
- 结尾和融资诉求
{project-name}/pitch-5min.md- 包含全部8个要素,精简为核心主张+1个支撑论据
- 聚焦节奏的演讲备注
{project-name}/pitch-2min.md- 逐字稿
- 两句话开篇+最强支撑论据+洞察+融资诉求
- 交付备注(节奏、重音、停顿)
{project-name}/pitch-1min.md- 两个版本:正式版(投资者活动)和 casual 版(社交场合)
- What You Do + Insight + Ask 仅这三部分
{project-name}/pitch-email.md- 候选主题(3个选项)
- 邮件正文:钩子 → 你做什么 → traction/洞察 → 为什么是现在 → 融资诉求 → 结尾
- 跟进邮件模板
- 不同类型投资者的个性化备注
{project-name}/pitch-appendix.md- Top 10 最可能的投资者问题及准备好的答案
- 异议处理(竞争威胁、市场风险、团队缺口)
- 已知劣势及诚实回答和缓解方案
- 财务和竞品支撑材料(如果过往会话中有)
Raw Data
原始数据
Each agent saves its raw output to . Agents must NOT write directly to deliverable paths — raw and synthesized output are separate.
{project-name}/raw/Raw research files:
investor-audience.mdcomparable-narratives.mdcompetitive-framing.mdwhy-now-timing.md
每个Agent的原始输出保存到目录下,Agent不得直接写入交付物路径,原始输出和合成输出是分开的。
{project-name}/raw/原始调研文件:
investor-audience.mdcomparable-narratives.mdcompetitive-framing.mdwhy-now-timing.md
Phase 3.5: Pitch Verification
3.5阶段:Pitch验证
After all pitch deliverables are written, before scoring and review, run a verification pass.
Reference: Readfor the full verification protocol, universal checks, and skill-specific checks.references/verification-agent.md
所有Pitch交付物写完后,评分和审核前,执行一轮验证。
参考: 阅读获取完整验证规则、通用检查项和Skill专属检查项。references/verification-agent.md
Process
流程
- Spawn agent V1: Verification — it reads all deliverable files and checks for: unlabeled claims, internal contradictions, confidence rating consistency, missing data gaps, missing flags, stale data, and duplicate-source false corroboration
- V1 also runs startup-pitch-specific checks: pitch claims vs. source data, cross-format consistency, pitch vs. appendix alignment, honesty checks (traction without timeframes, top-down TAM, titles without accomplishments)
- V1 produces
{project-name}/verification-report.md - If Critical issues found: Pause and present issues to the user. Ask: fix first, or proceed as-is?
- If only Warnings/Info: Show one-line summary and continue to review phase
In Claude.ai or when Agent tool is unavailable, run the verification checks yourself in the main conversation following the same protocol.
- 启动Agent V1: Verification——读取所有交付物文件,检查:未标注的主张、内部矛盾、可信度评级一致性、缺失的数据缺口、缺失的警示、过时数据、重复来源的虚假佐证
- V1同时执行startup-pitch专属检查:Pitch主张 vs 来源数据、跨格式一致性、Pitch vs 附录对齐、诚实性检查(无时间范围的traction、自上而下的TAM、无成就的头衔)
- V1生成
{project-name}/verification-report.md - 如果发现Critical问题: 暂停并向用户展示问题,提问:先修复,还是按当前内容继续?
- 如果只有Warnings/Info: 展示一行摘要,继续进入审核阶段
在Claude.ai或是Agent工具不可用的情况下,在主会话中按照相同规则自行执行验证检查。
Phase 4: Review & Practice
第四阶段:审核与练习
After generating the pitch deliverables, review quality and optionally practice with investor roleplay.
生成Pitch交付物后,审核质量,还可选择进行投资者角色扮演练习。
Step 1: Pitch Scoring Rubric
步骤1:Pitch评分标准
Review the completed pitch against each dimension. Score honestly — a high score on a weak pitch is useless in front of real investors.
Save to :
{project-name}/pitch-scorecard.md| Dimension | Score (1-10) | Rationale |
|---|---|---|
| Clarity — Can someone explain what you do after hearing 2 sentences? | ||
| Strength Sequencing — Is the most impressive element in the first 60 seconds? | ||
| Traction Honesty — Are numbers accurate, timeframed, and real? | ||
| Insight Quality — Is the insight genuinely non-obvious and specific? | ||
| Market Sizing — Is the math bottom-up with clear assumptions? | ||
| Business Model — One model, clearly stated? | ||
| Team Credentials — Specific, verifiable accomplishments? | ||
| Ask Clarity — Amount + milestones + timeframe, stated with confidence? | ||
| Overall |
Verdict:
- 65-80: Investor-ready. Go pitch.
- 50-64: Investor-ready with caveats. Address the weak dimensions first.
- 35-49: Needs work. Iterate on the weakest areas before pitching.
- Below 35: Major gaps. Consider running startup-design first to strengthen the foundation.
For each dimension scoring below 7: explain what's weak and suggest a specific fix.
从各个维度审核完成的Pitch,如实打分——低质量的Pitch打高分在真实投资者面前毫无用处。
保存到:
{project-name}/pitch-scorecard.md| 维度 | 得分(1-10) | 评分理由 |
|---|---|---|
| Clarity——听完2句话后,听众能解释清楚你做什么吗? | ||
| Strength Sequencing——最亮眼的要素有没有放在前60秒? | ||
| Traction Honesty——数字是否准确、有时间范围、真实? | ||
| Insight Quality——洞察是否真的非显而易见且具体? | ||
| Market Sizing——是否是有明确假设的自下而上计算? | ||
| Business Model——是否清晰陈述了单一模式? | ||
| Team Credentials——是否有具体可验证的成就? | ||
| Ask Clarity——是否有信心地陈述了融资金额+里程碑+时间范围? | ||
| Overall |
评级结论:
- 65-80: 符合投资者要求,可以去Pitch。
- 50-64: 符合投资者要求,但有注意事项,先解决薄弱维度再去Pitch。
- 35-49: 需要优化,先迭代薄弱环节再去Pitch。
- 35分以下: 存在重大缺口,建议先运行startup-design夯实基础。
每个得分低于7分的维度:说明薄弱点,并给出具体的修改建议。
Step 2: Iteration Loop
步骤2:迭代循环
Present the scorecard to the user. For each dimension that scored below 7:
- Explain the weakness
- Ask: "How do we fix this? Do you have more data, or should we reframe?"
- Iterate on the relevant pitch sections
- Re-score after changes
向用户展示计分卡,每个得分低于7分的维度:
- 解释薄弱点
- 提问:「我们怎么修复这个问题?你有更多数据吗,还是我们调整表述方式?」
- 迭代对应的Pitch章节
- 修改后重新打分
Step 3: Investor Roleplay (Optional)
步骤3:Investor Roleplay(可选)
After the scorecard review, offer practice: "Would you like to practice the pitch? I can play an investor and give you feedback."
If the user accepts:
Choose an investor persona:
- Angel Investor — Technical, focused on founders + idea. Asks "why you?" and probes domain expertise. Friendly but direct.
- Seed VC — Traction-obsessed, looking for product-market fit signals. Asks about metrics, retention, growth rate. Wants to see momentum.
- Series A VC — Scalability + market size obsessed. Asks about unit economics, competitive moats, expansion path. Thinking about the next round already.
- Accelerator Partner — Looking for coachability + speed of execution. Asks about what you've learned, how fast you ship, what you'd do with mentorship.
Roleplay flow:
- The user delivers their pitch (any format)
- Stay in character as the chosen investor persona
- Ask 3-5 questions that this type of investor would ask — drawn from the appendix but adapted to the persona
- Push back on weak points — investors do this, and the founder needs practice handling it
- After the Q&A, break character and provide feedback:
- What landed well
- Where the investor would have tuned out
- Which answers were strong vs. unconvincing
- Specific suggestions for improvement
Multiple rounds: The user can practice multiple times with different personas. Each round surfaces different weaknesses.
计分卡审核完成后,提供练习选项:「你想要练习Pitch吗?我可以扮演投资者给你反馈。」
如果用户同意:
选择投资者人设:
- Angel Investor——技术导向,关注创始人和创意,提问「为什么是你做这件事」,深挖领域专业度,友好但直接。
- Seed VC——痴迷traction,寻找产品市场匹配的信号,提问指标、留存、增长率,想要看到增长势头。
- Series A VC——痴迷可扩展性和市场规模,提问单位经济学、竞争壁垒、扩张路径,已经在考虑下一轮融资的情况。
- Accelerator Partner——寻找可指导性和执行速度,提问你学到了什么、迭代速度有多快、拿到mentorship后会做什么。
角色扮演流程:
- 用户进行Pitch(任何格式都可)
- 全程保持选定的投资人人设
- 提出3-5个这类投资者会问的问题——从附录中选取并适配人设
- 对薄弱点提出质疑——真实投资者会这么做,创始人需要练习应对
- 问答结束后,跳出人设给出反馈:
- 哪些部分效果好
- 哪个地方投资者会失去兴趣
- 哪些回答很有说服力,哪些没有说服力
- 具体的改进建议
多轮练习: 用户可以选择不同的人设练习多次,每轮会暴露不同的薄弱点。
Step 4: Delivery Tips
步骤4:交付技巧
Include practical delivery advice in the scorecard file:
- The 60-second rule: You earn each additional minute. If the first 60 seconds aren't compelling, the rest doesn't matter.
- Invite conversation. Pause after the insight. If an investor starts talking, let them — they're selling themselves.
- Own the numbers. If asked about a metric, know the exact figure and how you calculated it.
- Handle "I don't know" well. "I don't know, but here's how I'd find out" beats a fabricated answer.
- Practice the 2-sentence opener until it's effortless. This is the single most important part of the pitch.
Update PROGRESS.md — mark all phases complete.
在计分卡文件中加入实用的交付建议:
- 60秒规则: 你需要一步步争取额外的注意力,如果前60秒没有吸引力,后面的内容都没用。
- 引导对话。 讲完洞察后暂停,如果投资者开始说话,让他们说——他们正在说服自己。
- 对数字了如指掌。 如果被问到指标,要知道准确数字和计算方式。
- 坦然应对「I don't know」。「I don't know, but here's how I'd find out」比编一个答案好得多。
- 练习两句话开篇直到可以脱口而出,这是Pitch最重要的部分。
更新PROGRESS.md——标记所有阶段完成。
Honesty Protocol
诚实性规则
Reference: Readfor full protocol and anti-pattern details.references/honesty-protocol.md
A pitch that overpromises destroys founder credibility. Core rules apply (label claims, quantify, declare gaps), plus pitch-specific additions:
- No inflated metrics. If traction is weak, the pitch should acknowledge it and pivot to insight, team, or speed of execution. Fabricated traction will surface in due diligence and kill the deal.
- Honest market sizing. Bottom-up math only. Top-down TAM without justification is a red flag to investors — they've seen it thousands of times.
- Real team credentials. Specific, verifiable accomplishments. "Built X that did Y" — not vague titles or puffed-up bios.
- Flag pitch weaknesses. Every pitch has gaps. Identifying them proactively (and having a plan to address them) is stronger than pretending they don't exist.
- Label claims. Use [Data], [Estimate], [Assumption], [Opinion] tags in supporting materials.
| Anti-Pattern | What It Looks Like | What to Say |
|---|---|---|
| Inflated TAM | "$50B market" with no math | "Show the bottom-up calculation. Investors do the math." |
| Vanity traction | "10K signups" with no activation | "Signups aren't traction. What % actually use the product?" |
| Jargon overload | "AI-powered blockchain synergy" | "What does it actually DO? Say it in words a 10-year-old understands." |
| No insight | Describing a product, not a thesis | "Why will THIS approach work? What do you know that others don't?" |
| Weak team | Titles without achievements | "What have you DONE? Accomplishments, not positions." |
| Vague ask | "We're raising a round" | "How much? For what milestones? In what timeframe?" |
| "No competition" | "We're the first to do this" | "What do customers do TODAY instead? That's your competition." |
参考: 阅读获取完整规则和反模式细节。references/honesty-protocol.md
过度承诺的Pitch会毁掉创始人的可信度,除了通用规则(标注主张、量化、说明缺口),还有Pitch专属的补充规则:
- 不夸大指标。 如果traction不佳,Pitch应该承认这点,转而突出洞察、团队或执行速度。捏造的成果会在尽调中暴露,直接毁掉交易。
- 诚实的市场规模计算。 仅使用自下而上的计算,没有依据的自上而下TAM对投资者来说是红色警示——他们已经看过几千次了。
- 真实的团队资历。 具体可验证的成就,「搭建了X产品,达成了Y成果」,不是模糊的头衔或注水的简历。
- 标注Pitch的薄弱点。 每个Pitch都有缺口,主动说明这些问题(并给出解决方案)比假装不存在要好得多。
- 标注主张类型。 在支撑材料中使用**[Data]、[Estimate]、[Assumption]、[Opinion]**标签。
| 反模式 | 表现 | 正确表述 |
|---|---|---|
| 夸大TAM | 没有计算依据的「$50B market」 | 「展示自下而上的计算过程,投资者自己会算。」 |
| 虚荣traction | 没有激活数据的「10K signups」 | 「注册用户不是traction,实际使用产品的用户占比多少?」 |
| 黑话堆砌 | 「AI-powered blockchain synergy」 | 「它到底是做什么的?用10岁小孩能听懂的话讲。」 |
| 没有洞察 | 只描述产品,没有逻辑 | 「为什么这个方案能成?你知道哪些其他人不知道的信息?」 |
| 团队描述薄弱 | 只有头衔没有成就 | 「你做出过什么成果?要成就,不要职位。」 |
| 模糊的融资诉求 | 「We're raising a round」 | 「融多少钱?用来达成什么里程碑?多长时间?」 |
| 「没有竞品」 | 「We're the first to do this」 | 「现在用户用什么替代方案解决问题?那就是你的竞品。」 |
Reference Files
参考文件
Read only what you need for the current phase.
| File | When to Read | ~Lines | Purpose |
|---|---|---|---|
| Start of session | ~62 | Full honesty protocol with pitch anti-patterns |
| Before starting Phase 2 | ~64 | Source quality, cross-referencing, data gaps |
| When running Wave 1 | ~164 | Agent templates for investor + narrative research |
| When running Wave 2 | ~159 | Agent templates for competitive framing + why now |
| During Phase 3 | ~261 | Complete pitch framework with integration matrix |
| After waves complete | ~417 | Synthesis protocol and output templates |
| After intake, before Phase 2 | ~75 | Complexity scoring, tier definitions, wave configurations |
| After pitch construction | ~80 | Verification protocol, universal + skill-specific checks |
仅阅读当前阶段需要的内容即可。
| 文件 | 阅读时机 | ~行数 | 用途 |
|---|---|---|---|
| 会话开始时 | ~62 | 完整诚实性规则,包含Pitch反模式 |
| 第二阶段开始前 | ~64 | 来源质量、交叉验证、数据缺口处理 |
| 运行第一波调研时 | ~164 | 投资者和叙事调研的Agent模板 |
| 运行第二波调研时 | ~159 | 竞争定位和时机调研的Agent模板 |
| 第三阶段期间 | ~261 | 完整Pitch框架,包含整合矩阵 |
| 调研波次完成后 | ~417 | 合成规则和输出模板 |
| 信息收集后,第二阶段前 | ~75 | 复杂度评分、层级定义、调研波次配置 |
| Pitch构建完成后 | ~80 | 验证规则、通用+Skill专属检查项 |