Intern
What you actually do
Grid and the first-yes test. What mails a new buyer. You are naming clocks, not designing a VIP brand.
Library / System / Lifecycle is named states with a next move after the first yes
Lifecycle as a slide (acquire, convert, retain) is a workshop. Lifecycle as an operating layer is a data model: who just bought, who should buy again, who is lapsing, who is subscribed, who refunded — each with a next move and a stop. Coaches feel this as re-enrollment and delivery. DTC feels it as second order and replenishment. The software can be GHL or Klaviyo. The leak is the same: acquisition keeps spending because 'retention will cover it', and nobody can name the second yes.
Lifecycle as a slide (acquire, convert, retain) is a workshop. Lifecycle as an operating layer is a data model: who just bought, who should buy again, who is lapsing, who is subscribed, who refunded — each with a next move and a stop. Coaches feel this as re-enrollment and delivery. DTC feels it as second order and replenishment. The software can be GHL or Klaviyo. The leak is the same: acquisition keeps spending because 'retention will cover it', and nobody can name the second yes.
Define lapse in days for your offer. 45-day coffee and 400-day mattress are different clocks. 'We miss you' without a clock is a mood.
Day 0–7 after payment predicts completion and second purchase more than the next ad campaign. Access, use, kickoff, shipping truth — those are lifecycle, not 'onboarding extras'.
Second-yes is the number: second order, re-enrollment, membership renewal. If you cannot name it, you do not have LTV. You have a hope with a formula.
Acquire campaigns that include recent buyers and subscribers are how you pay to discount your own economics.
CS and email must share the state. A win-back email while CS is mid-complaint is how you look automated in the worst way.
Intern
Grid and the first-yes test. What mails a new buyer. You are naming clocks, not designing a VIP brand.
Operator
States with next moves. One second-yes path. Finite lapse. Share state with CS. One lapse definition.
CEO
Economics change after the first yes only if someone owns the second. Second-yes is the number. Until it exists, LTV is a slogan.
State (new buyer, repeat, lapse, member/subscriber, refunded, alumni), clock (days since event), next move, stop rule, owner (email/CS/AM), second-yes metric.
First yes (paid / enrolled / member) → leave acquire; start day-0–7 designed as product
Clock hits replenish/re-enroll window → one journey, not a blast to all buyers
Lapse definition met → finite win-back; then stop
Refund/churn → not acquire; not VIP
One page: states, entry event, clock, next move, stop. Coach vs DTC language differs; the grid does not.
Why: Slides without clocks are decoration.
Done when: Lapse days written. Second-yes defined.
Paid/enrolled writes the state in GHL or Klaviyo. Acquire stops. Day-0–7 sequence exists.
Why: If first yes does not change state, every later journey is a guess.
Done when: Test purchase/enroll leaves acquire the same day.
One journey: replenishment, attach, re-enroll, or renewal. Not five. Properties/fields that journey needs must exist.
Why: A 'retention program' with six ideas is how none ship.
Done when: One path live. A test profile in-window gets it; out-of-window does not.
Win-back with a last look. Then suppress. Do not run win-back as a personality.
Why: Forever we-miss-you is acquire in a sad font.
Done when: A lapsed test stops after the last step.
Second orders / renewals / re-enrolls this week vs first yes last period. One action on the clock, not on a new ad account.
Why: Acquisition meetings will eat this slot unless the number is on the wall.
Done when: Second-yes is a defended number. Hold or act.
Draft the state grid. Confirm first yes flips acquire off. List what currently mails a new buyer (probably too much). Ship or fix day-0–7. Define lapse days. Do not start a 'loyalty program' brand.
Another acquisition channel or a loyalty points vendor until second-yes is named and one post-first-yes path exists. Points on a missing clock are a discount with extra steps.
Lifecycle on a slide. Welcome coupon. Win-back forever. Day-0–7 is a PDF. Renewals are a panic. LTV in a deck. That is acquire with a vocabulary upgrade.
State grid. First yes exits acquire. One second-yes journey. Finite lapse. Monday second-yes number. CS can see why a person is in a state.
Email is a channel. State is the layer. Delivery, CS, access, and dunning all write state. Email without state is a calendar.
Later is how CAC rises while second-yes stays accidental. The layer is cheap to name now. The journeys can be one path, not a department.
DTC product: Klaviyo states. Coach/academy delivery: GHL states. Some operators need both, with one identity. Do not run two lapse definitions.
This week
This week: state grid, first-yes flip, day-0–7, lapse days, one second-yes path. No new acquire channel.
Until stages, fields, and write-in have owners, the sub-account is a filing cabinet.
Read ↗If every automation can fire, none of them is an operating system.
Read ↗If the thank-you does not change the contact, you paid for a brochure.
Read ↗Broadcasts feel like work. A spine with manners is the product.
Read ↗Working notes
Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.