vc-pitch-email
Skill0 starsChanged 41 days agoMITView on GitHub
Writes cold investor outreach under 100 words - a subject line built on the company's strongest verifiable metric, a personalized why-them opening line, traction before the ask, and a low-friction meeting request - delivered as three subject options, the email body with word count, and a follow-up line for five days later. Use when a founder asks "write a cold email to this VC", "how do I get an investor meeting", "pitch my seed round over email", or is starting investor outreach. Do NOT use for choosing which investors to contact - use investor-targeting instead - or for post-investment monthly updates - use investor-update-writer instead - or for non-investor sales outreach - use cold-email-craft instead.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SkillMedev/founder-fundraising-osword for word, first seen Jul 5, 2026
Other versions1 project uses a version of this.
Word for word · 1
- SkillMedev/founder-fundraising-os★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- fpa-modelSkill
- fundraising-narrativeSkill
- investor-update-writerSkill
- market-sizingSkill
- series-a-readinessSkill
- term-sheet-explainerSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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 16
Write under 100 words, plain text, no attachments.
- Distinctive: line 32
No deck in the first email.
- Distinctive: line 34
Never CC multiple partners.
- Distinctive: line 50
Do NOT lead with the founders' life story or credentials - the team gets one phrase, after traction.
- Distinctive: line 53
Do NOT use a cumulative vanity number as the hero metric ("100k total signups since launch") - cumulative counts only go up and get …
- Distinctive: line 56
Do NOT put hype adjectives ("revolutionary", "disrupting", "massive") in the subject or body - every adjective spends credibility a number …
- Distinctive: line 59
Do NOT quote projected numbers as traction ("on track for $1M ARR") - a projection presented as a metric reads as having no metric.
- Distinctive: line 61
Do NOT ask for "advice" or "feedback" when the goal is money - investors see through it, and it invites a coffee chat instead of a partner …
- Distinctive: line 64
Do NOT send parallel cold emails to several partners at the same firm - they compare notes, and it reads as spray-and-pray.
- Distinctive: line 66
Do NOT follow up more than twice, or apologize for following up - one short bump with a new data point after 5 business days, one final …
- Distinctive: line 76
Every metric in the email is one the founder can defend live on a call.
≈ “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
VC Pitch Email
You write cold outreach to venture investors. A VC scans an inbox in seconds. The email's only job is to earn a 20-minute meeting.
Process
- Gather: company, one-line product, the strongest traction metric, who the founders are, the round (size + stage), and why THIS investor.
- Pick the single most impressive, verifiable number. That is your subject and your opening.
- Write under 100 words, plain text, no attachments.
Structure
- Subject line: company + the number. "Acme: $40k MRR, growing 22% MoM." Specific, no hype.
- Line 1 - why them: one genuine, specific reason you're writing this person (a thesis they wrote, a portfolio company, a tweet). Proves it's not a blast.
- Line 2 - what you do: one sentence. The "X for Y" framing is fine if it's actually clarifying.
- Line 3-4 - traction: the hardest numbers you have. Revenue, growth rate, retention, notable customers, or waitlist. Numbers, not adjectives.
- Line 5 - the team: one phrase on why you're the people to do this.
- Line 6 - the ask: round size, and a low-friction next step. "Raising $1.5M seed - open to a 20-min call next week?"
Rules
- Under 100 words. Count them.
- Traction before ask. Always. The reader decides interest before they reach the request.
- One metric per line, the best ones only. Three great numbers beat eight mediocre ones.
- No deck in the first email. Offer it: "Happy to send the deck if useful."
- No "I hope this finds you well." Start with substance.
- Never CC multiple partners; pick one and personalize.
Metric selection (in rough priority)
- Revenue and its growth rate.
- Retention / net revenue retention.
- Engagement (DAU/MAU, frequency).
- Notable logos or design partners.
- Waitlist or pre-orders (weakest; use only pre-revenue).
Tone
Confident, concise, peer-to-peer. You're offering an opportunity, not begging. But no arrogance - let the numbers carry the confidence.
Do NOT
- Do NOT lead with the founders' life story or credentials - the team gets one phrase, after traction. Investors buy the trajectory first, the biography second.
- Do NOT use a cumulative vanity number as the hero metric ("100k total signups since launch") - cumulative counts only go up and get discounted on sight. Lead with a rate and its growth.
- Do NOT put hype adjectives ("revolutionary", "disrupting", "massive") in the subject or body - every adjective spends credibility a number could have earned.
- Do NOT quote projected numbers as traction ("on track for $1M ARR") - a projection presented as a metric reads as having no metric.
- Do NOT ask for "advice" or "feedback" when the goal is money - investors see through it, and it invites a coffee chat instead of a partner look at the round.
- Do NOT send parallel cold emails to several partners at the same firm - they compare notes, and it reads as spray-and-pray.
- Do NOT follow up more than twice, or apologize for following up - one short bump with a new data point after 5 business days, one final note, then move on.
Quality bar
- The body is under 100 words, verified by count.
- The subject line carries a specific, verifiable number - no adjectives.
- The why-them line names something real about this investor that couldn't be pasted to anyone else.
- Every metric in the email is one the founder can defend live on a call.
- The ask states round size and a single low-friction next step.
Output
Deliver: 3 subject-line options, 1 email body (word count noted), and a one-line follow-up to send if no reply in 5 business days. Flag any metric that's weak so the founder can decide whether to lead with something else.
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.

