CoreCMO

Channels & Execution


Email & Lifecycle

Email is the connective tissue between awareness and pipeline. Your highest-leverage owned channel — when you treat it as a program, not a newsletter habit.

Channels & Execution 5 prompts 1 agent — Lifecycle Email Agent ~5 min preview

The framework — strategy first


Email & Lifecycle — the strategic foundation.

STRATEGY & PROCESS

Email is the connective tissue between awareness and pipeline. Treat it as your highest-leverage owned channel: you don't pay per impression, the audience is yours, and the cadence is yours to set. The discipline below is what separates a real lifecycle program from a newsletter habit.

Email Program Architecture

PROGRAMAUDIENCEGOALCADENCE
[COMPANY] [Newsletter Name]Opt-in subscribers + Ideal Customer Profile (ICP) leadsThought leadership, top-of-funnel brand buildingBi-weekly
Marketing Qualified Lead (MQL) NurtureContent downloaders, webinar attendeesMove to Sales Qualified Lead (SQL) status5-touch, 3-week sequence
Event Pre/Post SequencesEvent registrants and attendeesDrive meetings, convert leadsPer event (see the Events playbook)
Demo Request Follow-UpDemo form fillsConfirm and prep for demoSame-day, Day 3, Day 7
Trial / POC OnboardingActive evaluatorsConvert trial to paidDay 1, 3, 7, 14, 30
Customer ExpansionCurrent customersUpsell, cross-sell, renewal prepQuarterly + trigger-based
Win-Back / Re-EngagementLeads cold for 6+ monthsRe-qualify or confirm remove4-touch, 6-week sequence

MQL Nurture Sequence Framework

5-Touch MQL-to-SQL Sequence

Day 0 — Welcome: Deliver the content they engaged with + one related resource. Establish credibility, no hard ask.

Day 3 — Proof: Share a customer story or outcome data from a similar company. No Call-to-Action (CTA) other than 'read more.'

Day 7 — Education: Share a how-to or best-practice piece addressing their primary pain. Invite to upcoming webinar.

Day 14 — Social Proof: Share a review site quote or third-party validation + benchmark data. Offer demo.

Day 21 — Conversion: Personalized note from the assigned Business Development Rep (BDR). Clear CTA to book 20 minutes.

Your Email Lifecycle Setup

The active lifecycle programs you run, plus the tools they run on. Every email prompt on the site uses this.

Saved as [MARKETING AUTOMATION TOOL], [CRM], [LIFECYCLE PROGRAMS], [LIFECYCLE TRIGGERS] across the site.

Email Standards & Deliverability

All outbound email flows run through [MARKETING AUTOMATION TOOL] with [CRM] sync. Every email touch creates a campaign activity record.

Subject line testing: A/B test every nurture sequence. Archive winning variants in the content library.

Deliverability hygiene: monthly list scrubs, hard bounce management, unsubscribe compliance (CAN-SPAM, CASL, GDPR as applicable).

Personalization minimum: first name, company name, and one behavioral signal (e.g., content topic, event attended).

Benchmark targets: Click rate >3%, Reply rate >1% (1:1 / 1:few sequences), Unsubscribe rate <0.2%.

A NOTE ON OPEN RATE — IT'S INFLATED, DON'T LEAD WITH IT

Open rate stopped being a defensible primary metric in 2021 when Apple's Mail Privacy Protection (MPP) shipped, and Gmail's privacy changes finished the job. MPP pre-fetches every image in every email Apple Mail receives — which fires the tracking pixel before the human ever opens the message. The reported "open rate" you see in your ESP now includes a meaningful proportion of bot opens. The senior-operator move is to keep open rate as a directional signal but to never put it on the board deck or use it as the gate between MQL and SAL.

The metrics that survived MPP and that a CFO will accept: click rate (the user actively did something), reply rate (especially for 1:1 / 1:few sequences), pipeline-influenced rate (open opportunities whose contacts engaged with email in the prior 30 days), and unsubscribe rate (the inverse signal that the targeting is wrong). Lead the dashboard with those four.

The prompt pack


Paste-ready prompts for Email & Lifecycle.

Each prompt is a named, scoped deliverable. Click any card to expand the paste-able body. Run against your Operator Brief.

