Investor Outreach
Draft personalized cold emails, warm-intro asks, follow-ups, and process updates for angels, VCs, strategics, and accelerators without generic fundraising fluff.
Overview
Investor Outreach is an agent skill most often used in Validate (also Launch, Grow) that drafts cold, warm-intro, follow-up, and update emails for fundraising with personalized structure and proof-led asks.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill investor-outreachWhat is this skill?
- Cold email scaffold: subject, investor-specific opener, proof-led pitch, one concrete ask
- Hard bans on generic lines (e.g. "I'd love to connect", vague thesis praise)
- Optional handoff to brand-voice for VOICE PROFILE before drafting
- Warm intro blurbs, post-meeting follow-ups, and in-process investor updates
- Thesis- and partner-fit tailoring rules so copy cannot go to any fund
- 5 core outreach rules (personalize, low-friction ask, proof, concise, no generic copy)
- 4-message types: cold email, warm intro, follow-ups, in-process updates
- 6 hard-banned phrase patterns called out for rewrite
Adoption & trust: 4.5k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know who to pitch but every draft sounds interchangeable, fluffy, or afraid to make one clear ask.
Who is it for?
Solo founders running a live fundraise who need repeatable email patterns and strict anti-generic guardrails.
Skip if: Teams that only need a CRM pipeline, pitch deck design, term-sheet negotiation, or outreach with zero personalization requirements.
When should I use this skill?
User wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized investor-facing messaging (cold email, warm intro, follow-ups, updates, thesis fit).
What do I get? / Deliverables
You get investor-specific messages with a defined structure, banned generic phrases removed, and when voice matters you align copy to an existing VOICE PROFILE from brand-voice before sending.
- Subject line plus body for cold, warm-intro, follow-up, or update emails
- Rewritten copy with generic fundraising language removed per hard bans
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Fundraising outreach is the canonical shelf in Validate because solo founders most often install this while scoping the raise, narrative, and next-step asks before or during early traction proof. Scope subphase fits when you are defining who to contact, what proof to lead with, and what single low-friction ask each message should carry.
Where it fits
Map which proof points belong in the first cold email before you widen the investor list.
Frame traction and pricing narrative in a short update without adjective-heavy pitching.
Turn a launch milestone into a one-ask investor note that leads with measurable proof.
Send a disciplined follow-up or quarterly-style update during an active fundraise process.
How it compares
Use for message craft and ask discipline—not instead of a data room, financial model, or investor CRM.
Common Questions / FAQ
Who is investor-outreach for?
Solo and indie builders (and tiny founding teams) who are emailing angels, VCs, strategic investors, or accelerators and want concise, personalized investor communication.
When should I use investor-outreach?
Use it while validating scope and narrative for a raise, when tailoring outreach to fund thesis or partner fit, after meetings for follow-ups, during a process for investor updates, and at launch or growth milestones when you need a crisp proof-led note—not a generic blast.
Is investor-outreach safe to install?
It is prose and workflow guidance only; review the Security Audits panel on this Prism page before installing any skill from the repo.
Workflow Chain
Requires first: brand voice
SKILL.md
READMESKILL.md - Investor Outreach
# 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 1. Personalize every outbound message. 2. Keep the ask low-friction. 3. Use proof instead of adjectives. 4. Stay concise. 5. 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 1. subject line: short and specific 2. opener: why this investor specifically 3. pitch: what the company does, why now, and what proof matters 4. ask: one concrete next step 5. 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