Article
Cold Email Sequences: Architecture, Stop Rules, and… - Gangly
getgangly.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
“A cold email sequence is an email-only workflow that moves an eligible prospect through planned message jobs until a reply, opt-out, delivery failure, ownership change, disqualifying fact, or final stop condition occurs.” This canonical owns sequence architecture. Use the cold-email follow-up guide for follow-up writing, email sequence examples for copy artifacts, and the multichannel cadence guide when calls or social touches enter the plan.
Define the cold email sequence job “A sequence should answer one bounded prospecting question.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
Write the sequence contract before copy “Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence.” Layer Question Evidence Eligibility Why may this person enter now? IDs, role, trigger, source/date Message What new job does it perform? Version, claim sources, CTA State What permits the next send? Delivered, no stop, still eligible Stop Which event removes or pauses? Reply, opt-out, bounce, complaint, duplicate Decision What expands or retires it? Denominators, gates, window
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “Eligibility Why may this person enter now? IDs, role, trigger, source/date” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
Define the cold email sequence job “Enrollment population, trigger, problem, proof and next action must be coherent.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “State What permits the next send? Delivered, no stop, still eligible” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
A sequence should answer one bounded prospecting question. For example: will finance leaders at companies with a verified system change discuss a specific reconciliation problem? Enrollment population, trigger, problem, proof and next action must be coherent. Mixing industries, roles, problems and offers prevents useful diagnosis. “Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window.” Write the sequence contract before copy
A sequence should answer one bounded prospecting question. For example: will finance leaders at companies with a verified system change discuss a specific reconciliation problem? Enrollment population, trigger, problem, proof and next action must be coherent. Mixing industries, roles, problems and offers prevents useful diagnosis. “Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.” Write the sequence contract before copy
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “Message What new job does it perform? Version, claim sources, CTA” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “Stop Which event removes or pauses? Reply, opt-out, bounce, complaint, duplicate” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
Layer Question Evidence Eligibility Why may this person enter now? IDs, role, trigger, source/date Message What new job does it perform? Version, claim sources, CTA State What permits the next send? Delivered, no stop, still eligible Stop Which event removes or pauses? Reply, opt-out, bounce, complaint, duplicate Decision What expands or retires it? Denominators, gates, window “A governed suppression service owns the strongest do-not-contact state.” Give every message a distinct job
Layer Question Evidence Eligibility Why may this person enter now? IDs, role, trigger, source/date Message What new job does it perform? Version, claim sources, CTA State What permits the next send? Delivered, no stop, still eligible Stop Which event removes or pauses? Reply, opt-out, bounce, complaint, duplicate Decision What expands or retires it? Denominators, gates, window “CRM may own account and rep assignment.” Give every message a distinct job
“It is not a fixed number of emails or permission to keep sending until someone responds.” This canonical owns sequence architecture. Use the cold-email follow-up guide for follow-up writing, email sequence examples for copy artifacts, and the multichannel cadence guide when calls or social touches enter the plan.
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “Decision What expands or retires it? Denominators, gates, window” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
Define the cold email sequence job “Mixing industries, roles, problems and offers prevents useful diagnosis.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
“A cold email sequence is an email-only workflow that moves an eligible prospect through planned message jobs until a reply, opt-out, delivery failure, ownership change, disqualifying fact, or final stop condition occurs.” This canonical owns sequence architecture. Use the cold-email follow-up guide for follow-up writing, email sequence examples for copy artifacts, and the multichannel cadence guide when calls or social touches enter the plan.
Define the cold email sequence job “A sequence should answer one bounded prospecting question.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
Define the cold email sequence job “Enrollment population, trigger, problem, proof and next action must be coherent.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
Write the sequence contract before copy “Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence.” Layer Question Evidence Eligibility Why may this person enter now? IDs, role, trigger, source/date Message What new job does it perform? Version, claim sources, CTA State What permits the next send? Delivered, no stop, still eligible Stop Which event removes or pauses? Reply, opt-out, bounce, complaint, duplicate Decision What expands or retires it? Denominators, gates, window
Create a one-page contract: eligible account/person; verified address; approved outreach basis; exclusions; trigger/as-of time; problem hypothesis; evidence; CTA; sender; message jobs; progression; stop/pause rules; suppression authority; experiment; metrics; review date; rollback owner; retained evidence. “Eligibility Why may this person enter now? IDs, role, trigger, source/date” CRM may own account and rep assignment. A governed suppression service owns the strongest do-not-contact state. The sender executes approved messages but should not overwrite consent, ownership or identity. A rep may correct relevance or take over a reply; automation should pause while correction is unresolved.
“It is not a fixed number of emails or permission to keep sending until someone responds.” This canonical owns sequence architecture. Use the cold-email follow-up guide for follow-up writing, email sequence examples for copy artifacts, and the multichannel cadence guide when calls or social touches enter the plan.
Define the cold email sequence job “Mixing industries, roles, problems and offers prevents useful diagnosis.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
A sequence should answer one bounded prospecting question. For example: will finance leaders at companies with a verified system change discuss a specific reconciliation problem? Enrollment population, trigger, problem, proof and next action must be coherent. Mixing industries, roles, problems and offers prevents useful diagnosis. “Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window.” Write the sequence contract before copy
Define the cold email sequence job “A sequence should answer one bounded prospecting question.” Freeze sender domain/mailbox, legal entity, owner, platform, CRM source, list source and date, jurisdictions/subscriber types, suppression sources, segment, trigger, message versions, send window, threading, reply and OOO handling, bounce rules, experiment assignment, and observation window. Deliverability is a separate prerequisite covered by the deliverability guide; legal review belongs with the compliance guide.
“A cold email sequence is an email-only workflow that moves an eligible prospect through planned message jobs until a reply, opt-out, delivery failure, ownership change, disqualifying fact, or final stop condition occurs.” This canonical owns sequence architecture. Use the cold-email follow-up guide for follow-up writing, email sequence examples for copy artifacts, and the multichannel cadence guide when calls or social touches enter the plan.
Measure with trustworthy denominators “Prospect reply rate = prospects with human reply ÷ prospects with at least one delivered message.” Positive reply rate = prospects with policy-defined positive reply ÷ delivered prospects.
In Reply rates
Correction burden = review/correction/incident minutes ÷ enrolled prospects. “Separate positive, negative, referral, opt-out, complaint, automated and unknown replies.” Worked example—not a benchmark: 500 eligible prospects enroll; 470 receive at least one message. Thirty produce human replies, 12 are positive under the frozen rubric, and eight become qualified meetings. Positive reply rate is 12 ÷ 470 = 2.55%; qualified meeting rate is 8 ÷ 500 = 1.6%. If one suppressed prospect was sent and the gate is zero, the pilot fails regardless of conversion.
Report raw counts by segment, sender, source, version and touch eligibility. Separate positive, negative, referral, opt-out, complaint, automated and unknown replies. Do not infer reading from a pixel or causation from the last message before booking. “Worked example—not a benchmark: 500 eligible prospects enroll; 470 receive at least one message. Thirty produce human replies, 12 are positive under the frozen rubric, and eight become qualified meetings. Positive reply rate is 12 ÷ 470 = 2.55%; qualified meeting rate is 8 ÷ 500 = 1.6%. If one suppressed prospect was sent and the gate is zero, the pilot fails regardless of conversion.” Pilot, revise, and roll back safely
Rollback pauses enrollments and queued sends, preserves opt-outs/evidence, removes only test-created future work, restores routing, reconciles CRM state, revokes unnecessary permissions, communicates incidents and monitors delayed events. Never delete suppression or legitimate reply history. “TCO = platform/mailbox + data + domain/authentication operations + copy/research + approvals + integration + reply work + monitoring/reconciliation + incidents + overlap + exit.” Print the cold email sequence checklist
Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.