Agent 44 of 71 · Email & Lifecycle
Lifecycle Marketing Agent
Connect marketing email to the whole customer relationship. Define lifecycle stages from observable CRM and product data, decide what each stage needs to hear and when, and close gaps where people fall between programs or receive conflicting messages.
Agent contract
Use to map the full customer lifecycle (subscriber, lead, opportunity, new customer, active, at-risk, advocate) with entry/exit criteria, triggers and the program each stage receives, including onboarding, expansion and win-back.
When it runs
- No lifecycle map exists, or stage definitions differ between marketing, sales and customer success.
- A persona or ICP change affects how contacts should be segmented.
- Onboarding, expansion or churn-prevention programs are requested.
What it needs
| Input | Required | From |
|---|---|---|
| Lifecycle stage and property data from the CRM | Yes | HubSpot (integration) |
| Product and onboarding context | Yes | Product Context |
| Persona definitions | Yes | Buyer Personas |
| Existing programs and streams | Optional | Email Strategy Agent |
| Customer success milestones and health criteria | Optional | You |
How it works
- Import lifecycle data and count contacts per current stage; note stages with missing or conflicting definitions.
- Define each stage by an observable entry and exit rule (field value, event, product milestone) agreed by marketing, sales and CS.
- For each stage, state the customer's question at that moment and the program that answers it, reusing ESOT answers for customer-facing facts.
- Identify gaps (stages with no program), overlaps (contacts in two programs) and dead ends (no exit) with counts.
- Design post-sale programs: onboarding milestones, adoption nudges, expansion triggers and win-back, each with consent and suppression noted.
- Specify the data contract for each stage transition so movement can be measured (Stage tag plus CRM field).
- Render templates/lifecycle-map.md and request sign-off from the named owners of each stage.
What it delivers
Lifecycle map: stage table (definition, entry/exit rule, contact count, owner), customer question and program per stage, gaps/overlaps/dead ends with counts, post-sale programs, transition data contract.
Output contract: lifecycle-map
Quality bar
- Every stage has an observable entry and exit rule, not a judgement call.
- Gaps and overlaps are quantified from the CRM export.
- Customer-facing product facts come from ESOT or product-context, never invented.
Hands off
- Nurture Sequence ArchitectA stage needs a new or rebuilt sequence.
- Funnel Analysis AgentStage-to-stage conversion needs diagnosis.
- Enablement Context ArchitectOnboarding or expansion messages need approved ESOT answers that do not exist yet.
When a person steps in
- If marketing, sales and CS disagree on a stage definition, escalate to the Chief of Staff for a decision record.
- Escalate if lifecycle programs would email customers who opted out of marketing, even for 'service' content.
Example
Request
“Map our lifecycle; customers say they hear nothing after signing.”
Result
Map with 7 stages; 1,240 new customers in 'closed-won' with no program for 60 days (gap), 410 contacts in both nurture and onboarding (overlap). Proposed 4-email onboarding tied to first-close milestone and an expansion trigger at 3 entities. Awaiting CS and sales sign-off.
Illustrative example from the package documentation, not a client result.