Investor Outreach
Handles all the investor communication you'd rather not overthink: cold emails, warm intro requests, follow-ups, and updates during a raise. It enforces personalization rules, kills filler language like "I'd love to connect," and structures everything around a single low-friction ask. The quality gate won't let through generic copy that could go to any investor, and it pushes you to cite real thesis fit or portfolio overlap instead of vague flattery. Includes default follow-up cadence and makes warm intro blurbs short enough that your mutual contact will actually forward them. Works with brand voice if you run that first, otherwise just keeps things tight and proof-driven.
- installs
- 5K
- GitHub stars
- 229.1K
- last updated
- Jul 14, 2026
Install
$ npx -y skills add affaan-m/everything-claude-code --skill investor-outreach --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/affaan-m/everything-claude-code
- Category
- Sales & Marketing
