Agent 43 of 71 · Email & Lifecycle
Nurture Sequence Architect
Design sequences that move a defined person one buying stage forward and then stop. Each email has a job in the arc, branches react to what the reader actually did, and exit rules make sure nobody keeps receiving nurture after they reply, buy or opt out.
Agent contract
Use to design a multi-email sequence: entry trigger, audience, number and spacing of emails, the job of each, branching on replies or clicks, exit and suppression rules, and the stage the sequence should move people to.
When it runs
- A lead magnet, event or campaign needs a follow-up path.
- Email Strategy Agent assigns a new stream that needs structure.
- An existing sequence shows drop-off at a specific step.
What it needs
| Input | Required | From |
|---|---|---|
| Entry trigger and segment definition | Yes | You |
| Persona and stage the sequence serves | Yes | Buyer Personas |
| Approved kernels by stage | Yes | Message Memory |
| Proof items per stage | Yes | Proof Vault |
| Qualifying signal from the lead magnet | Optional | Lead Magnet Architect |
| Program rules (caps, suppression, consent) | Optional | Email Strategy Agent |
How it works
- Define entry precisely (trigger event, segment, consent basis) and the target stage movement, e.g. awareness → consideration.
- Set the arc: usually 4–6 emails, each with one job (reframe, teach, prove, invite) and the kernel it carries.
- Place proof by stage: awareness emails teach without hard claims; consideration and decision emails cite ProofIDs.
- Space emails within the program frequency cap and specify send windows; avoid overlap with other active streams for the same contact.
- Define branches: reply → hand to a human owner; high-intent click → shorten path to the ask; no engagement after N emails → exit to newsletter or sunset.
- Write exit and suppression rules: replied, meeting booked, became opportunity or customer, unsubscribed, bounced.
- Render templates/email-sequence.md with a flow diagram and run `python3 scripts/sns.py proof check <sequence.md>` on the spec.
What it delivers
Sequence spec: entry trigger and segment, target stage move, flow with timing, per-email job/kernel/ProofID/tags, branches, exit and suppression rules, success metric and read dates.
Output contract: email-sequence
Quality bar
- Each email has a distinct job; no two emails make the same ask in the same words.
- Every sequence has exits for reply, conversion, unsubscribe and bounce.
- Decision-stage emails cite ProofIDs that pass the proof check.
Hands off
- Email CopywriterThe spec is approved and each email needs copy.
- Marketing Workflow ArchitectBranching and exit logic needs to be built in the ESP or automation tool.
- Email Performance OptimizerThe sequence has run long enough for a step-level readout.
When a person steps in
- If the entry segment lacks consent for marketing email, stop and return to the Email Strategy Agent.
- If no approved kernels exist for the target stage, route to the Message Kernel Architect instead of drafting new claims.
Example
Request
“Design the follow-up for people who take the close-readiness assessment.”
Result
Two 5-email paths by score band over 18 days; low band leads with teaching, high band reaches the demo ask by email 3 with PRF-0007; reply branch routes to AE within one business day; exits on meeting booked, opportunity created or unsubscribe. Proof check passed; EXP-0034 logged.
Illustrative example from the package documentation, not a client result.