sourcing-outreach
Sourcing Outreach
When to Use
Activate when the user asks to write cold outreach to potential candidates (LinkedIn InMails, cold emails), craft referral request messages, build a multi-touch follow-up sequence, or improve response rates on existing recruiting outreach. Also activate when the user is sourcing for a specific role and needs help personalizing messages at scale.
Context Required
- From startup-context: Company name, one-line mission, stage/funding, notable investors or customers, recent milestones, and team size.
- From user: Role being hired for, the candidate's name and background (LinkedIn profile, blog posts, talks, open-source work), what specifically drew the user to this candidate, and the communication channel (LinkedIn, email, Twitter DM).
Workflow
- Research the candidate — Review the candidate details provided by the user. Identify 1-2 specific, genuine connection points: a project they shipped, a talk they gave, an open-source contribution, a blog post, or a career pattern that signals fit.
- Choose the outreach template — Select from: cold LinkedIn InMail, cold email, warm intro request, referral ask, or follow-up. Each has different length and tone constraints.
- Draft the message — Write a short, personalized message using the PRC framework (see below). Keep LinkedIn InMails under 300 characters for the preview. Keep cold emails under 150 words.
- Add a clear, low-friction CTA — The ask should be small: a 15-minute call, a reply with interest level, or permission to send more details. Never ask for a resume or formal application in cold outreach.
- Build the follow-up sequence — Draft 2-3 follow-ups spaced 4-7 days apart. Each follow-up adds new information (a company milestone, a team blog post, a relevant data point) rather than just "bumping" the thread.
- Review for tone — Ensure the message sounds human, not templated. Check that personalization is specific enough that it could only apply to this candidate.
More from shawnpang/startup-founder-skills
terms-of-service
When the user needs to draft, review, or update terms of service for their SaaS product or web application.
63pitch-deck
When the user wants to create, review, or restructure a fundraising pitch deck for seed or Series A. Also activates when the user mentions "deck", "pitch", "investor presentation", or "slide structure".
54competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
52review-mining
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores. Also use when the user mentions "what are users saying", "competitor reviews", "pain points", or "voice of customer research".
52prd-writing
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
48landing-page
When the user needs to create, critique, or optimize a landing page for conversion -- including headline rewrites, CTA placement, layout restructuring, or full page copy drafts.
46