Five copy-paste prompts. Open ChatGPT, Claude, or Gemini. Paste a prompt. Run it. The output of one prompt feeds into the next.

READ THIS ONCE BEFORE ANY PROMPT IN THIS BOOK

These prompts assume you've populated your Operator Brief (the worksheet that lives in /Operator-Brief-Worksheet.docx). When a prompt asks for OPERATOR BRIEF, paste the relevant Brief sections rather than typing context from scratch.

Your output then arrives in your voice, against your buyers, using your differentiators. Not [BRACKETED] generics. The Brief is the difference between an LLM helper and a tool that sounds like you.

Prompt 1

5-touch MQL nurture

A 5-email nurture sequence with subject + body + send timing for each.

Write a 5-touch MQL nurture sequence for the segment below. PRODUCT: [one-liner] MQL ENTRY POINT: [gated download / webinar / form] TARGET PERSONA: [role + vertical] GOAL: book a sales call For each of 5 emails (Day 0, +2, +4, +7, +12): - Subject (≤6 words) - Pre-header (≤90 chars) - Body (150–200 words) - Single CTA (1 button per email) Each email should add new value, not push the CTA harder. End with the ONE A/B test you'd run on this sequence first.

Prompt 2

Subject-line lab

Twelve subject-line variants for one email, scored on hook strength + clarity + brand fit.

Write 12 subject-line variants for the email below. EMAIL PURPOSE: [one sentence] AUDIENCE: [persona] BODY OPENING: [first 2 lines of body] BRAND VOICE: [3 adjectives] 12 variants across 4 archetypes (3 each): 1. Curiosity hook 2. Question 3. Number / specific stat 4. Direct value claim For each: subject + score 1-5 on hook / 1-5 on clarity / 1-5 on brand fit. Recommend top 3 for testing.

Prompt 3

Segmentation logic

A segmentation tree: which contacts get which lifecycle program, with entry rules.

Design segmentation logic for our lifecycle email program. DATA AVAILABLE: [list fields — title, vertical, stage, last activity, ARR, etc.] PROGRAMS: [list — onboarding, MQL nurture, advocacy, win-back, expansion] Build a decision tree that routes a contact into ONE program at any time. Entry rules should be unambiguous. Output: 1. Tree (markdown nested list) 2. Mutual-exclusion check — contacts can't be in two programs 3. Re-segmentation triggers (when a contact moves between programs) 4. The one segment we currently have NO program for

Prompt 4

Deliverability audit

A deliverability audit: top 5 things to fix, ranked by impact on inbox placement.

Audit our email deliverability. ESP: [HubSpot / Marketo / Customer.io / etc.] DOMAIN: [domain] RECENT ENGAGEMENT: [open rate, click rate, complaint rate, last 30d] AUTH STATUS: [SPF / DKIM / DMARC — yes/no] Identify the top 5 deliverability issues. For each: - Issue (with technical evidence) - Impact on inbox placement - Fix (specific action) - Owner (Marketing Ops / IT / vendor) - Time-to-fix Rank by impact × ease. Recommend the one to fix this week.

Prompt 5

Win-back sequence

A 3-email win-back sequence for cold contacts (no engagement in 90 days).

Write a 3-email win-back for contacts cold for 90+ days. ORIGINAL CONVERSION POINT: [what they signed up for] SEGMENT: [persona / vertical] WIN-BACK GOAL: re-engage OR clean from list Email 1 (Day 0): re-engagement — "is this still relevant" tone, soft CTA Email 2 (Day +5): high-value asset — give without asking, hard reset Email 3 (Day +10): break-up — direct "can we remove you" with one-click stay For each: subject (≤6 words), body (≤140 words), CTA. Then propose the criterion for auto-suppression after the third email.

The agent spec


The agent for Email & Lifecycle.

How to install this agent

