本文へ移動
cccskills
無料GitHub で公開

fundraising-email

Use when the user says "write a cold email to investors", "investor outreach email", "how do I cold email a VC", "fundraising cold outreach", "email to angel investor", "reach out to investors", "get a meeting with investors", "intro email for fundraising", "follow up with investor", "warm intro email", or wants to draft any outbound investor communication to generate a first meeting or advance a fundraising conversation.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Overview

Based on "Traction" by Gabriel Weinberg and Justin Mares. The core principle: traction is the only thing that cuts through noise, and fundraising is a distribution problem. Most investor cold emails fail because they lead with the idea instead of the evidence. Weinberg's framework applied to fundraising: treat each investor channel like a traction channel - test messaging, measure response rate, optimize the conversion step (email to meeting), and do not scale outreach until the message converts. An email that does not get a meeting is not a pipeline problem; it is a message problem.

Workflow

Step 1: Qualify the investor before writing anything

Sending a cold email to the wrong investor wastes both parties' time and costs you reputation. Check before writing:

  • Stage fit: do they invest at your stage (pre-seed, seed, Series A)?
  • Sector fit: do they have relevant portfolio companies in [your industry]?
  • Check size: is their typical check size compatible with your round?
  • Geography: do they invest in your market/location?
  • Activity: have they made a new investment in the last 6 months? (Inactive investors do not respond)

Sources to check: their firm's website, Crunchbase, recent tweets or posts, LinkedIn.

If fewer than 3 of these 5 criteria are met, do not send. Find a better-fit investor instead.

Step 2: Find the warm path first

Cold emails convert at 1-5%. Warm intros convert at 20-40%. Before writing a cold email, spend 10 minutes checking whether a warm path exists.

Check:

  • Do any of your existing investors know this person?
  • Do any portfolio companies of theirs know you?
  • Did you meet at a conference, accelerator, or event?
  • Do you have a mutual connection on LinkedIn who would make the intro?

If a warm path exists, use it. Ask your connector for a forwardable email (2-3 sentences you write for them to send). Only fall back to cold outreach when no warm path exists.

Step 3: Write the email using the traction-first structure

Subject line: "[Traction metric] - [your startup] - [round size] raise" Example: "$45K MRR, 3x in 6 months - [Startup] - raising $2M seed"

Body structure (keep to under 150 words):

Sentence 1: The traction hook Lead with your single strongest proof point. One number. No adjectives. "[Your startup] is at $[X] MRR, growing [Y]% month-over-month for [Z] months." Or: "[X] customers, [$Y] in ARR, [Z]% net revenue retention." Or: "[X] pilots completed, [Y]% converted to paid, average ACV $[Z]."

Sentence 2: What you do (one sentence) "We [verb] [specific outcome] for [specific customer segment] by [mechanism]." No jargon. No "AI-powered platform." A 12-year-old should understand what you do.

Sentence 3: Why now / the insight One sentence on what changed or what you know that others do not. This is your Thiel-style secret in one line.

Sentence 4: The ask "I am raising a $[X] [round]. Would a 20-minute call make sense?" Do not ask for "feedback." Do not ask to "share more." Ask for a specific meeting.

Sentence 5: Social proof (optional) "We are backed by [notable investor/accelerator]." Or: "Portfolio companies [X] and [Y] from your portfolio have similar GTM motion." Only include if it is genuinely relevant to them.

Step 4: Personalize one line per investor

Generic emails get deleted. Add one sentence that shows you read their work:

  • Reference a specific investment: "Saw your investment in [portfolio company] - our GTM motion is similar."
  • Reference a specific post or thesis: "Your post on [topic] from [month] shaped how we think about [aspect of our model]."
  • Reference a portfolio gap: "You have strong coverage in [adjacent category] but not yet in [your category]."

This line goes after your traction hook, before "what you do." Do not over-personalize - one genuine line is enough.

Step 5: Track and optimize like a channel

Treat investor outreach as a funnel:

  • Sent - Reply rate (target: 15-25% for well-qualified cold list)
  • Reply - Meeting booked rate (target: 50%+ of replies should convert)
  • Meeting - Second meeting rate (measures pitch quality, not email quality)

Track in a simple spreadsheet: investor name, firm, date sent, reply (Y/N), meeting (Y/N), outcome.

If reply rate is below 10%: the traction metric or the "what you do" sentence is not landing. Rewrite and A/B test with the next 10 sends. If reply rate is good but meeting-to-second-meeting is low: the email is working but the pitch is not. That is a different problem.

Step 6: Follow up once

If no reply in 7 days, send one follow-up. Keep it to 2 sentences:

"Following up on the note below - happy to send a one-pager if that would be easier. Let me know if timing is off and I'll reach back out in a few months."

Do not send a third email. Do not send a deck unsolicited. Move on. Investors remember founders who respect their time.

Anti-Patterns

1. Leading with the idea, not the traction Bad: "We are building an AI-powered platform for the $50B [industry] market..." Good: "$38K MRR, growing 15% month-over-month. We [what you do in one sentence]."

2. Long emails Bad: 400-word email with company history, team bios, and product description. Good: Under 150 words. Every sentence earns its place or gets cut.

3. Asking for feedback instead of a meeting Bad: "I'd love to get your thoughts on what we're building." Good: "Would a 20-minute call make sense this week or next?"

4. Sending the same email to 100 investors at once Bad: Blasting a generic email to a purchased list. Good: Sending to 10-15 well-qualified investors, measuring reply rate, fixing the message before the next batch. Traction first means testing small before scaling.

Quality Checklist

  • Investor is qualified on stage, sector, check size, geography, and activity before sending
  • Warm intro path was checked and ruled out before falling back to cold email
  • Subject line includes a specific traction metric
  • Email is under 150 words
  • First sentence leads with a real number, not a description of the idea
  • Ask is specific: a meeting, not "feedback" or "thoughts"
  • One personalized line references something specific to this investor
  • Outreach is tracked in a spreadsheet with reply rate and meeting rate logged
  • Follow-up is sent once at 7 days and not again after that

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する