Nurture Sequence Architect
Architects nurture sequences where each email earns the next open.
Sonnetjson outputv1.2
Variable filler
Fill values and watch them flow into the prompt below. Nothing is stored.
The entry trigger for the sequence
What they know and believe at entry
The conversion goal
Number of emails in the sequence
Days the sequence spans
The prompt
You design email nurture sequences where each email earns the next open. You architect the sequence; a writer executes each email later.INPUT:Entry trigger: {{trigger}} // e.g. downloaded guide X, tier=NURTURE from ICP scorerAudience state: {{audience_state}} // what they know/believe at entryConversion goal: {{goal}}Sequence length: {{n_emails}} over {{n_days}} daysTASK — for each email produce:1. job: the ONE belief change or micro-commitment this email exists to create (not "provide value").2. subject_direction: the emotional register + hook type, not final copy.3. content_beat: the single idea, story, or proof point carried.4. cta_intensity: none | soft | direct — the sequence must escalate, never open with direct.5. exit_condition: behavior that should remove them from the sequence (e.g., booked a call → exit to sales handoff).SEQUENCE RULES:- Email 1 delivers the promised asset in the first two lines.- No two consecutive emails with the same content_beat type (story/data/how-to/proof).- At least one email must give away something genuinely useful with zero CTA.OUTPUT — ONLY JSON: { "sequence_thesis": "", "emails": [ { "day": 0, "job": "", "subject_direction": "", "content_beat": "", "cta_intensity": "", "exit_condition": "" } ] }Tap the block to copy
inputs
- trigger
- entry event
- audience_state
- beliefs at entry
- goal
- conversion goal
- n_emails / n_days
- sequence shape
outputs
- sequence_thesis
- the belief journey in one line
- emails[]
- day, job (one belief change), subject_direction, content_beat, cta_intensity (escalating), exit_condition
v1.22026-06-16current
Rule added: at least one email gives away something genuinely useful with zero CTA.
v1.02026-03-12
Initial release.
Honest known limits — every prompt has them.
- This architects the sequence — the emails themselves are written later, so a great architecture can still be executed poorly.
- Escalation rules assume the whole sequence sends; heavy mid-sequence exits (a good thing) make late-sequence CTAs under-tested.