investor-outreach
Verifiedby affaan-m · Updated Apr 16, 2026
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
See It In Action
Let me explore the project first to understand the company context, then generate the outreach materials.
Here's the complete follow-up pack.
INVESTOR 1: Priya Sharma — Canopy Seed Fund
Note to David (for the Priya intro)
David — thanks again for coffee yesterday. Here's the blurb for Priya below. Given Canopy's portfolio (Speakeasy, Depot, and the recent API monitoring investment), Layup fits squarely in her infra thesis. We're at $38K MRR with 22% MoM growth and no sales team — she mentioned she likes seeing metrics early, so I've included them. Appreciate you making this intro.
— Alex
Forwardable Blurb (Priya) — 88 words
Layup is an API-first migration engine that lets engineering teams move between cloud services, databases, and internal tools without rewriting integration code. Founded by Alex Reeves (ex-Stripe payments infra) and Jordan Kato (ex-Datadog pipeline). Currently at $38K MRR, growing 22% MoM, with 14 paying customers including Ramp, Vanta, and Replit. 100% logo retention, 138% NRR. Schema-aware diffing catches breaking changes before migrations run — reduces migration time from 6 weeks to 3 days. Raising a $2.5M seed with $800K committed.
Follow-Up Email 1 — Day 4–5 after intro
Subject: Layup — quick context + one question
Hi Priya,
Following up on David's intro. A few concrete data points since Layup maps directly to what Canopy backs with Speakeasy and Depot:
- 14 paying customers, $38K MRR, 22% MoM growth — no sales team
- Ramp is paying $4,200/mo to migrate internal tooling from legacy REST services
- Vanta uses us for SOC 2 compliance data pipeline migrations at $3,800/mo
- 100% logo retention across our 6-month cohort, 138% NRR
We price per migration run, not per seat — usage-based, same model as Speakeasy. Our pipeline sits at $210K ARR in active trials.
Would 25 minutes work this week or next? Happy to walk through the product and how we're thinking about expanding integration coverage from 18 to 40+.
Alex Reeves CEO, Layup | ex-Stripe payments infra
Follow-Up Email 2 — Day 10–12
Subject: Layup — closing the loop
Hi Priya,
Wanted to share one update before I drop off your radar: we closed two new contracts last week, bringing MRR to ~$42K. Both came inbound from teams that hit the same wall — rewriting integration code every time they swap a vendor or internal service.
I know Canopy recently led a round in an API monitoring company. Layup sits one layer deeper — we handle the actual migration when teams act on what monitoring surfaces. Happy to dig into that overlap if it's useful.
If the timing isn't right, no worries at all. Otherwise, I can make any 25-minute slot work.
Alex
INVESTOR 2: Marcus Webb — Angel
Note to David (for the Marcus intro)
David — here's the Marcus blurb. Given his Plaid background, he'll immediately get the API integration pain we solve. Our Ramp and Vanta contracts are in his world. And the "picks and shovels" framing from his recent podcast is basically our pitch — infrastructure tooling that every team migrating services needs. Thanks for connecting us.
— Alex
Forwardable Blurb (Marcus) — 86 words
Layup is an API-first migration engine — engineering teams move between cloud services, databases, and internal tools without rewriting integration code. Built by Alex Reeves (ex-Stripe payments infra) and Jordan Kato (ex-Datadog pipeline). $38K MRR, 22% MoM growth, 14 paying customers including Ramp, Vanta, and Replit. Zero customer churn, 138% net revenue retention. Schema-aware diffing catches breaking changes pre-migration, cutting migration time from 6 weeks to 3 days. Raising a $2.5M seed, $800K committed. Usage-based pricing, no seat licenses.
Follow-Up Email 1 — Day 4–5 after intro
Subject: Layup — migrations infra, ex-Stripe + ex-Datadog team
Hi Marcus,
Following up on David's intro. Your "picks and shovels" framing from your recent podcast is exactly how we think about Layup — we're the infrastructure layer underneath every team that needs to move between services without rewriting integration code.
Given your time at Plaid, you've seen this problem at scale. A few numbers:
- $38K MRR, 22% MoM, no sales team
- Ramp pays $4,200/mo for internal tooling migrations; Vanta pays $3,800/mo for compliance pipeline migrations
- 100% logo retention, 138% NRR
- Schema-aware diffing cuts migration time from 6 weeks to 3 days
We're raising a $2.5M seed with $800K committed. Your check size and focus fit well.
Are you at Founders Summit next week? Would be great to meet in person. Otherwise, happy to do 20 minutes on a call.
Alex Reeves CEO, Layup | ex-Stripe payments infra
Follow-Up Email 2 — Day 10–12
Subject: Layup — one update, then I'll let it rest
Hi Marcus,
Quick update: our pipeline just crossed $210K ARR in active trials, and we signed two new contracts last week. Every deal follows the same pattern — an eng team realizes they're spending 4–6 weeks rewriting integration code for a migration that should take days.
We're at 18 supported integrations and using the seed to get to 40+. The compounding effect is real: each new integration makes existing customers expand (hence 138% NRR).
If the timing works, I'd value 20 minutes — especially given what you built at Plaid around API integrations. If not, no hard feelings.
Alex
Personalization notes — gaps to fill before sending:
- Priya: Her Substack post title about seed-stage dev tools is referenced indirectly but not by name. If you can find the exact title, swap it into Follow-Up 1's opener for a stronger hook.
- Marcus: The podcast title/platform is referenced generically. If you find it, name it directly in Follow-Up 1.
- MRR update in day 10–12 emails: I used ~$42K as a projected number. Replace with actuals when you send.
SKILL.md
Investor Outreach
Write investor communication that is short, concrete, and easy to act on.
When to Activate
- writing a cold email to an investor
- drafting a warm intro request
- sending follow-ups after a meeting or no response
- writing investor updates during a process
- tailoring outreach based on fund thesis or partner fit
Core Rules
- Personalize every outbound message.
- Keep the ask low-friction.
- Use proof instead of adjectives.
- Stay concise.
- Never send copy that could go to any investor.
Voice Handling
If the user's voice matters, run brand-voice first and reuse its VOICE PROFILE.
This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.
Hard Bans
Delete and rewrite any of these:
- "I'd love to connect"
- "excited to share"
- generic thesis praise without a real tie-in
- vague founder adjectives
- begging language
- soft closing questions when a direct ask is clearer
Cold Email Structure
- subject line: short and specific
- opener: why this investor specifically
- pitch: what the company does, why now, and what proof matters
- ask: one concrete next step
- sign-off: name, role, and one credibility anchor if needed
Personalization Sources
Reference one or more of:
- relevant portfolio companies
- a public thesis, talk, post, or article
- a mutual connection
- a clear market or product fit with the investor's focus
If that context is missing, state that the draft still needs personalization instead of pretending it is finished.
Follow-Up Cadence
Default:
- day 0: initial outbound
- day 4 or 5: short follow-up with one new data point
- day 10 to 12: final follow-up with a clean close
Do not keep nudging after that unless the user wants a longer sequence.
Warm Intro Requests
Make life easy for the connector:
- explain why the intro is a fit
- include a forwardable blurb
- keep the forwardable blurb under 100 words
Post-Meeting Updates
Include:
- the specific thing discussed
- the answer or update promised
- one new proof point if available
- the next step
Quality Gate
Before delivering:
- the message is genuinely personalized
- the ask is explicit
- the proof point is concrete
- filler praise and softener language are gone
- word count stays tight
FAQ
What does investor-outreach do?
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
When should I use investor-outreach?
Use it when you need a repeatable workflow that produces text response.
What does investor-outreach output?
In the evaluated run it produced text response.
How do I install or invoke investor-outreach?
npx skills add https://github.com/affaan-m/everything-claude-code --skill investor-outreach
Which agents does investor-outreach support?
Claude Code
What tools, channels, or permissions does investor-outreach need?
It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.
Is investor-outreach safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is investor-outreach different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does investor-outreach outperform not using a skill?
About investor-outreach
When to use investor-outreach
Writing cold emails to angels, VCs, or strategic investors. Preparing warm intro requests and forwardable blurbs. Sending follow-ups or investor updates after meetings.
When investor-outreach is not the right choice
When the task is to actually send emails or manage a CRM workflow. When broad marketing copy is needed instead of personalized investor communication.
What it produces
Produces text response.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill investor-outreachInvoke: Ask Claude Code to use investor-outreach for the task.