investor-outreach
affaan-m/everything-claude-code
Draft personalized cold emails, warm intros, and investor updates that are concrete and easy to act on.
What is investor-outreach?
Generates investor-facing communications for fundraising outreach to angels, VCs, and accelerators. Use this when you need to write cold emails, warm intro requests, follow-ups, or investor updates that are personalized, concise, and include proof instead of generic praise.
- Draft cold emails with specific personalization tied to investor thesis or portfolio
- Write warm intro requests with forwardable blurbs under 100 words
- Generate follow-up sequences with new data points at day 4-5 and day 10-12
- Create post-meeting updates with specific discussion points and next steps
- Remove filler language and enforce concrete asks instead of soft closing questions
How to install investor-outreach
npx skills add https://github.com/affaan-m/everything-claude-code --skill investor-outreachHow to use investor-outreach
- 1.Gather personalization context: identify a relevant portfolio company, public thesis, mutual connection, or market fit with the investor
- 2.Provide the core message: what your company does, why now, and one proof point
- 3.Specify the ask: a meeting, intro call, or next concrete step
- 4.If using brand voice, run the brand-voice skill first and reference its VOICE PROFILE
- 5.Review the draft against the quality gate: personalization is genuine, ask is explicit, proof is concrete, and filler language is removed
Use cases
- Sending a cold email to a VC partner referencing their recent portfolio company or public thesis
- Requesting a warm introduction with a concise, forwardable blurb for a connector
- Following up after no response with a new data point or proof point
- Drafting an investor update after a meeting with promised answers and next steps
- Tailoring outreach to an accelerator or strategic investor based on fund focus
- Founders and CEOs fundraising from investors
- Business development leads managing investor outreach campaigns
- Startup operators preparing investor communications during a funding process
investor-outreach FAQ
State that the draft still needs personalization rather than sending generic copy. Gather one or more of: relevant portfolio companies, a public thesis or article, a mutual connection, or clear product-market fit with their focus.
Default cadence is day 0 (initial outbound), day 4-5 (short follow-up with new data), and day 10-12 (final follow-up with clean close). Do not continue nudging after that unless you want a longer sequence.
If your voice matters for the outreach, run brand-voice first and reuse its VOICE PROFILE. This skill keeps the investor-specific structure and ask discipline, not a parallel voice system.
Delete generic phrases like 'I'd love to connect,' 'excited to share,' vague founder adjectives, thesis praise without real tie-in, begging language, and soft closing questions when a direct ask is clearer.
Explain why the intro is a fit, include a forwardable blurb under 100 words, and make it easy for the connector to forward without additional context.
Full instructions (SKILL.md)
Source of truth, from affaan-m/everything-claude-code.
name: investor-outreach description: 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. metadata: origin: ECC
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
Related skills
More from affaan-m/everything-claude-code and the wider catalog.
security-review
Security checklist and patterns for authentication, input validation, secrets, and sensitive features.
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable applications.
coding-standards
Baseline coding conventions for naming, readability, immutability, and quality across projects.
frontend-patterns
React and Next.js patterns for components, state management, performance, and modern frontend practices.
backend-patterns
REST/GraphQL API design, database optimization, and server-side patterns for Node.js, Express, and Next.js.
golang-testing
Go testing patterns: table-driven tests, subtests, benchmarks, fuzzing, and TDD methodology.