fundraising-email

$npx mdskill add mkurman/zorai/fundraising-email

Crafts concise investor emails for cold outreach, follow-ups, and updates.

  • Generates tailored messages for cold outreach, warm intros, and meeting follow-ups.
  • Depends on startup-context data including metrics, stage, and fundraising status.
  • Classifies email intent to select the appropriate tone and structural template.
  • Outputs short, scannable drafts optimized for investor attention spans.

SKILL.md

.github/skills/fundraising-emailView on GitHub ↗
---
name: fundraising-email
description: 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".
related: [pitch-deck, investor-research]
reads: [startup-context]

tags: [nontechnical, startup-founder-skills, fundraising-email]
---

# 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

1. **Read startup context** — Pull the company narrative, metrics, and fundraising details from `.agents/startup-context.md`.
2. **Determine email type** — Classify as one of the five types below. Each has different structure, tone, and length.
3. **Draft the email** — Follow the type-specific template. Keep it short — investors scan, they don't read.
4. **Add personalization** — Include at least one specific reference to why this investor is a fit (thesis, portfolio company, blog post). Generic emails get ignored.
5. **Review against principles** — Check the draft against the quality checklist. Trim aggressively.
6. **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

1. **Brevity wins** — Investors get 50-100 inbound emails weekly. Over 200 words in a cold email gets skimmed.
2. **Specificity beats superlatives** — "$42K MRR growing 25% MoM" beats "fast-growing revenue".
3. **Social proof early** — Recognizable customer, investor, or accelerator in the first two lines.
4. **One clear CTA** — Every email gets exactly one ask.
5. **Personalization is mandatory** — Reference their thesis, portfolio, or writing. Doubles response rates.
6. **Subject lines are headlines** — Lead with your best metric or most surprising fact.
7. **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 meeting
- `investor-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.

More from mkurman/zorai

SkillDescription
account-management>
agile-scrum>
albumentationsFast image augmentation library (Albumentations). 70+ transforms for classification, segmentation, object detection, keypoints, and pose estimation. Optimized OpenCV-based pipeline with unified API across all CV tasks. Supports images, masks, bounding boxes, and keypoints simultaneously. Note: classic Albumentations (MIT) is no longer maintained; successor AlbumentationsX uses AGPL-3.0. For torchvision-native augmentations, use torchvision.transforms.v2.
aml-complianceAnti-Money Laundering (AML) and Know Your Customer (KYC) compliance workflow. Sanctions screening, PEP detection, transaction monitoring, suspicious activity reporting (SAR), and OFAC compliance.
anki-connectThis skill is for interacting with Anki through AnkiConnect, and should be used whenever a user asks to interact with Anki, including to read or modify decks, notes, cards, models, media, or sync operations.
approval-checkpoint-long-taskCanonical long-task pack for daemon-managed work with deliberate approval checkpoints, status summaries, rollback notes, and mobile-safe governance-aware updates.
auditing-goal-artifactsUse when reviewing recent zorai goal run outputs, closure markers, ledgers, or evidence bundles to judge whether completion is credible or to identify remaining uncertainty.
autogenAutoGen (Microsoft) — multi-agent conversation framework. Agent-to-agent chat, code generation & execution, tool use, group chat, and human-in-the-loop. Build collaborative AI systems with specialized agents.
backtraderPython backtesting framework for trading strategies. Data feeds, brokers, analyzers, and live trading support. Strategy development with commission models, slippage, and signal-based execution.
beautiful-mermaidRender Mermaid diagrams as SVG and PNG using the Beautiful Mermaid library. Use when the user asks to render a Mermaid diagram.