pitch-meeting-coach

Coach a founder for the live VC / investor pitch meeting itself (not the deck — different skill). Covers pre-meeting research (partner background, recent investments, fund-thesis match, time-of-day timing), the 30-minute meeting structure (open, narrative, demo, Q&A, close), live-room dynamics (who in the room, who's the decision-maker, partner vs principal vs analyst signal-reading), the kill-questions ("what would make this not work?", "why now?", "why you?", "what's the failure mode?"), how to read interest signals vs polite-no signals during the meeting, follow-up email sequence in the 48 hours after, and second-meeting / partner-meeting prep. Use when founder says "pitch meeting tomorrow", "VC meeting prep", "first meeting with [Sequoia/a16z/specific firm]", "partner meeting", "term sheet meeting", "investor call". Triggers on phrases like "pitch meeting", "VC meeting", "investor call", "first meeting", "partner meeting", "term sheet meeting", "diligence meeting", "intro meeting investor", "associate screen", "Zoom pitch", "in-person VC meeting".

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "pitch-meeting-coach" with this command: npx skills add charlie-morrison/pitch-meeting-coach

pitch-meeting-coach

Coach a founder for the actual pitch meeting — the live conversation with an investor (associate screen, principal-led intro, partner meeting, or full-partnership pitch). The deck is its own skill (use pitch-deck-coach for that). This skill covers everything around the meeting: the research before, the structure during, the dynamics in the room, the kill-questions to expect, the signals to read, and the follow-up after.

Most founder-pitch failures aren't deck failures. They're meeting failures: founder didn't research the partner / firm thesis, opened with chitchat that ate 8 minutes of a 30-minute meeting, demoed before the narrative landed, gave generic answers to "why now / why you" that any founder would give, missed the polite-no-disguised-as-yes signal, and sent a generic follow-up email. This coach front-loads the meeting craft.

When to engage

Trigger when the founder mentions:

  • Specific upcoming meeting: "pitch tomorrow at 2pm with [firm]", "first meeting with [partner]", "Zoom pitch for [round]"
  • Meeting type: associate screen / first-meeting / second-meeting / partner-meeting / partnership-meeting / IC pitch / term-sheet meeting / intro meeting
  • Meeting format anxiety: "should I demo first or after pitch", "how long is the deck part", "do I show financials in first meeting", "what if the partner is silent"
  • Specific firm/partner research: "what does [partner] care about", "[firm] thesis on [vertical]", "is [partner] writing checks now"
  • Q&A prep: "what hard questions will they ask", "what's the dealbreaker question", "how do I answer 'why won't this work'"
  • Reading the room: "they were polite but I can't tell", "should I follow up if they haven't replied in 5 days"
  • Multi-round dynamics: "second meeting Tuesday", "partner wants me to meet other partners", "they said 'we'll discuss internally'"

Do not engage for: pure deck design (use pitch-deck-coach), specific term-sheet negotiation tactics (use term-sheet-negotiation-coach), pre-seed / friends-and-family round mechanics (use pre-seed-fundraising-coach for the broader fundraise process), or accelerator interview prep (use accelerator-application-coach).

Diagnostic sweep — before the meeting

  1. Meeting type + decision power. What is this meeting?

    • Associate screen (15-30 min, often Zoom): gatekeeper. Goal = pass to a principal/partner. They cannot say yes; they can say no. Optimize for credibility + clarity, not depth.
    • First-meeting with partner (30-45 min): partner's individual yes/no, but they need partnership buy-in for any check. Goal = create a partner who wants to champion you internally.
    • Partner-meeting / partnership (45-60 min, sometimes 90): the IC-equivalent meeting where multiple partners hear the pitch. Decision: yes / further diligence / no. Highest stakes.
    • Diligence meeting (variable): they're already leaning yes; testing specific concerns. Goal = remove blockers, not re-pitch.
    • Term sheet meeting: term sheet exists or imminent; they want comfort or to negotiate. Different mode entirely (negotiation, not pitch).
  2. Firm + partner research depth. Have they actually:

    • Read the partner's last 5-10 portfolio investments and noticed pattern?
    • Read the partner's last 5-10 published essays / podcast interviews / X threads?
    • Identified competing investments they've passed on? (Public on Crunchbase / PitchBook for many firms.)
    • Found one mutual connection willing to give a 2-line readout on the partner's communication style?
  3. Pitch structure rehearsal. Has founder rehearsed the full 30 minutes timed, with a friend playing investor, including hard Q&A? Or are they showing up cold?

  4. Demo readiness. Does the demo work in 60 seconds without internet hiccup? On their laptop, on Zoom screen-share, with backup screen-recording in case live demo breaks?

  5. Numbers fluency. Can the founder answer in <5 seconds: monthly burn, runway, MRR, growth rate (M-o-M and Y-o-Y), CAC, payback, gross margin, current FTE count, key churn metric, last 6 months trajectory? Hesitation here = "not ready to raise".

  6. Bad-news fluency. Can the founder articulate (without flinching): the biggest risk to the company, the worst month in last 12, the customer churn that hurt most, the cofounder issue if any? VCs trust founders who can name the bear case.

Pre-meeting research (24-72h out)

Partner research

  • Last 5 deal announcements: what's the common thesis? Stage? Geography? Sector? Check sizes (TechCrunch, firm site, LinkedIn, Crunchbase).
  • Recent essays / podcast interviews / X threads: what's the partner publicly excited about? What contrarian view do they hold? Quote one specific opinion you can react to (genuinely, not sycophantically) in the meeting.
  • LinkedIn: career arc, prior operating roles. Operator-turned-VC have different energy than career-VC.
  • Reverse: how did the partner get to this firm? Sometimes they came from a portfolio company you can mention.

Firm thesis research

  • Firm site "what we invest in" / "thesis" page. Many firms have explicit stage / sector / check-size guides.
  • Recent fund: when did they close? How much? Pace of deployment matters — early-fund VC has time, late-fund VC is reserve-focused.
  • LP profile if public: corporate-backed funds behave differently from sovereign / endowment LPs (different patience, different exit pressure).

Competitive landscape research

  • Have they invested in / passed on competitors? Public-knowledge passes are surface-able; private passes are not. If they invested in a competitor, the meeting is almost surely a "no" pretending to be a "maybe" — be honest with yourself.
  • If they passed on a strong competitor, find out (via mutuals) what they didn't believe — preempt that objection in the pitch.

Network bridge

  • Mutual connection on LinkedIn? Reach out 24-48h before, ask for a 2-minute readout on the partner's style: "Are they more 'numbers' or 'narrative'? Do they like demos? Do they ask hard questions or stay polite?"
  • Founders in their portfolio you have a relationship with: the partner has likely asked them about you already. Coach those founders on what to say (not coach-as-coaching, just ensure they know the rough product and trajectory).

Meeting structure — the standard 30 minutes

This is the default arc. Adjust for shorter (associate screen) / longer (partner meeting) variants.

Minutes 0-3: open

  • Two minutes of human warm-up. NOT 8 minutes of weather/sports — calibrate. If partner is brief on the warm-up, mirror that.
  • "How would you like to spend our 30 minutes?" — this single question often gets you a useful answer ("Just walk me through what you're building, save 10 min for Q&A"). The partner has done 3 of these meetings today.
  • If partner says nothing structural, you control the time. Default: "I'll spend 12-15 min walking through what we're building, then leave plenty of time for Q&A."

Minutes 3-8: narrative (problem + insight + why now)

  • The strongest opens are NOT "We are a [X] company that [Y]." They are: "Three years ago I was [specific real story]. The pain I noticed was [Z]. What's changed in the world is [specific now-possible thing]. So we built [product]."
  • The narrative arc: pain (specific, scoped, customer-rooted) → insight (what you saw that others didn't) → why now (technological / regulatory / behavioral shift that made this possible / inevitable now) → product (one sentence).
  • Avoid: TAM-first opens, market-data-first opens, "the [vertical] industry is broken" opens, founder-bio-first opens. Lead with the problem, not credentials.

Minutes 8-13: product + demo

  • One-sentence product: "[Product] is [category] for [audience] that [unique-mechanism]."
  • Live demo if possible (60-90 seconds), or screen-recording if live is risky. Demo is not a feature tour — it's a "watch the magic moment happen" with you narrating the customer's POV.
  • If product is pre-launch: show a customer-quote screenshot / Figma flow / waitlist email instead. Don't fake-demo a product that doesn't exist.

Minutes 13-18: traction + go-to-market

  • Show real numbers, not vanity. Charts that show growth (M-o-M, cohort retention, revenue trajectory). Avoid "we have 50,000 users" if 200 are paying.
  • Customer logos / customer quotes (with permission) help.
  • GTM motion: how customers find you today, what's the next channel, what's CAC and LTV math even if early.
  • Be specific about the GTM bet: "We grow via [channel] because [reason]. The unlock to 10x is [specific thing]."

Minutes 18-24: team + ask

  • Team: why this team, what makes you uniquely insightful here. 30-90 seconds. Not a CV recitation.
  • Ask: round size, valuation expectation (if comfortable), milestones the round funds, lead status. Be precise: "$3M seed, $1M committed, looking for lead, deploying 18 months to [specific milestone]."
  • If valuation is awkward: "We're in conversations in the $X-$Y range" rather than dodging.

Minutes 24-30: Q&A

  • Most signal in the meeting comes in Q&A. Partner's questions reveal what they're worried about / interested in.
  • Aim to spend at least 30% of the meeting in Q&A. Founders who race through "the deck" with 4 minutes left for questions are signaling weakness.
  • Close: "What's our process from here? When can I expect to hear back?" Always ask. Partners respect the close; ambiguity rewards no-one.

The kill questions (and how to answer them)

Pre-rehearse answers — concise, honest, structured. Avoid hand-wavy "great question!" filler.

"Why now?"

  • Wrong answer: "AI is hot." / "Everyone is doing this." / "There's a lot of capital."
  • Right answer: 1-2 specific shifts (technological, regulatory, behavioral, distribution) that didn't exist 18 months ago and that uniquely enable this. Be specific: "GPT-4-quality embeddings dropped to $0.0001/k tokens last quarter, which made unit economics work for [our customer]." Or "FTC rule [X] forced [vertical] to standardize [Y], creating a 6-month integration window."

"Why you?"

  • Wrong answer: founder bio recitation; "I'm passionate about [vertical]"; "I have 10 years in [vertical]".
  • Right answer: a specific pattern only you noticed because of your specific past. "I was the head of growth at [company] and watched [pattern]. When I left, I realized [insight] applied here too."

"What would make this not work?"

  • Wrong answer: "Nothing! We're confident!" / "Execution risk."
  • Right answer: name the actual top-2 risks honestly. "The two things that worry me most: (1) if [incumbent] launches [feature], we'd need to [specific differentiation strategy]. (2) if [behavior] doesn't materialize at the rate we expect, we burn 6 months of runway. Here's what we're doing to de-risk both: [specific plan]."

"Who are your competitors?"

  • Wrong answer: "We have no competitors." (Auto-disqualifies. Either ignorant or evasive.)
  • Right answer: name 2-4 real competitors, include adjacent / status-quo / DIY paths, and articulate the wedge: "[Competitor A] has [strength]; we win on [specific dimension] because [structural reason]." Demonstrate competitive map fluency.

"What's your moat / defensibility?"

  • Wrong answer: "First-mover advantage." (Investors hate this.) "We have great UX." (Not a moat.)
  • Right answer: structural advantages that compound. Network effects, proprietary data accumulation, switching costs, regulatory/distribution advantages, learning loops. Be honest if moat is "still building" — describe the path.

"What's the path to $100M ARR / unicorn?"

  • Wrong answer: TAM × penetration math.
  • Right answer: customer-funnel arithmetic. "We acquire customers via [channel] at $X CAC. Average customer pays $Y/year. To $100M ARR we need [N] customers at this ACV, which means [N×CAC] of CAC investment, fueled by [round structure]."

"Tell me about your worst customer / churned customer"

  • Wrong answer: dismiss / blame customer.
  • Right answer: name a real one, what we missed, what we changed.

"What do you do if we don't fund?"

  • Wrong answer: "We'll fail." / "We'll talk to other VCs."
  • Right answer: a credible plan that's NOT raising-from-this-firm-dependent. "We have $X runway, we're profitable on [X subset], we're talking to [3-5 firms in parallel], if no fundraise lands, we cut to [smaller team], focus on [core product]." This shows you're not desperate.

"What's your founder-to-CEO arc?"

  • Honest answer about strengths + gaps. "I'm strong at [product / sales / engineering], gap on [the other thing]. Plan to hire [specific role] in [N months]." Investors know first-time CEOs have gaps. They're checking self-awareness, not infallibility.

Reading the room — interest signals vs polite-no signals

Strong interest signals

  • Partner takes detailed notes (especially numbers, names of customers, names of competitors)
  • Partner asks who else is investing / who else they should talk to
  • Partner asks about lead vs. follow position
  • Partner asks about timeline / process / "what's the next step on your end"
  • Partner introduces you to other team members or schedules follow-up before the meeting ends
  • Partner shares a specific concern + asks how you'd address it (engaging with risk = engaged with deal)
  • Partner extends meeting past scheduled end ("if you have time, can we go 15 more")

Polite-no signals (the meeting is over even if it's still going)

  • Partner agrees with everything (no pushback = no real engagement)
  • "Interesting" / "fascinating" repeated without specific follow-up
  • Partner steers conversation to founder's career / general industry trends instead of this deal
  • Phrases: "we'll discuss internally", "let me see if there's interest from the partnership", "we don't typically [X] but maybe..."
  • Partner offers introductions to other VCs (sometimes a real generosity, often a polite punt)
  • Meeting ends 5-10 minutes early without a clear next step
  • "Send us the deck and we'll circle back" (in 2025-2026 this is usually a no)
  • Days of silence after the meeting (>5 business days without follow-up = lean no)

Mixed / wait-and-see signals

  • "We'd love to see another month/quarter of data"
  • "Let's reconnect in [N months]"
  • "Could you send us a follow-up with [specific data]"
  • "We're early in our diligence on [vertical]" (translation: not yet a thesis)

Format-specific tactics

Zoom pitch

  • Camera at eye level (stack laptop on books). Not chin-cam.
  • Lighting from front, not back. Turn off ceiling lights, use a window or ring light.
  • Mic: separate USB mic, not laptop builtin. Audio quality changes perceived competence.
  • Screen-share rehearsal: practice transition from face to deck to demo and back without 30-second fumbles.
  • Eye contact: look at camera lens during key moments, not at partner's face on screen.
  • Backup: have a phone-tethered hotspot ready in case home internet drops mid-pitch.

In-person partner meeting

  • Arrive 15 minutes early. Don't enter early; sit in lobby and review notes.
  • Dress one notch above partner's expected dress (one notch only — don't show up in a suit at a hoodie firm).
  • Print 2 hard copies of the deck. Almost no one uses them anymore, but offering signals preparation.
  • Water in front of you during meeting. Avoid coffee on empty stomach (jitters during Q&A).
  • After meeting, write down everything specific (questions, follow-ups, what was said) within 30 minutes — your memory degrades fast.

Partner meeting / IC pitch

  • Different partners care about different things. Pre-research each partner who'll be in the room.
  • Some partners are silent throughout but have decision power. Don't dismiss the silent one.
  • Q&A often goes to partners not present in the room (associate-relayed concerns). Surface and address them: "I've heard concerns from your team about [X]. Here's how we think about it..."
  • Decision usually doesn't happen in the meeting. Expect 24-72h for follow-up.

48-hour follow-up email

Send within 24h, not later. Length: ~150-250 words.

What goes in

  • Specific reference to something they said (proves you listened)
  • Direct answer to any open question from the meeting (often partners ask "can you send me [specific data]" — answer in this email)
  • Updated metrics if you have a new data point since the meeting
  • Specific next-step ask: "I'd love to set up a call with [specific other partner you mentioned]" or "When could we talk again?"
  • Named timeline: "We're aiming to close the round by [month]; I'll send updates every 2 weeks until then."

What stays out

  • Apologies for the pitch ("I should have explained X better")
  • New pitch material that wasn't in the meeting
  • Sycophancy ("It was such an honor...")
  • Generic "thanks for your time"

Multi-round dynamics

Second meeting

  • They liked the pitch. Now testing specific theses.
  • Bring updated data (1-2 weeks of metrics, new customer wins, new hire announcements).
  • Expect deeper team meetings, customer calls, technical deep-dives.
  • Decision velocity matters: if the firm hasn't moved to a "yes / no / specific deeper diligence" within 3-4 weeks of first meeting, they're stalling. Politely surface: "We're talking to other firms with similar timelines; can you give me a sense of where we are in your process?"

Partner meeting / partnership pitch

  • Champion partner has set you up; now you must persuade the partnership.
  • Different partners ask different questions. Pre-prep with champion: "Who else will be in the room? What do they each care about?"
  • Show acceleration since first meeting: new logos, growth, hires, customer references willing to take calls.
  • Be ready for "what's your floor on valuation" / "what if we want to lead at $X". Don't negotiate at the meeting unless you've decided your floor in advance.

Term sheet meeting

  • Terms exist or are imminent. The meeting is about comfort + alignment, not pitching.
  • Bring legal counsel pre-briefed (don't bring counsel to the meeting — different conversation).
  • Negotiation is OK but should be specific (board composition, option pool, pro-rata) — not bluster.

Anti-patterns

  • Reading slides verbatim
  • Defensive / argumentative responses to questions
  • Over-explaining / 5-minute monologues
  • Promising features mid-meeting that aren't on the roadmap
  • Disclosing other-VC interest in a way that sounds like ultimatum ("a16z is meeting with us tomorrow") — name names without urgency cues
  • Lying about metrics — the truth surfaces in diligence, the deal dies, your reputation in the partner-network compounds
  • Asking "what would it take to invest" — asks the partner to do your work
  • Following up daily for 7 days after the meeting — anxious-energy signal

Output to founder

After diagnostic, produce:

  1. Meeting-type calibration (associate screen / first / partner / IC / term — adjust strategy)
  2. Partner + firm research findings (what you found, what to reference in the meeting)
  3. 30-minute structure draft (mapped to time, with specific opening line, narrative arc)
  4. Top 6-8 likely questions with rehearsed answers (written down, not just thought-about)
  5. Demo plan (live, recorded, fallback)
  6. Numbers cheat sheet (one page founder can reference: burn, runway, MRR, growth, CAC, etc., with answers ready in <5 seconds)
  7. Bad-news fluency rehearsal (top 2 risks, worst month, biggest churn — practiced)
  8. Signal reading guide (what specific things from this partner / firm history mean strong-yes vs polite-no)
  9. 48-hour follow-up email draft template (to be customized post-meeting)
  10. Format-specific checklist (Zoom: lighting, mic, backup; in-person: arrival, materials)

The pitch meeting is a 30-minute window where the founder either becomes someone the partner wants to spend the next 7-10 years with — or doesn't. Most founders show up under-prepared on the meeting craft (not the deck) and lose deals they could have won. This coach closes that gap.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Research

Graph DB Toolkit

Graph database toolkit for Neo4j and Cypher-based graph analytics. Use when working with knowledge graphs, relationship queries, graph traversal, Neo4j opera...

Registry SourceRecently Updated
Research

Session Log Analyzer

Analyze agent session logs, generate PDF analysis reports, and sync them to Notion. Use when you need to (1) analyze session log files for usage statistics a...

Registry SourceRecently Updated
170Profile unavailable
Research

GOG Sales Analytics

Weekly GOG sales scraper, AI analysis via Gemini, and Feishu Drive report sync. Scrapes all discounted games from GOG catalog, generates markdown insights, a...

Registry SourceRecently Updated
320Profile unavailable
Research

Earnings Call Processor

Automated earnings call transcript processing and analysis. Use when the user provides an earnings call audio file or transcript and wants structured analysi...

Registry SourceRecently Updated
1110Profile unavailable