--- name: follow-up-email-sequence-writer description: Drafts a personalized multi-touch follow-up email sequence for a contact or deal, grounded in the prior CRM engagements so each touch builds on the last. Use when the user asks to "write a follow-up sequence", "draft follow-up emails for this deal", "nurture this contact", "what should I send next", or wants the next several touches planned and written. license: MIT compatibility: Requires a connected CRM. Drafts only — does not send. metadata: author: Builder.org version: 2.0.0 persona: Strategic Steve, Marketing Meg rave: R4 A4 V4 E3 category: crm --- # Follow-Up Email Sequence Writer ## What it does A ready-to-paste follow-up sequence built on where the relationship actually stands: it reads the prior engagements, gives each touch one job, and writes emails that build on each other instead of repeating "any thoughts?". Drafts only; nothing is sent or logged. ## When to use - "Write a follow-up sequence for [contact]", "draft follow-up emails for this deal", "what should I send next". - "Nurture this contact", "draft my next 3 emails". - Not for a first-ever touch with no history; that single email is `cold-email-writer`. Not for reviving a deal that has been dead for weeks; `stalled-deal-revival` diagnoses before it drafts. ## Inputs One is enough: a contact email, or a deal or company name. Works with any CRM your assistant can read (HubSpot, Salesforce, or similar). Optional: the goal (book a meeting, revive, close), tone, and number of touches. Without a stated goal, infer it from the deal stage and say which you inferred. ## The bar - Touch 1 references the real last interaction by content or date. A sequence that could have been written without reading the history is a template, and the reader can smell it. - Each touch has one distinct job and a different angle. If two touches could swap positions without anyone noticing, one of them is filler. - Every email is under 120 words, one ask each. These get read on phones between meetings. - The final touch closes the loop honestly, with a clean way to say no. An endless sequence is not persistence, it is noise. - The sequence stops the moment they reply. Say so in the plan. ## Workflow 1. **Pull the context.** The contact, company, deal stage, and recent engagements: the last message each direction, what was discussed, any objection or unanswered question, and who went quiet first. The unanswered question is usually where touch 1 starts. 2. **Set the arc and confirm it.** Default: 4 touches over 14 days (day 0, 3, 8, 14), spacing that stays present without crowding, because reply odds decay fast after two silent weeks. Give each touch a job: continue the thread, add new value, make the direct ask, close the loop. Show this plan in two lines before drafting; if you cannot pause for a reply, state it and continue. 3. **Write each email.** Under 120 words, one idea, one ask, angle varied across touches: the open thread, then proof or a useful artifact, then the direct ask with a reason to decide now, then the graceful close. Reference reality throughout; a "circling back" that could apply to anyone is banned. 4. **Add subject lines and spacing.** One or two subject options per touch, under 7 words. Replies to the existing thread keep its subject; fresh angles get fresh subjects. Attach the day offsets. 5. **Deliver the sequence** paste-ready, with the stop-on-reply rule stated at the top. ## Output ``` ## Follow-up sequence · [contact/deal] · goal: [goal] Plan: [N] touches over [D] days. Stop the moment they reply. ### Touch 1 · Day 0 · [job] Subject: [option A] / [option B] [body under 120 words] ### Touch 2 · Day 3 · [job] ... ``` ## Worked example ``` Fictional example. Never reuse these names or numbers in real output. ## Follow-up sequence · Elena Vasquez, Meridian Freight · goal: close the open proposal Plan: 4 touches over 14 days. Stop the moment she replies. ### Touch 1 · Day 0 · answer the open question Subject: your API question, answered Elena, your Feb 6 note asked whether the dispatch API supports partial loads, and I let that sit too long. It does; two of our logistics customers run exactly that flow. Short walkthrough attached. Does that clear the last technical question, or is there another one behind it? ### Touch 2 · Day 3 · add proof Subject: how Ridgeline handled the same rollout Quick one: Ridgeline Carriers went live in three weeks with the same two-hub setup you are planning for Columbus. Their ops lead wrote up what she would do differently; sharing it because most of it applies to you. Worth a read before your team scopes the rollout. ### Touch 3 · Day 8 · direct ask Subject: March 31 timing Elena, being direct: if we sign by March 13, you are live before your Columbus hub opens, and that date is what your proposal is priced around. Can we get 20 minutes this week with you and Rob to settle the open items? ### Touch 4 · Day 14 · close the loop Subject: closing the file? No reply needed if the timing is wrong, and no hard feelings either. I will assume Columbus pushed this down the list and stop nudging. If it is still live, one line back and I will hold the proposal terms through April. ``` ## Never - Never write "just checking in", "bumping this", or "any thoughts?" as the substance of a touch. Every email carries something: an answer, an artifact, a reason, or a clean exit. - Never repeat the same ask verbatim across touches. - Never fabricate a prior conversation detail. If the history is thin, say the sequence is working from limited context. - Never let the sequence outlive a reply, an unsubscribe, or a "no". The stop rule is part of the deliverable. - Never send or enroll anything. Drafts only; the user owns the send. ## Recovery - No prior engagement found: say it plainly, write a first-touch sequence instead, and mark it cold so the user is not fooled about what it is. - History exists but the last word was theirs, unanswered by us: touch 1 becomes the overdue reply and owns the delay in one unfussy line. - An objection sits unresolved in the history: the sequence gets one touch dedicated to answering it head-on; ignoring a known objection wastes every other touch. - The goal conflicts with the stage (asked to "close" a deal still in discovery): flag the mismatch, then write to the honest goal (book the scoping call) and say why.