Departments / sales / email-outreach

email-outreach

Use when a rep needs a personalized outbound email sequence grounded in a research brief. Produces a 3-step cold or 4-step warm sequence with subject lines under 45 characters, bodies under 120 words, one clear CTA per email, and no filler phrases.

Department

Sales

Safety

writes-local
Writes locally

Supported stacks

Stack-agnostic — no detection required.

When to use

Trigger this skill when:

Do not use this for newsletter-style nurture emails or for templated mass sends. This skill produces account-specific sequences.

Inputs

Required:

Optional:

Outputs

A Markdown document containing the full sequence. Each email block has:

For linkedin-follow, the output includes the connection request message (under 300 characters, per LinkedIn’s limit) plus a follow-up DM.

Tool dependencies

Procedure

  1. Parse the research brief. Extract: chosen angle, the trigger it’s tied to, the persona, and the hypothesis.
  2. Pick the sequence pattern.
    • cold-3: Day 0 opener → Day 3 value-add → Day 7 break-up.
    • warm-4: Day 0 intro ack → Day 4 value-add → Day 9 specific ask → Day 14 break-up.
    • linkedin-follow: connection request → DM 3 days after acceptance → email 7 days after DM.
    • break-up: single email ending a dormant sequence.
  3. Draft subject lines. Under 45 characters, lowercase-friendly, no clickbait. Reference something specific — a trigger, a mutual connection, a metric.
  4. Draft bodies. Under 120 words. Structure:
    • Line 1: Reference the trigger, by name. (“Saw the Insight Partners round.”)
    • Lines 2-3: Hypothesis about their situation. Specific, not generic.
    • Lines 4-5: One concrete proof point — a customer name + outcome.
    • Last line: one specific CTA.
  5. Choose one CTA per email. Valid CTAs:
    • A specific meeting time (“Tuesday 10am PT or Wednesday 2pm PT?”).
    • A binary question (“Is this worth a 15-minute look, or not a priority this quarter?”).
    • A resource link tied to their situation.
    • For break-up: permission to close the file.
  6. Write the LinkedIn connection message if applicable. Under 300 chars. No pitch. Reference a specific shared context.
  7. Write the break-up email with dignity. Name the topic, offer a resource, close the loop. No “just following up.”
  8. Add a one-line rationale above each email so the rep understands the intent and can edit with context.

Examples

Example 1 — cold-3 sequence for Acme Retail VP Data

Inputs: research brief showing Series B + new VP Data + real-time CDP JDs. Angle 1 selected. Persona: Priya Shah, VP Data.

Output:

Day 0 — Opener

Rationale: Lead with the trigger (Series B + stated use of funds on personalization) and anchor on a relevant customer. Short and specific.

Subject: acme + insight partners round

Hi Priya,

Saw the $35M Series B and the stated focus on personalization. Congrats.

We helped Warby Parker lift repeat-purchase rate 6.2% in the first 90 days after moving their Shopify + Segment + Snowflake stack to real-time. Given your job posts for real-time CDP engineers, you’re likely heading to the same architecture.

Worth a 15 minute comparison of that build vs. a managed path? Tuesday 10am PT or Wednesday 2pm PT?

— Alex


Day 3 — Value-add

Rationale: If no reply, add a proof point. Send a specific artifact — not a “circling back.”

Subject: 90-day personalization blueprint

Priya — since Acme’s stack mirrors Warby Parker’s, I pulled the 90-day rollout plan they used.

Three surfaces (homepage, PDP, cart-abandon), one measurement framework, and the internal staffing model (1 PM, 2 eng, 1 analyst).

Happy to send, or walk through it live. Which is easier?

— Alex


Day 7 — Break-up

Rationale: Permission to close. No guilt, no “one more try.” A polite break-up often gets a response.

Subject: closing the loop

Priya — I’ll stop reaching out on this thread. If real-time personalization moves up your priority list in Q3 or Q4, I’ll be around.

In the meantime, here’s the Warby Parker teardown in case it’s useful: [link].

— Alex

Example 2 — warm-4 sequence for Nimbus Logistics CIO

Referral from a mutual VC. Sequence acknowledges the intro in Day 0, sends a short case-study link in Day 4, proposes a specific meeting in Day 9, and breaks up cleanly in Day 14. Day 0 subject: intro from sarah at bain capital.

Example 3 — LinkedIn connection + follow-up for a VP RevOps

Constraints

Quality checks

Before returning:

Customise for your organisation

email-outreach

The LLM will rewrite this skill for your environment. Your API key and form inputs stay in your browser — only the skill and your environment go to OpenRouter.

One line. Be specific — cloud, language, framework, orchestrator.

Free text that steers the rewrite. Leave blank if nothing specific.

cost estimate: