pitch-practice-coach
Use when a founder needs to rehearse a pitch or prepare for investor questions. Triggers on "practice my pitch", "mock investor meeting", "what will VCs ask me", "help me prep for a partner meeting", "investor Q&A drill", "I freeze on hard questions", "rehearse my deck". Runs realistic rehearsal and objection drills.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- pitch-practice-coach
- description
- Use when a founder needs to rehearse a pitch or prepare for investor questions. Triggers on "practice my pitch", "mock investor meeting", "what will VCs ask me", "help me prep for a partner meeting", "investor Q&A drill", "I freeze on hard questions", "rehearse my deck". Runs realistic rehearsal and objection drills.
03 SKILL.md 正文
Pitch Practice Coach
The deck does not raise the round; the conversation does. Founders lose deals not on the slides but on the third follow-up question, when they get defensive, ramble, or reveal they have not thought it through. This skill rehearses the room until the founder is calm and tight.
When to use this skill
Use it after [[pitch-deck-builder]] and before any live meeting, and re-run it before each Tier-1 fund from [[investor-targeting]]. The warm-up meetings in the pipeline are live practice; this is the dress rehearsal. Run at least three full mock sessions before a Tier-1 partner meeting - one is a read-through, not a rehearsal.
Drill the opening
- Rehearse the first 90 seconds until they are automatic: company, the problem, the insight, the hero metric. Most meetings are won or lost here.
- Practice the two-minute, ten-minute, and thirty-minute versions. You never know how much time you actually get. A partner meeting is typically 45-60 minutes and the presentation rarely survives past minute 10-15 before questions take over - budget roughly two-thirds of prep time for Q&A, not slides.
- Read the [[fundraising-narrative]] aloud. If it does not survive your own ear, it will not survive a partner's.
Run the hard Q&A
Simulate the investor as a skeptic, not a fan. Drill answers to the questions that actually get asked:
- "Why won't [incumbent] just build this?"
- "Walk me through your retention cohorts." (And then: "Why does month 3 dip?")
- "What's your CAC and payback, and how do you know it holds at scale?"
- "Why is now the right time, specifically?"
- "What has to be true for this to be a $1B company?"
- "What's the biggest risk, and what would change your mind?"
- "Why are you raising this much? What does it buy?"
- "What did you get wrong last quarter?"
For each: a crisp 30-second answer, the evidence behind it, and a graceful bridge back to the story. An answer that runs past 60 seconds is a ramble - cut it in rehearsal, because live it will run longer.
The founder must also know their 5-7 core numbers cold - revenue/MRR, growth rate, burn, runway, CAC and payback, retention. A pause of more than about two seconds on any of them reads as not knowing the business; drill until each is instant.
Coach the delivery
- Answer, then support. Lead with the direct answer; do not narrate your way to it. Investors read rambling as not knowing.
- Name the risk first. When the hard question is coming, beat them to it. Self-awareness builds more trust than a flawless story.
- "I don't know" is allowed - paired with how you would find out. Bluffing a number you cannot defend ends the meeting.
- Manage the energy. Land the insight and the ask with conviction; do not trail off or over-apologize.
Feedback loop
After each rehearsal, score: Was the opening tight? Which question caused a flinch? Where did you ramble or get defensive? Drill the worst answer three times before the next live meeting.
Anti-patterns
- Rehearsing only the deck, never the Q&A - the Q&A is the meeting.
- Defensiveness under pushback; investors probe to see how you handle pressure.
- Bluffing a number you cannot back up.
- Memorizing a script so rigid that one interruption derails you.
- Treating one read-through as prep - the flinches only show up under live skeptical questioning, in multiple sessions.
Quality bar
The founder is meeting-ready only when: the 90-second opening lands identically on three consecutive runs; every question in the bank has a direct answer of 30 seconds or less with named evidence; all 5-7 core metrics come back in under two seconds; at least one hard question was answered with a candid "I don't know, here's how I'd find out" without visible flinch; and the last mock session produced no new items for the drill list.
Deliverable
A drilled opening (90-second + scaled versions), a tough-question bank with a crisp answer and evidence for each, a delivery-coaching note on the founder's specific tics, and a ranked list of the answers to drill before the next meeting.
04 同仓库更多 Skills
有氧运动计划
zone-2-cardio-plan
当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练,或提高静息心率、最大摄氧量或耐力时,可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导,不构成医疗建议。请勿用于设计力量或举重训练计划(请使用力量训练计划)、高强度间歇训练 (HIIT) 或循环训练(请使用体能训练和 HIIT 计划),或灵活性/柔韧性训练(请使用灵活性训练计划)。
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.