Five steps from spec to running agent.

  1. System prompt — copy the system prompt block below into your AI tool's system prompt field (Claude Project instructions, Cowork Skill instructions, custom GPT config, or your agent platform's equivalent).
  2. Inputs — wire the inputs as the agent's reference files. The Operator Brief is always input #1; the other inputs vary by agent.
  3. Outputs — the output schema tells you what the agent produces. Use it as a structured-output instruction in the system prompt, or as the format you expect to see back.
  4. Evals — before publishing any output, score it against the eval criteria. Don't ship anything that doesn't pass.
  5. Cadence — set the run cadence on your calendar (or your agent platform's scheduler). Log every run in your wins log.

Lifecycle Email Agent

Owns the email program as a lifecycle — trigger-based sequences, suppression hygiene, deliverability monitoring, and the lifecycle-to-stage map. Protects sender reputation while compounding pipeline.

Who is this agent
Identity card
NameLifecycle Email Agent
RoleEmail lifecycle program operations — the nurture-to-pipeline layer
OwnerDirector of Lifecycle Marketing
Reports toVP Marketing
Versionv0.5 (supervised)
SurfaceReplit + Postgres + integration with email platform (HubSpot / Marketo / Customer.io / Klaviyo)
Output target/lifecycle/sequences/ + /lifecycle/health.md + /lifecycle/weekly-digest.md
Review cadenceDaily deliverability watch; weekly sequence performance review; quarterly lifecycle refresh
Mission
Run email as a lifecycle program, not a blast list. Maintain trigger-based sequences for every lifecycle stage. Watch deliverability daily — bounce rates, spam complaints, sender reputation. Manage suppression hygiene. Coordinate with the Comms Governance Agent to respect cross-channel send-rate caps. Convert traffic into pipeline without burning the list.
Goals & KPIs the agent moves
Leading indicators — the agent controls these
Bounce rate< 2%
Sender reputation (Google Postmaster / Microsoft SNDS)≥ 95% “high”
Lagging indicators — downstream outcomes with review triggers
Spam complaint rate. Trigger: any single week above 0.2% pages the Marketing Ops Lead for list-hygiene and segmentation review.< 0.1%
Sequence-to-MQL conversion vs. pre-sequence baseline. Trigger: 2 consecutive quarters below baseline pages the Demand Gen Lead for sequence-content review.≥ 1.2× baseline
What it does
Task list
  1. Real-time Process new contacts entering each lifecycle stage. Trigger the appropriate sequence. Coordinate with Comms Governance Agent to check send-rate caps before each send.
  2. Daily Pull deliverability data from email platform + Google Postmaster. Surface any platform showing degradation.
  3. Daily Suppression hygiene: process unsubscribes + bounces + complaints. Remove from all active sequences immediately.
  4. Daily Watch sequence health: open rates, click rates, reply rates per sequence. Flag any sequence with sudden drop.
  5. Weekly Compile weekly Lifecycle Health digest — deliverability, sequence performance, suppression hygiene, top-performers, underperformers.
  6. Weekly Draft new sequence variants for underperforming stages. Submit to Brand Voice Agent + Director for review.
  7. Monthly Sequence-to-stage map audit. Are all lifecycle stages covered? Are stages still defined correctly?
  8. Monthly List hygiene audit. Surface dormant contacts (no engagement > 6 months). Recommend re-engagement campaign or suppression.
  9. Quarterly Full lifecycle refresh. Audit every sequence’s performance. Retire dead sequences. Build new ones for emerging stages.
  10. Event When a contact triggers a sales-handoff signal (demo request, pricing page visit), pause nurture + route to AE.
  11. Event When Comms Governance Agent raises a send-rate cap concern, sequence holds + suggest alternative timing.
Schedule grid
TaskFrequencyDurationOutput goes to
Real-time sequence trigger + send coordinationContinuous< 5 sec per eventEmail platform + Comms Governance Agent
Daily deliverability checkDaily 06:00~10 minDirector Lifecycle + IT if degradation
Daily suppression hygieneDaily 06:30~5 minEmail platform
Daily sequence health watchDaily 16:00~10 minDirector Lifecycle
Weekly Lifecycle Health digestWeekly Mon 11:00~30 minDirector Lifecycle + VP Marketing
Weekly sequence variant draftingWeekly Wed 10:0060–90 minDirector Lifecycle + Brand Voice Agent
Monthly list hygiene + sequence map auditMonthly 1st~90 minDirector Lifecycle + Director MarOps
Quarterly lifecycle refreshQuarterly Q-1 days~4 hoursDirector Lifecycle + VP Marketing
Triggers

Scheduled (cron-style):

ScheduleWhat it runs
0 6 * * *Daily deliverability check
30 6 * * *Daily suppression hygiene
0 16 * * *Daily sequence health watch
0 11 * * 1Weekly Lifecycle Health digest
0 10 * * 3Weekly variant drafting
0 9 1 * *Monthly list + sequence audit

Event-driven:

EventWhat it runs
Contact enters a new lifecycle stageTrigger appropriate sequence after Comms Governance check
Contact unsubscribes or marks spamRemove from ALL active sequences immediately
Sender reputation drops below “high” on PostmasterPage Director Lifecycle + IT within 30 min; pause sends from affected domain
Sales-handoff signal fires (demo request, pricing page visit)Pause nurture sequences; route to AE via Account Intel Hub
Comms Governance Agent flags send-rate cap concernHold the send; surface suggested-window for retry
Who it works with
Inputs
SourceTypeCadenceRequired?
Operator Brief (Sections 3, 8)MarkdownRead every runRequired
Lifecycle-stage definitionsYAMLQuarterly refreshRequired — core config
Email platform send + engagement dataAPIReal-timeRequired
Google Postmaster + Microsoft SNDSAPI / portalDailyRequired
CRM stage + opportunity eventsWebhookReal-timeRequired
Comms Governance Agent decision APIInline callPer-sendRequired
Brand Voice Agent scoring APIInline callPer-draftRequired
Suppression list (master)PostgresReal-timeRequired
Outputs
OutputFormatTarget pathAudience
Sequence triggers + sendsEmail platform callsEmail platformRecipient (after governance + voice gates)
Daily deliverability healthMarkdown + Slack message/lifecycle/deliverability/YYYY-MM-DD.mdDirector Lifecycle + IT
Weekly Lifecycle Health digestMarkdown + chart bundle/lifecycle/digests/YYYY-WW.mdDirector Lifecycle + VP Marketing
Sequence variant draftsMarkdown + email HTML/lifecycle/sequences/<stage>-<date>.mdDirector Lifecycle + Brand Voice Agent (approval)
Monthly list hygiene reportMarkdown/lifecycle/hygiene/YYYY-MM.mdDirector Lifecycle + Director MarOps
Quarterly lifecycle refreshMarkdown/lifecycle/quarterly/Q<n>.mdVP Marketing
↑ Upstream — agents/sources that feed this one
  • Operator Brief (human-maintained). Personas + voice rules ground every sequence draft.
  • Signal Router. Routes lifecycle-stage transitions + sales-handoff signals.
  • Account Intel Hub. Per-account context informs sequence personalization.
  • Persona Researcher Agent. Persona-level engagement patterns inform sequence design.
  • Comms Governance Agent. Send-rate cap decisions gate every send.
  • Brand Voice Agent. Scores every sequence draft before publish.
↓ Downstream — agents/humans that consume its output
  • Director of Lifecycle Marketing (human). Reviews + approves new sequences; owns deliverability + hygiene.
  • Email platform (Marketo / HubSpot / Customer.io / Klaviyo). Receives sequence configurations + send commands.
  • Comms Governance Agent. Receives send-event data for the cross-channel ledger.
  • Account Intel Hub. Receives per-contact engagement signals for the account record.
  • Revenue Attribution Engine. Receives sequence-to-conversion data for the attribution model.
  • Performance Marketing Agent. Receives high-converting sequence patterns for paid-channel testing.
Human escalation paths
Trigger conditionEscalate toWithin
Sender reputation drops below “high” sustained 24hDirector Lifecycle + IT + VP MarketingImmediate (deliverability emergency)
Spam complaint rate > 0.1% on any campaignDirector Lifecycle + Legal + IT< 4 hours
Bounce rate > 5% on a sendDirector LifecycleSame business day (list hygiene issue)
Sequence MQL conversion drops > 30% vs. trailing 30 daysDirector Lifecycle + VP Marketing< 7 days
Comms Governance hard-rejects a send (caps + escalation pattern)Director Lifecycle + Director Comms GovernanceSame business day
How to build it
System prompt
You are the Lifecycle Email Agent for [COMPANY]. YOUR JOB Run email as a lifecycle program, not a blast list. Maintain trigger-based sequences for every stage. Protect deliverability. Coordinate with Comms Governance Controller. Convert traffic to pipeline without burning the list. INPUTS (always read in this order) 1. /operator-brief.md (Sections 3, 8) 2. /lifecycle/stages.yaml - lifecycle stage definitions 3. /lifecycle/sequences/* - active sequence library 4. CRM event payload (the trigger) 5. Comms Governance decision (approve/hold/reject) 6. Suppression list (master) OUTPUTS - Email platform send commands (after gates pass) - /lifecycle/deliverability/YYYY-MM-DD.md (daily) - /lifecycle/digests/YYYY-WW.md (weekly) - /lifecycle/sequences/<stage>-<date>.md (variant drafts) RULES 1. ALWAYS check Comms Governance Agent BEFORE any send. Honor decision. 2. ALWAYS check suppression list BEFORE any send. Honor hard rejects. 3. Run Brand Voice Agent on every new sequence variant BEFORE go-live. 4. Remove unsubscribed + complained contacts from ALL active sequences immediately. 5. Sales-handoff signals (demo, pricing visit) pause nurture - they're now in active sales motion. 6. Never adjust the suppression list autonomously to re-add a contact. 7. Voice rules from Brief Section 8 apply to every draft. ESCALATION - Sender reputation drop sustained 24h: page Director + IT + VPM immediately. - Spam rate >0.1%: page Director + Legal + IT within 4h. - Bounce rate >5% on a send: page Director same business day.
Tools & integrations
Platform / toolUsed forRequired?
Replit + PostgresSequence state + suppression listRequired
Email platform API (HubSpot / Marketo / Customer.io / Klaviyo)Send + engagement dataRequired
Google Postmaster + Microsoft SNDS APISender reputation monitoringRequired
Salesforce / HubSpot CRM APILifecycle stage + opportunity eventsRequired
Comms Governance Agent APIPer-send gatingRequired
Brand Voice Agent APIPer-draft scoringRequired
Slack APIDaily + weekly digests + alertsRequired
Guardrails — what it must not do
  • Never send without Comms Governance approval. Hard gate.
  • Never send to a suppressed contact. Hard gate.
  • Never publish a sequence without Brand Voice Agent scoring + Director approval.
  • Never re-add an unsubscribed contact autonomously. Compliance requires explicit re-opt-in.
  • Honor TCPA + GDPR + CAN-SPAM + CASL at all times.
  • Never share suppression list outside the lifecycle + legal + compliance scope.
  • Never modify lifecycle stage definitions autonomously. Stage changes are quarterly.
Evals + hallucination defense

Evals — output quality checks:

  1. Deliverability stability. Monthly: % of days with sender reputation “high” on Postmaster. Target ≥ 95%.
  2. Sequence conversion. Monthly: per-sequence MQL conversion vs. baseline. Target ≥ 1.5× trailing 90-day baseline.
  3. Suppression latency. Daily: time from unsubscribe-event to removal from active sequences. Target < 60 seconds.
  4. Voice fidelity. Monthly: Brand Voice Agent score across new sequence drafts. Target average ≥ 4.2.

Hallucination defense — specific checkpoints:

  • Sequence performance claims must trace to email platform API exports.
  • Sender reputation claims must cite Postmaster / SNDS API responses.
  • Per-contact engagement signals must trace to specific event IDs.
  • Suppression decisions must cite the source event (unsubscribe / bounce / complaint) + timestamp.
  • When data is missing for a metric, surface the gap rather than guess.
Maturity curve + first-run checklist
v0.1 — Manual-assistAgent drafts sequence variants on-demand. Sends happen via human review. Useful from day 1.
v0.5 — SupervisedReal-time triggers + governance + hygiene on. Director Lifecycle approves new sequences. Default ship state.
v1.0 — Semi-autonomousAfter 90 days clean evals + zero compliance violations, agent can auto-approve minor sequence variants (subject-line tests, send-time optimization). New stage sequences stay human-approved.

First-run checklist — 5 steps from spec to running agent:

  1. Author lifecycle-stage definitions YAML with Director Lifecycle + CRO.
  2. Wire email platform + Postmaster + SNDS APIs. Verify daily deliverability data.
  3. Build the initial sequence library — one per stage to start.
  4. Run in shadow mode for 2 weeks. Director reviews every send; tunes governance interaction.
  5. Turn on live mode. Subscribe Director Lifecycle + VP Marketing to weekly digest. Log every run in /lifecycle/agent-log.md.
Strategic · Creative · Data Driven · Revenue Accelerator