Content and publishing
Draft your follow-up emails.
Drafts a connected series of three to six emails, four unless you choose another count, for cold outreach or for nurturing a warm list. Each email does one job and carries two or three subject line options, a short plain-text body in your voice, and exactly one call to action, with every call pointing to the same action. The emails are saved as drafts, and a person sends them from your own email tool.
- Three to six emails
- One ask in each
- Saved as drafts only
At a glance
- Group
- Content and publishing
- Command
- /email-sequence
- Uses
- Your offer, buyers and voice
- Writes
- The emails and a send plan
- Sends
- Nothing. Drafts only.
01When to use it
Use it when a list needs more than one email.
- A new offer needs a series of emails to one segment of your buyers.
- A list of prospects or sign-ups needs a structured follow-up over several emails.
- You want a cold outreach drip, a nurture flow, or a set of emails to warm up leads.
Not for
- One email, tuned by hand for one named prospect. Use /email-personalize
- Texting a phone list. That skill checks consent first. Use /sms-campaign
02What it needs
Your offer, your buyers, your voice.
- Your offer file, for the promise, the proof, how you handle price, and the one action every email asks for.
- Your buyer file, for the target segment, its pains, the triggers that start a purchase, its objections and its language.
- Your voice files: tone, banned phrases and reading level.
- Optional: the segment, cold or warm, how many emails, and a list of prospects or accounts from your pipeline. Leave them out and it picks sensible defaults and tells you which.
- Optional: a past reply rate or booked-call rate from your numbers log.
- Your rules file. If none exists, it tells you, and asks before writing any public claim.
03What it writes
Two drafts: the emails and the plan.
- final/email-sequence.md
- Every email with its goal, subject line options, body and single call to action, plus a suggested send cadence and a note on where results are tracked, by replies, booked calls or both.
- final/brief.md
- The goal of the series, the segment, the arc from first email to last, and the plan for sending and measuring it.
- Ledger rows
- Only with a past reply rate or booked-call rate on file: one row per metric, with a target. With none, nothing is logged and the brief notes that the first send sets the baseline.
04Limits
What it never does.
- Send or schedule an email, or connect to an email tool to send one.
- Pad the series with filler to reach a count.
- Put two asks in one email.
- Invent a metric, a name, a result or a case study figure. Proof comes from your offer file or a cited source.
- Compare you with an agency or a hire, or claim what most buyers want, unless a source in your files backs the line.
What stays with you.
- Sending each email from your own tool, on the cadence you settle on.
- Answering any line tagged for you to check.
- Reading replies and booked calls once the first send sets a baseline.
05Sample output
A four-email arc, with its timing.
From a made-up cold sequence a print shop could send to event planners. Every email asks for the same thing: a short call.
| Job | Subject options | Send | |
|---|---|---|---|
| 1 | Relevance and a hook | Badges for your spring expo / Name badges by Thursday | Day 0 |
| 2 | The problem | When the badge printer jams at 7am / Check-in lines start at the printer | Day 3 |
| 3 | Proof | How check-in ran at Example Expo / A badge run from last spring | Day 6 |
| 4 | A direct ask | Fifteen minutes on your next event? / A quick call about June | Day 10 |
- 1 Day 0
- JobRelevance and a hook
- Subject optionsBadges for your spring expo / Name badges by Thursday
- 2 Day 3
- JobThe problem
- Subject optionsWhen the badge printer jams at 7am / Check-in lines start at the printer
- 3 Day 6
- JobProof
- Subject optionsHow check-in ran at Example Expo / A badge run from last spring
- 4 Day 10
- JobA direct ask
- Subject optionsFifteen minutes on your next event? / A quick call about June
Email 4, as drafted
- Goal: book a short call about the next event.
- Body: four short lines of plain text in the shop's voice.
- Call to action: pick a time at example.com/call.
- Subject options: Fifteen minutes on your next event? / A quick call about June.
06Related skills
Often run beside it.
/email-personalizePersonalize one email to one prospect Content and publishing-
/sms-campaignDraft a text campaign to a consented list Content and publishing -
/landing-pageDraft a landing page with one action Content and publishing -
/copy-optimizeScore copy variants and keep the best Content and publishing
07Questions
Before you run it.
Will it send or schedule the emails?
No. Every email is saved as a draft. It never connects to an email tool to dispatch anything, so a person sends each one from their own email tool.
How many emails will I get?
Between three and six, and four if you do not choose. Each one does a single job, such as a hook, the problem, proof, an objection, a direct ask, or a breakup note at the end, and the arc is trimmed to the count instead of padded.
Can it use my past reply rates?
Yes, when they are on file. It logs a row per metric with the baseline, the current figure and a target. With nothing on file, it invents nothing and the brief says the first send will set the baseline.
Have us build it
We can build it for you.
Start with the free plan. A person names the first fix.



