home / skills / gtmagents / gtm-agents / lifecycle-mapping

This skill helps design automation programs aligned to lifecycle stages, SLAs, and GTM objectives, improving churn prevention and renewal outcomes.

npx playbooks add skill gtmagents/gtm-agents --skill lifecycle-mapping

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.7 KB
---
name: lifecycle-mapping
description: Use when designing automation programs aligned to lifecycle stages, SLAs,
  and GTM objectives.
---

# 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
1. **Stage Definition** – awareness, activation, adoption, expansion, advocacy (customize per business).
2. **Signal Library** – activation events, product usage milestones, score thresholds, purchase behaviors.
3. **Touch Architecture** – how many touches per stage, channel mix, personal vs automated.
4. **SLA Matrix** – entry/exit criteria, owner, response time, success metrics.
5. **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:

1. **Stage 1 – Briefing & Alignment**
   - Confirm objective, ICP, offer, timeline, and budget.
   - Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.
2. **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.
3. **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.
4. **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.
5. **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.

---

Overview

This skill helps design and audit automation programs mapped to lifecycle stages, SLAs, and GTM objectives. It provides a repeatable framework, templates, and a five-stage campaign blueprint to align demand, lifecycle, and revenue teams. Use it to reduce scope creep, clarify ownership, and accelerate experimentation.

How this skill works

It defines a lifecycle framework (stages, signals, touches, SLA matrix, experiment layer) and supplies practical templates like heat maps, SLA worksheets, and backlog boards. The skill guides you through Plan → Build → QA → Launch → Inspect, including KPI guardrails, rollback procedures, and structured retros. It also prescribes a five-stage GTM campaign blueprint for cross-functional orchestration.

When to use it

  • Blueprint onboarding, expansion, renewal, or churn-prevention journeys
  • Align automations to account stages, ICP tiers, health scores, or SLAs
  • Audit existing programs for gaps, overlap, or over-communication
  • Coordinate large GTM initiatives across marketing, sales, and RevOps
  • Embed a testing cadence and risk controls before full launch

Best practices

  • Limit simultaneous active journeys per contact and enforce prioritization rules
  • Include manual CSM/AE checkpoints for high-touch cohorts
  • Lock KPIs and owners before building; refuse scope creep without metrics
  • Document all assumptions so experiments can validate or disprove them
  • Pair automation changes with a clear rip-cord rollback owned by Sales or Ops

Example use cases

  • Create a lifecycle heat map to visualize stage coverage and automation gaps
  • Build an SLA worksheet that assigns owners, triggers, and response times
  • Run a campaign using the five-stage blueprint for a new product GTM wave
  • Audit email and in-app cadences to reduce unsubscribes and over-messaging
  • Establish Day 0/Day 7 guardrails and a rollback for a high-risk automation rollout

FAQ

How many touches per stage should I set?

There’s no single number — set a range based on segment value and channel. Use the touch architecture to document limits and run experiments to find the optimal cadence.

What KPIs should I lock before build?

Lock leading conversion metrics (reach, form conversion), engagement (open/click rates), and downstream impact (SQLs, CAC payback). Also set guardrails like unsubscribe and churn thresholds.