Email Drafting

Type 3a: Signal-Based (Competitor Engagement — Liker)

Signal source: LinkedIn Sales Navigator — engaged with competitor company page content Framework: Signal-Proof-Ask

Subject: The other side of freight AI

Hi {first_name} — I noticed you've been following the freight AI space and wanted to reach out. HappyRobot is the other side of that conversation — we're the platform 8 of the top 10 US freight brokers including DHL and Werner run for AI carrier calls.

If you're evaluating options in this space, I'd love to show you what enterprise-grade looks like. 15 minutes?

Why it works: Acknowledges their research without calling out the competitor by name in email (saves that for LinkedIn). "Other side of that conversation" is intriguing. Proof point (8 of top 10) is specific and strong.

Type 3b: Signal-Based (Competitor Engagement — Commenter)

Signal source: Same as 3a but lead left a comment (higher intent) Framework: Signal-Proof-Ask with comment reference

Subject: Re: your comment on freight AI

Hi {first_name} — I saw your comment on {competitor}'s post about {topic}. That's exactly the problem we work on. HappyRobot powers AI carrier calls for DHL, Werner, and 8 of the top 10 US freight brokers.

If you're actively looking at this, worth 15 minutes to see the other option?

Why it works: References their exact comment (Tier 3 personalization). "Actively looking at this" matches their behavior. Even shorter than 3a because higher-intent leads need less convincing.

Type 4: Pain-Based (Commenter)

Signal source: LinkedIn post search for pain-language keywords Framework: PAS (Problem → Agitate → Solve)

For commenters (wrote about the pain):

Hi {first_name}, saw your comment on the {source} post about {pain_topic}. "{comment_snippet}..." — that resonated.

We've been working with brokers who had the same issue. HappyRobot handles {relevant_task} so your team doesn't have to.

Worth a quick look?

For reactors (liked/reacted to pain content):

Hi {first_name}, noticed you've been following the conversation around {pain_topic} on LinkedIn.

If {company} is dealing with {specific_pain}, we might be able to help. HappyRobot automates {relevant_task} for freight brokers — no extra headcount needed.

Open to a quick chat?

Why it works: Quotes their own words back to them (strongest personalization). Empathetic tone — no hard sell. Short. The reactor version is lighter-touch because the signal is weaker.

Type 5: Competitive Displacement

Signal source: G2 reviews (1-star), public complaints, known competitor customers Framework: PAS

Subject: UserTesting alternatives in 2026

{first_name} — I'll keep this short. If you've run into participant quality issues with UserTesting, you're not alone. HubSpot and Glassdoor both moved to Outset after hitting the same wall.

We use Prolific-verified participants instead of a general panel. Different quality tier entirely. Worth 20 minutes to compare?

Why it works: Validates their frustration without bashing the competitor. Names companies they'd respect. Explains the "why" behind the switch (Prolific-verified participants). CTA is specific (20 minutes, comparison framing).

Type 6: ABM / Enterprise

Signal source: Target account list, vertical-specific research Framework: AIDA

Touch 1:

{first_name} — WeightWatchers cut their per-study research cost from $150K to $8K using Outset's AI-moderated interviews. They run 3x the studies they used to, in half the time.

I put together a quick breakdown of what this could look like for {company}'s {vertical} research. Worth 20 minutes?

Touch 3 (Day 7):

Following up with something concrete — built a rough ROI model using {industry} benchmarks. Even conservative numbers show a 6-8x reduction in per-study cost.

Happy to walk through the math. 15 minutes?

Touch 5 (Day 14):

Last note from me. If research cost or speed isn't a priority right now, totally understand. But if it is — the WeightWatchers and HubSpot numbers are worth seeing.

Open to a quick benchmark call? No demo, just data.

Why it works: Leads with a specific customer story and hard numbers. Each touch adds new value (case study → ROI model → benchmark offer). Breakup touch removes pressure. CTA evolves: overview → walk-through → benchmark.

Type 7: Follow-Up Patterns (Touch 2+)

New angle (not a bump):

{first_name} — different angle from my last email. {Peer company} just published results from their first quarter using {product}: {specific metric}. Thought it might be relevant given {company}'s {situation}.

Asset-led:

Put together a one-page breakdown of {topic relevant to them}. No pitch — just data. Want me to send it over?

Social proof drop:

Quick update — {new customer} just went live with us last week. Similar setup to {company}. Happy to share what their onboarding looked like.

Breakup:

I'll keep this short — if the timing isn't right, no worries at all. But if {problem} comes back up, I'm an easy call away. Cheers.

Type 8: Re-engagement (90-Day)

Signal source: Outreach log — leads contacted 90+ days ago with no reply, or leads who filled the role your product replaces Framework: Signal-Proof-Ask

Hi {first_name} — we chatted about 3 months ago when you were hiring for {role}. Curious how it's going. If you're still feeling the pain on {problem}, a few things have changed on our end worth seeing.

15 minutes to catch up?

Why it works: References the original conversation and signal. Acknowledges time has passed. "A few things have changed" creates curiosity without overselling.

Output Format

When delivering email drafts, use this structure:

Single Email

**Subject:** [subject line]
**Personalization tier:** [1/2/3]
**Framework:** [PAS/BAB/AIDA/Signal-Proof-Ask]
**Word count:** [X words]

---

[Email body with merge fields in {curly_braces}]

---

**Merge fields used:** {first_name}, {company}, {role_title}, ...

Full Sequence

## Sequence: [Campaign Name]

**Touches:** [N]
**Personalization tier:** [1/2/3]
**Tone:** [casual-direct / professional-sharp / provocative / empathetic]

### Touch 1 — Day 1
**Subject:** [subject]
**Framework:** [framework]

[body]

### Touch 2 — Day [N]
**Subject:** Re: [original subject] OR [new subject]
**Framework:** [framework]

[body]

### Touch 3 — Day [N]
**Subject:** [subject]

[body]

---

**Merge fields:** {first_name}, {company}, ...
**Notes:** [any special instructions for the outreach tool]