Lifecycle / CRM Plan Skill
Lifecycle marketing is the difference between a product people sign up for and one they actually use.
This skill maps the customer lifecycle to triggered journeys — each with a clear job — so messaging is
behaviour-driven and purposeful, not a batch-and-blast newsletter that trains people to ignore you.
Required Inputs
Ask for these only if they aren't already provided:
- Product & lifecycle stages — what the journey from signup → active → loyal → churned looks like.
- The key moments — activation milestone, the "aha", upgrade triggers, and churn signals.
- Channels available — email, push, in-app, SMS — and any consent/deliverability constraints.
- Goal — the lifecycle metric to move (activation %, D30 retention, expansion, winback rate).
Output Format
Lifecycle / CRM Plan: [product]
1. Lifecycle map — the stages and the one behaviour you want at each (signup → activate → habit → expand → renew; with winback for lapsed).
2. Journey table — the core deliverable:
| Journey |
Trigger (behaviour, not date) |
Audience/segment |
Message & goal |
Channel |
Timing |
Success metric |
Exit/suppression |
| Onboarding |
signed up, not activated |
new, no key action |
get to first value |
email + in-app |
t+0, t+1d, t+3d |
activation % |
activated → exit |
| Winback |
inactive 30d |
was active |
reason to return |
email |
t+30, t+37 |
reactivation % |
returned → exit |
3. Segmentation — the few segments that change the message (by behaviour/value, not vanity demographics).
4. Timing & frequency — cadence rules and a global frequency cap / suppression so journeys don't collide or fatigue.
5. Measurement — per-journey metric, holdout group to prove incrementality, and the deliverability guardrails (bounce/spam/unsub watch).
Quality Checks
Anti-Patterns
Based On
Lifecycle marketing / behavioural CRM practice — trigger-based journeys, segmentation, and incrementality testing with holdouts.
1---2name: lifecycle-crm-plan-23description: "Design lifecycle marketing / CRM journeys across the customer lifecycle. Use when asked to plan onboarding emails, lifecycle/CRM campaigns, drip sequences, re-engagement or winback flows, or a messaging calendar. Produces a lifecycle plan — stage map, the trigger/message/goal for each journey, channel & timing, segmentation, suppression rules, and success metrics."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/lifecycle-crm-plan.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/lifecycle-crm-plan-27 openclaw:8 emoji: 📈9---1011# Lifecycle / CRM Plan Skill1213Lifecycle marketing is the difference between a product people sign up for and one they actually use.14This skill maps the customer lifecycle to triggered journeys — each with a clear job — so messaging is15behaviour-driven and purposeful, not a batch-and-blast newsletter that trains people to ignore you.1617## Required Inputs1819Ask for these only if they aren't already provided:2021- **Product & lifecycle stages** — what the journey from signup → active → loyal → churned looks like.22- **The key moments** — activation milestone, the "aha", upgrade triggers, and churn signals.23- **Channels available** — email, push, in-app, SMS — and any consent/deliverability constraints.24- **Goal** — the lifecycle metric to move (activation %, D30 retention, expansion, winback rate).2526## Output Format2728### Lifecycle / CRM Plan: [product]2930**1. Lifecycle map** — the stages and the one behaviour you want at each (signup → activate → habit → expand → renew; with winback for lapsed).3132**2. Journey table** — the core deliverable:3334| Journey | Trigger (behaviour, not date) | Audience/segment | Message & goal | Channel | Timing | Success metric | Exit/suppression |35|---|---|---|---|---|---|---|---|36| Onboarding | signed up, not activated | new, no key action | get to first value | email + in-app | t+0, t+1d, t+3d | activation % | activated → exit |37| Winback | inactive 30d | was active | reason to return | email | t+30, t+37 | reactivation % | returned → exit |3839**3. Segmentation** — the few segments that change the message (by behaviour/value, not vanity demographics).4041**4. Timing & frequency** — cadence rules and a **global frequency cap / suppression** so journeys don't collide or fatigue.4243**5. Measurement** — per-journey metric, holdout group to prove incrementality, and the deliverability guardrails (bounce/spam/unsub watch).4445## Quality Checks4647- [ ] Journeys are **behaviour-triggered**, not date-batched48- [ ] Every journey has an explicit goal, success metric, and exit condition49- [ ] A global frequency cap / suppression prevents message collisions and fatigue50- [ ] A holdout group is used to measure incrementality, not just open/click rates51- [ ] Segmentation is based on behaviour/value, not vanity attributes5253## Anti-Patterns5455- [ ] Do not batch-and-blast — untriggered, irrelevant sends train users to ignore and unsubscribe56- [ ] Do not measure success by opens/clicks alone — tie journeys to the lifecycle outcome (activation, retention, revenue) with a holdout57- [ ] Do not forget exit conditions — a user who already activated should not keep getting "activate now" emails58- [ ] Do not ignore frequency capping — overlapping journeys are how you fatigue and burn a list59- [ ] Do not skip deliverability guardrails — a great journey in the spam folder reaches no one6061## Based On6263Lifecycle marketing / behavioural CRM practice — trigger-based journeys, segmentation, and incrementality testing with holdouts.