Write Investor Outreach
Draft concise, personalized emails and updates for angels, VCs, and accelerators. It crafts cold emails, warm intros, and follow-ups with clear asks and relevant investor-specific details.
affaan-m on GitHub
Curated by PromptsEdge from a public repo · MIT license. All credit goes to the author.
What is this skill?
Write investor communication that is short, concrete, and easy to act on.
When to use
- 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
Install this skill
- 1
Get the skill — it’s free
Use the Get this skill panel. Unlocked skills stay in My skills. - 2
Download or clone the files
Download the zip, or clone the repo and copy theskills/investor-outreachfolder. - 3
Put it where your agent looks for skills
For Claude Code, use your personal skills folder (every project) or a project’s own folder:~/.claude/skills/investor-outreach/SKILL.md # all projects .claude/skills/investor-outreach/SKILL.md # this project only
- 4
Just ask
No command needed. The agent reads the skill’s description and loads it on its own when your request matches.
SKILL.md frontmatter
What your agent reads to decide when to load this skill.
--- 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. ---
Files
Open any Markdown file to read it here.
Related skills
View all →- Govern Project DocsFreeYour AI maintains long-lived project documentation by assigning clear roles and linking active agents to canonical sources. It helps prevent doc rot, context loss, and repeated rediscovery by organizing existing docs without adding new root files.
- Kubernetes Deployment PatternsFreeTurn your Kubernetes manifests into production-ready deployments with proper resource management and security. It provides templates for probes, RBAC, autoscaling, ConfigMaps, Secrets, and kubectl debugging commands.
- Create Hookify RulesFreeYour AI writes and configures Hookify rules to watch for patterns and show messages during events. It handles YAML frontmatter, regex patterns, and supports multiple event types like bash, file changes, and prompts.
- Growth Log WritingFreeWrite learning logs that extract reusable patterns from complex tasks or failures. It guides you to capture insights that compound over time, avoiding trivial diary entries and focusing on meaningful lessons.