write-outreach-draft-sequence v0.1.1A

Immutable. This exact content never changes and is served at /api/v1/blob/ea49f0bbf578353e.

---
name: write-outreach-draft-sequence
description: >-
  Step of the write-outreach playbook: the brief a helper follows to write one segment's email and
  LinkedIn sequence, first lines and replies from rows and an angle prepared earlier. Run
  write-outreach instead; not for direct use.
version: 0.1.1
---

# draft-sequence

You are writing cold outreach for **one segment** of **one brand**. **This brief is complete: don't load any skill, don't read playbook files, don't start other agents, make no GooseWorks calls.** At most 3 web reads, only to re-check that a row's signal link still says what the row claims. Return in the shape at the end; no preamble.

**Inputs (in the prompt):** the brand, what it sells and its price; the sender (name, role); the segment and its angle — pain in the buyers' words (with the quote and link — or, with no quote bank, in our words labelled "not yet from buyers"), proof (a signed-off claim verbatim, or "proof needed: <what>"), the ask; the sequence shape (touches, channels, days); the rows (name, title, company, signal + URL + date, hook + URL, region flag, email status); the brand's `[outreach …]` rules and voice notes; today's date.

## Rules

- **Touch 1:** first line = the row's signal or hook and why it matters to the pain; then one or two lines on the pain and what we do (plain product fact, or the signed-off proof verbatim); one ask; sign-off with the sender's first name. 50–90 words. Subject under 50 characters, lower-case, plain.
- **Follow-ups:** each adds something new (a second pain, a short resource, signed-off proof, or a general practice framed as such — never an invented peer story) — never "bumping", "checking in", "circling back". 30–50 words, then 20–30 for the last, which leaves the door open without guilt. Same thread.
- **At most 6 touches in all** per person (e.g. 4 emails, the connection request, one LinkedIn message).
- **LinkedIn:** connection note ≤200 characters with no pitch, no ask, no link (free accounts get only a few notes a month — at volume, the invite goes without a note and the line moves to message 1); messages after accept are short, value first, one question; never the email's text.
- **First line per row:** built only on that row's facts. Nothing invented — no compliments, mutual connections, numbers, customers or results. No hook → write "no personal hook" and use the segment opener.
- **Never:** hype words (revolutionary, game-changing, cutting-edge, best-in-class), jargon (synergy, leverage, touch base), "hope this finds you well", fake "Re:", lying about how you found them, school, family, health, politics, location, "#OpenToWork", the funding amount as the opener, the predecessor of a new leader.
- **Proof:** only the signed-off line you were given, verbatim. Anything else that sounds like a result → cut it and list it under "proof needed".
- **Region rules:** `UK-soletrader` → a short letter instead of email and no DM; `CASL` / `AU-NZ` with a non-published address → no email, LinkedIn only; every email ends with the opt-out line you were given; `EU-UK`, `UK-ltd` and unknown-country rows' first email carries the source-and-object line.
- Count words and characters; rewrite to fit, never cut a sentence off.

## Return this shape

```
## <Segment>
Angle: pain "<their words>" (<link>) · proof: <verbatim or "proof needed: …"> · ask: <…>
Sequence: | day | channel | touch | subject | text | words/chars |
First lines: | row | first line | rests on (signal/hook URL, date) |
Letters (UK sole traders, if any): …
Replies: | category | answer |
Proof needed: …
Re-checked links: <n> held, <n> changed (which)
```