fundraising-email
Skill331 starsChanged 8 months agoMITView on GitHub
When the user wants to write an email to an investor — cold outreach, warm intro request, follow-up after a meeting, monthly investor update, or thank-you note. Also activates for "intro email", "investor email", "follow up with VC", or "investor update".
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 54
No attachments on first email.
- Distinctive: line 66
Goal: Keep current and prospective investors informed.
- Distinctive: line 76
If invested: genuine thanks, confirm logistics, add to update list.
- Distinctive: line 77
If passed: thank them, leave the door open, ask if they want monthly updates.
- Distinctive: line 92
No NDAs. No reputable investor signs them for startup pitches.
- Distinctive: line 93
Don't email multiple partners at the same firm.
- Distinctive: line 94
Don't follow up more than twice without new information.
- Distinctive: line 95
Don't CC multiple investors on the same email.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Fundraising Email
When to Use
- The founder needs to write a cold outreach email to an investor.
- The founder wants to draft a warm intro request (a "forwardable email").
- The founder needs a follow-up after an investor meeting.
- The founder is writing a monthly investor update.
- The founder wants to send a thank-you or round-closing notification.
Context Required
From startup-context: company one-liner, stage, key traction metrics, fundraising status, and any notable social proof (investors, customers, press).
From the user: email type, recipient (investor name and firm), prior relationship context, and desired outcome (meeting, intro, materials review).
Workflow
- Read startup context — Pull the company narrative, metrics, and fundraising details from
.agents/startup-context.md. - Determine email type — Classify as one of the five types below. Each has different structure, tone, and length.
- Draft the email — Follow the type-specific template. Keep it short — investors scan, they don't read.
- Add personalization — Include at least one specific reference to why this investor is a fit (thesis, portfolio company, blog post). Generic emails get ignored.
- Review against principles — Check the draft against the quality checklist. Trim aggressively.
- Deliver the final draft — Output subject line and email body, ready to copy-paste.
Output Format
**To:** [Investor Name]
**Subject:** [Subject line]
[Email body]For investor updates, output a longer structured email with sections (see type 4 below).
Frameworks & Best Practices
The Five Email Types
1. Cold Outreach
Goal: Get a 30-minute meeting. Length: 5-7 sentences, under 150 words.
- Line 1: Why this investor specifically (1 sentence).
- Lines 2-3: What you do and for whom (no jargon).
- Lines 4-5: Strongest traction proof point — one number that makes them lean in.
- Line 6: Specific, low-commitment ask ("Would you have 30 minutes this week or next?").
- No attachments on first email. Subject line formula:
[Specific hook] — [Company Name](e.g.,"$40K MRR in 6 months, AI contract review — Lexara").
2. Warm Intro Request (The Forwardable Email)
Goal: Make it effortless for your connector to intro you. Two parts:
- Note to connector (2-3 sentences): "Would you be willing to introduce me to [Partner] at [Firm]? Short blurb below you can forward directly."
- Forwardable blurb (4-6 sentences): Written so the connector sends it as-is. Include what the company does, strongest metric, why this firm is relevant, and what you're looking for. If the connector has to rewrite it, they won't send it.
3. Follow-Up After Meeting
Goal: Maintain momentum, deliver materials, set next steps. Length: 4-8 sentences.
- Thank them and reference one specific thing discussed. Attach requested materials. Address any open question. Propose a specific next step with a date. Send within 3 hours — speed signals competence.
4. Monthly Investor Update
Goal: Keep current and prospective investors informed. Length: 300-500 words.
- Highlights: Top 3 wins (metrics-first).
- KPIs: Table with this month, last month, MoM change.
- Challenges: 1-2 honest struggles (invites help; investors respect candor).
- Asks: 1-3 concrete requests (intros to specific customer types, candidates for a role).
- What's Next: Top 2-3 priorities for next month.
- Send on the same day each month. Monthly updates are the #1 way to convert a "not yet" into a future "yes".
5. Thank-You / Round Closing Note
Goal: Maintain the relationship. Length: 3-5 sentences.
- If invested: genuine thanks, confirm logistics, add to update list.
- If passed: thank them, leave the door open, ask if they want monthly updates. Never burn bridges — the investor who passes on seed may lead your Series A.
Core Principles
- Brevity wins — Investors get 50-100 inbound emails weekly. Over 200 words in a cold email gets skimmed.
- Specificity beats superlatives — "$42K MRR growing 25% MoM" beats "fast-growing revenue".
- Social proof early — Recognizable customer, investor, or accelerator in the first two lines.
- One clear CTA — Every email gets exactly one ask.
- Personalization is mandatory — Reference their thesis, portfolio, or writing. Doubles response rates.
- Subject lines are headlines — Lead with your best metric or most surprising fact.
- Send Tuesday-Thursday, 8-10am investor's timezone — Open rates drop on Mondays and Fridays.
What Not to Do
- No "disruptive", "revolutionary", "game-changing", or "the Uber of X".
- No NDAs. No reputable investor signs them for startup pitches.
- Don't email multiple partners at the same firm. They compare notes.
- Don't follow up more than twice without new information.
- Don't CC multiple investors on the same email.
Related Skills
pitch-deck— the email drives the meeting; the deck carries the meetinginvestor-research— research determines who to email and what personalization to use
Examples
Example prompt: "Write a cold email to Sarah Chen at Greylock. We're an AI code review startup with $55K MRR."
Good output:
Subject: $55K MRR — AI code review, 4 enterprise customers — CodeLens
Hi Sarah,
Your investment in Developer Infrastructure at Greylock — particularly the thesis in your "Next Wave of DevTools" post — is why I wanted to reach out to you specifically.
I'm the CEO of CodeLens. We automate code review for enterprise engineering teams using LLMs, catching security vulnerabilities and logic errors that slip past existing tools.
We launched 5 months ago: $55K MRR, 4 enterprise customers (two Fortune 500), growing 30% MoM. We're raising a $3M seed round.
Would you have 30 minutes this week or next?
Example prompt: "Help me write this month's investor update."
Good output approach: Pull metrics from startup context, ask the founder for this month's highlights and challenges, then produce the structured update. Flag any missing or stale KPIs.
Other versions1 project uses a version of this.
Word for word · 1
- Maudeunfledged834/startup-founder-skills★ 8100% 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 repository49 other files it gives its agents.
- accelerator-applicationSkill
- architecture-designSkill
- board-updateSkill
- churn-analysisSkill
- cicd-setupSkill
- code-reviewSkill
- cold-outreachSkill
- community-discoverySkill
- competitive-analysisSkill
- competitor-monitoringSkill
- content-strategySkill
- contract-reviewSkill
- daily-product-digestSkill
- data-roomSkill
- earned-media-outreachSkill
- email-marketingSkill
- employer-brandSkill
- event-hostingSkill
- feedback-synthesisSkill
- founder-thought-leadershipSkill
- interview-kitSkill
- investor-researchSkill
- job-descriptionSkill
- landing-pageSkill
- launch-strategySkill
- lead-scoringSkill
- market-researchSkill
- mvp-scopingSkill
- onboarding-flowSkill
- partnership-outreachSkill
- pitch-deckSkill
- prd-writingSkill
- privacy-policySkill
- process-docsSkill
- proposal-generationSkill
- review-miningSkill
- roadmap-planningSkill
- sales-scriptSkill
- security-reviewSkill
- sentiment-monitoringSkill
- seo-technicalSkill
- soc2-prepSkill
- social-contentSkill
- sourcing-outreachSkill
- startup-contextSkill
- support-docsSkill
- tech-stack-evalSkill
- terms-of-serviceSkill
- user-research-synthesisSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

