Lesson 87.3 gave you a memory — requests, promises, preferences, next steps. Now that memory must act at the right moments. The new customer's first week, the trial user one step from value, the member whose renewal nears: each deserves help that arrives with progress. And each deserves silence the moment it stops applying. That is the whole lesson.

The vocabulary, in plain language

• Onboarding: help that gets a new user to first value — setup, first project, first win. Measured in days, not quarters.
• Activation: the moment they first succeed meaningfully — worksheet run, first deploy, first report shared. Everything before it serves this.
• Nurture: useful contact with someone not yet ready — the monthly check, the relevant guide. Nurture feeds; it never chases.
• Renewal: the run-up to a continue-or-leave decision — reminder, value summary, easy path. Surprises at renewal are betrayals.
• Reactivation: a genuine reason to return for someone gone quiet — a fixed pain, a new relevant capability. Not "we miss you" on a timer.
• Transactional message: expected mail about their account — receipts, confirmations, password resets, delivery notices. Always allowed, always plain.
• Marketing message: optional persuasion — campaigns, offers, announcements. Allowed only inside consent (Class 78, Lesson 87.3).

The mental model: lifecycle mail is a hiking guide, not a helicopter. It meets walkers where the trail forks — the first ascent, the viewpoint, the junction near the end — points at the right path, then steps aside. A helicopter hovering overhead shouting encouragement is spam with good intentions.

Trigger at progress, exit on time

Two rules govern every lifecycle message:

Rule 1: trigger at a progress moment. Each message fires on something the person did or a date that matters to them — account created, first project shipped, trial day 5 with no activation, renewal in 21 days, quiet for 90 days after a resolved ticket. "Tuesday, to everyone" is never a trigger. The CRM stage plus the activity record (Lesson 87.3) decides who qualifies — which is why lifecycle without a maintained CRM becomes blasting.

Rule 2: exit the moment it stops applying. Every flow names its exits: activated, converted, unsubscribed, bounced, replied "not now," moved stage, completed the sequence's job. Entered onboarding and already deployed on day 2? Exit immediately with congratulations, not emails 3 through 7. Renewed early? The reminder sequence dies that hour. Exits are checked before every send, not evaluated monthly.

Walk it with ByeBuy. Onboarding: account created → three short notes (day 0: run the first worksheet; day 3, only if none run: the 10-minute guided version; day 7, only if still none: the office-hours invite) — exit on first worksheet completed. Activation triggers nurture: monthly "one check from your track" while subscribed. Renewal for team seats: value summary at 21 days, plain reminder at 7, receipt as transactional on the day. Reactivation once per quiet spell: "the export bug you hit (#118) is fixed — here is the one-click retry," then silence. Each flow has an owner who reads replies as well as sends.

Exercise: map the lifecycle

Create LIFECYCLE-MAP.md. One row per moment — each with its trigger, message, exit, and owner. Start with five rows; add more only when a stage earns its own flow.

# LIFECYCLE-MAP.md — [Project]

| Moment | Message (one line) | Trigger (progress, not calendar) | Exit (stop when) | Owner |
|--------|--------------------|----------------------------------|------------------|-------|
| Onboarding 1 | ___ | account created + ___ | activated / unsubscribed / ___ days | ___ |
| Onboarding 2 | ___ | still no ___ at day ___ | activated / replied / unsubscribed | ___ |
| Nurture | ___ | stage ___ + quiet ___ days + consent ___ | converted / opted out / stage moved | ___ |
| Renewal | ___ | renewal in ___ days + plan ___ | renewed / cancelled / expired | ___ |
| Reactivation | ___ | quiet ___ days + genuine reason ___ | returned / declined / one send then stop | ___ |

## Transactional vs marketing check
- These sends are transactional (always allowed): ___
- These need live consent (checked where before each send): ___
- Reply handling: replies go to ___ within ___ hours (never no-reply for lifecycle)

Worked mini-example — local studio: onboarding "booking confirmed → prep note 48h before (trigger: booking + 2 days out; exit: visit done)"; nurture "quarterly care tip to past visitors with consent (trigger: visit + 60 days; exit: rebooked or opted out)"; renewal "membership in 21 days → visits-this-year summary (trigger: date + plan; exit: renewed/cancelled)"; reactivation "the Saturday slot you asked about reopened (trigger: asked + slot free; exit: booked/declined/one send)." Replies route to the front desk within 4 hours.

Finish line: a LIFECYCLE-MAP.md with five moments, progress-based triggers, explicit exits, consent checks, and named owners.

Verify quickly: for each row, name one person who qualifies today and one who must be excluded by the exit. If the exit excludes nobody, it is decorative — rewrite until it bites.

Common failure mode: the immortal drip — onboarding emails 1–9 sent to everyone including the activated, the cancelled, and the unsubscribed-except-nobody-checked. Engagement sinks, complaints rise, and the team concludes "email doesn't work." Email works; exits were missing.

Check your understanding

1. What distinguishes a transactional message from a marketing message, and why does it matter per send? 2. State the two lifecycle rules in your own words. What breaks when each is violated? 3. Why must exits be checked before every send rather than reviewed monthly?

Next

Messages arrive on time and stop on time. The final lesson closes the loop: recurring support evidence becomes product backlog and documentation, and you prove the improvement in fewer future tickets.