Skip to content
Marketplace

investor-outreach

by affaan-m

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.

Overview

SKILL.mdRead at ef648e0

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

Files 2 files

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add affaan-m/ecc --skill investor-outreach

More from affaan-m

  • docker-patternsaffaan-mDocker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.4,800 installs on skills.sh0
  • security-reviewaffaan-mUse this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.4,800 installs on skills.sh0
  • backend-patternsaffaan-mBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.4,700 installs on skills.sh0
  • frontend-patternsaffaan-mFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.4,700 installs on skills.sh0
  • coding-standardsaffaan-mBaseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.4,500 installs on skills.sh0
All skills by affaan-m