pitch-practice-coach
Skill0 starsChanged 4 months agoMITView on GitHub
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.
In this repository19 other files it gives its agents.
- cap-table-managerSkill
- data-room-builderSkill
- due-diligence-checklistSkill
- financial-plannerSkill
- fundraise-closing-mechanicsSkill
- fundraise-readiness-auditSkill
- fundraise-team-hiringSkill
- fundraising-narrativeSkill
- fundraising-stage-selectorSkill
- investor-pipeline-crmSkill
- investor-targetingSkill
- investor-update-writerSkill
- market-sizingSkill
- pitch-deck-builderSkill
- safe-vs-priced-roundSkill
- series-a-readinessSkill
- term-sheet-explainerSkill
- term-sheet-negotiationSkill
- vc-pitch-emailSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use it after [[pitch-deck-builder]] and before any live meeting, and re-run it before each Tier-1 fund from [[investor-targeting]].
- Distinctive: line 30
Read the [[fundraising-narrative]] aloud.
- Distinctive: line 60
Name the risk first: When the hard question is coming, beat them to it.
- Distinctive: line 69
After each rehearsal, score: Was the opening tight?
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

