Lifecycle Mapping Frameworks Skill
When to Use
- Blueprinting onboarding, expansion, renewal, or churn-prevention journeys.
- Aligning automation programs with account stages, ICP tiers, or health scores.
- Auditing existing programs for gaps or over-saturation.
Framework
- Stage Definition – awareness, activation, adoption, expansion, advocacy (customize per business).
- Signal Library – activation events, product usage milestones, score thresholds, purchase behaviors.
- Touch Architecture – how many touches per stage, channel mix, personal vs automated.
- SLA Matrix – entry/exit criteria, owner, response time, success metrics.
- Experiment Layer – embed test slots to iterate hooks, cadences, or offers per stage.
Templates
- Lifecycle heat map (stage vs metric vs automation coverage).
- SLA worksheet (stage, trigger, owner, time-to-response, fallback).
- Journey backlog board (ideas, prioritized, building, live, measuring).
- GTM Agents Campaign Planning Checklist – captures marketing director playbook @puerto/README.md#183-212.
- KPI Guardrails Sheet – track reach, engagement, SQL impact, CAC payback with min/max thresholds.
- Status Packet Template – weekly single-slide update mirroring GTM Agents project-manager format @puerto/TEAM-STRUCTURE.md#193-204.
Tips
- Limit simultaneous journeys per contact; define prioritization rules.
- Include manual checkpoints (CSM/AE) for high-touch segments.
- Document every assumption so experiments can deliberately challenge them.
- Lock KPIs before build starts and refuse scope creep until metrics + owners are confirmed.
- Borrow GTM Agents's cadence: Plan → Build → QA → Launch → Inspect so reporting lines know when to approve or intervene.
- Pair every automation change with a "rip-cord" procedure the Sales Director or Ops Lead can trigger if leading indicators degrade.
GTM Agents Campaign Blueprint (Adopted)
Use this five-stage blueprint when large GTM initiatives require orchestration across demand gen, lifecycle, and RevOps teams:
- Stage 1 – Briefing & Alignment
- Confirm objective, ICP, offer, timeline, and budget.
- Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.
- Stage 2 – Architecture
- Map lifecycle stages to channels + automations.
- Define entry/exit criteria, personalization logic, and compliance constraints.
- Assign data availability checks (Serena) + documentation pulls (Context7) if needed.
- Stage 3 – Build & QA
- Break work into swimlanes (journey build, content, data, QA) and track in backlog.
- Require Playwright or similar browser QA for every externally facing experience.
- Stage 4 – Launch & Monitor
- Set Day 0/Day 7 KPI guardrails (e.g., form conversion ≥ 4%, unsubscribe ≤ 0.4%).
- Route anomalies to the Operations Lead with a rollback procedure.
- Stage 5 – Inspect & Iterate
- Use Sequential Thinking to run structured retros (what worked, what failed, hypotheses for next wave).
- Feed learnings back into lifecycle heat map + SLA matrix.
Status Reporting Template
Campaign: <Name>
Week Ending: <Date>
1. Highlights (wins, blockers, escalations)
2. KPI Snapshot (target vs actual vs guardrail)
3. Journey Coverage (stage, channel, live %)
4. Next 5 Actions (owner, due date)
5. Risks & Decisions Needed (include GTM Agents-style RAG)
Use this template to sync with Sales Director, Partnership Manager, and Project Manager counterparts each week.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: lifecycle-mapping3description: Use when designing automation programs aligned to lifecycle stages, SLAs,4---56# Lifecycle Mapping Frameworks Skill78## When to Use9- Blueprinting onboarding, expansion, renewal, or churn-prevention journeys.10- Aligning automation programs with account stages, ICP tiers, or health scores.11- Auditing existing programs for gaps or over-saturation.1213## Framework141. **Stage Definition** – awareness, activation, adoption, expansion, advocacy (customize per business).152. **Signal Library** – activation events, product usage milestones, score thresholds, purchase behaviors.163. **Touch Architecture** – how many touches per stage, channel mix, personal vs automated.174. **SLA Matrix** – entry/exit criteria, owner, response time, success metrics.185. **Experiment Layer** – embed test slots to iterate hooks, cadences, or offers per stage.1920## Templates21- Lifecycle heat map (stage vs metric vs automation coverage).22- SLA worksheet (stage, trigger, owner, time-to-response, fallback).23- Journey backlog board (ideas, prioritized, building, live, measuring).24- **GTM Agents Campaign Planning Checklist** – captures marketing director playbook @puerto/README.md#183-212.25- **KPI Guardrails Sheet** – track reach, engagement, SQL impact, CAC payback with min/max thresholds.26- **Status Packet Template** – weekly single-slide update mirroring GTM Agents project-manager format @puerto/TEAM-STRUCTURE.md#193-204.2728## Tips29- Limit simultaneous journeys per contact; define prioritization rules.30- Include manual checkpoints (CSM/AE) for high-touch segments.31- Document every assumption so experiments can deliberately challenge them.32- Lock KPIs before build starts and refuse scope creep until metrics + owners are confirmed.33- Borrow GTM Agents's cadence: **Plan → Build → QA → Launch → Inspect** so reporting lines know when to approve or intervene.34- Pair every automation change with a "rip-cord" procedure the Sales Director or Ops Lead can trigger if leading indicators degrade.3536## GTM Agents Campaign Blueprint (Adopted)37Use this five-stage blueprint when large GTM initiatives require orchestration across demand gen, lifecycle, and RevOps teams:38391. **Stage 1 – Briefing & Alignment**40 - Confirm objective, ICP, offer, timeline, and budget.41 - Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.422. **Stage 2 – Architecture**43 - Map lifecycle stages to channels + automations.44 - Define entry/exit criteria, personalization logic, and compliance constraints.45 - Assign data availability checks (Serena) + documentation pulls (Context7) if needed.463. **Stage 3 – Build & QA**47 - Break work into swimlanes (journey build, content, data, QA) and track in backlog.48 - Require Playwright or similar browser QA for every externally facing experience.494. **Stage 4 – Launch & Monitor**50 - Set Day 0/Day 7 KPI guardrails (e.g., form conversion ≥ 4%, unsubscribe ≤ 0.4%).51 - Route anomalies to the Operations Lead with a rollback procedure.525. **Stage 5 – Inspect & Iterate**53 - Use Sequential Thinking to run structured retros (what worked, what failed, hypotheses for next wave).54 - Feed learnings back into lifecycle heat map + SLA matrix.5556## Status Reporting Template57```58Campaign: <Name>59Week Ending: <Date>60611. Highlights (wins, blockers, escalations)622. KPI Snapshot (target vs actual vs guardrail)633. Journey Coverage (stage, channel, live %)644. Next 5 Actions (owner, due date)655. Risks & Decisions Needed (include GTM Agents-style RAG)66```6768Use this template to sync with Sales Director, Partnership Manager, and Project Manager counterparts each week.6970---7172---73> Converted and distributed by [TomeVault](https://tomevault.io/claim/gtmagents) — claim your Tome and manage your conversions.74<!-- tomevault:4.0:skill_md:2026-04-11 -->