Where we are in the Cadence campaign
You have positioning (b2), a content engine (b3), search (b4), and paid ads (b5) bringing people to Cadence. Now what? A signup that never activates is a wasted acquisition. Lifecycle email is the cheapest, most controllable channel you have to move someone from "signed up" to "uses it every day" to "upgraded to Teams". AI can draft every message - but the journey map and the data are yours.
Lifecycle: the right message at the right moment 6 min live
Lifecycle marketing is one idea: meet people where they are. A brand-new signup needs a different message than a power user who has not upgraded. Map the journey, decide what each stage needs to hear, and let a trigger send it at the moment it is relevant. AI drafts the messages; you own the map and the data behind it.
LiveMap the journey before you write a word3 min▶
The mistake is writing emails first. Map the journey first: what stage is the person in, what do they need to do next, and what message moves them there. Then a "trigger" - an event like "signed up" or "recorded first meeting" - sends the right message automatically.
- Signup -> activation. The riskiest gap. Someone signed up but has not felt the value yet. Get them to their first real win fast (for Cadence: notes from a real meeting).
- Activation -> upgrade. Once they get value on the free solo plan, show the Teams benefit at the moment it is relevant - not on day one.
- Retention. Keep active users active; re-engage the ones going quiet before they churn.
- You own the strategy and the data; AI drafts the copy. The model does not know your funnel - you do.
Self-studyTriggers vs blasts2 min read▶
- A blast goes to everyone at once - fine for a genuine announcement, weak for moving people through a journey.
- A triggered email fires on an event or delay ("2 days after signup with no meeting recorded"), so it lands when it is relevant.
- Lifecycle is mostly triggered. The value is relevance: the right message at the right moment beats the same message to everyone.
- AI helps design the trigger logic too - ask it to propose triggers for each stage - but you validate them against your real product events.
Segmentation + personalization without the creep 5 min live
Personalization works when it feels helpful and fails when it feels like surveillance. AI can help you segment by stage, behavior, and persona and tailor each message - but only on data people consented to share. Cadence solo and Cadence Teams are different audiences with different needs, and that is where good segmentation starts.
LiveSegment by stage and persona, personalize with consent3 min▶
Good segmentation is about relevance, not data hoarding. Split by where someone is (stage), what they have done (behavior), and who they are (persona: solo user vs team admin). Then tailor the message - and use only consented first-party data to do it.
| Segment | Message angle |
|---|---|
| New signup, no meeting yet (solo) | Get to your first automatic note fast - here is the one step |
| Active solo user, not upgraded | You are getting value alone; here is what Cadence does for a whole team |
| Team admin evaluating Teams | One shared source of truth for decisions and action items |
| Was active, now quiet | Gentle re-engage: what you missed, one reason to come back |
The personalization that crossed the line. A brand referenced behavior a user never agreed to share, and the "helpful" email read as creepy - unsubscribes spiked. Personalization built on non-consented data is not just a legal risk under GDPR/PDPA, it damages trust. Consent first, always.
Self-studyRail two for email - the consent checklist2 min read▶
- Consented first-party data only. Personalize with what people gave you, for the purpose they agreed to - not scraped or inferred data.
- Respect GDPR and PDPA. Clear opt-in, easy opt-out, honour unsubscribes immediately.
- Never paste customer PII into a consumer AI tool. Draft with placeholders ([first name], [company]); the real merge happens in your ESP.
- The comfort test. "Would this personalization feel helpful or creepy to the person receiving it?" If creepy, do not send it.
Subject lines + testing 4 min live
The subject line decides whether any of your work gets read. AI generates variants in seconds - the discipline is the same as paid: test one thing, pick one metric, respect deliverability. No spammy tricks that get you opened once and filtered forever.
LiveGenerate variants, test one thing, protect deliverability2 min▶
- Generate widely. Ask AI for ten subject-line variants in different styles: benefit, curiosity, specific, short.
- Test narrowly. Pick two, change only the subject line, keep the email body identical, measure open rate.
- Respect deliverability. No all-caps, no "FREE!!!", no fake "Re:" tricks. A subject that beats the spam filter matters more than one that wins a single test.
- Watch the whole funnel. A high open rate that does not lead to the next step is a vanity win - tie it back to activation or upgrade.
Self-studyDeliverability quick rules2 min read▶
- Avoid spam triggers. Excessive caps, exclamation marks, and money words push you toward the spam folder.
- Be honest. The subject must match the email. Clickbait that misleads trains people to ignore you.
- Send to people who want it. Clean your list; high bounce and complaint rates hurt every future send.
- Test length and personalization. Short vs descriptive, [first name] vs none - but change one at a time.
Draft the Cadence welcome/activation sequence ★ 13 min · everyone builds
Build a 3-email welcome and activation sequence from the positioning brief, tailored to solo vs Teams. AI drafts every email; you own the journey logic and keep it consent-safe with placeholders, not real PII.
Open any chat AI. Paste your Cadence positioning brief and the lifecycle map: signup -> activation, and the one next step at each stage.
Ask for a 3-email sequence: (1) welcome + fastest first win, (2) activation nudge to record a real meeting, (3) show the value they are getting and hint at Teams.
Ask for two variants of the sequence: one for a solo user, one for a team admin - same journey, different emphasis.
Use placeholders only: [first name], [company]. No real customer data goes into the chat tool (rail two).
Edit for voice and truth. Cut any claim you cannot back; the model does not know your product numbers.
Subject-line variants + a simple A/B test plan ★ 8 min · build your own
Generate a batch of subject-line variants for the welcome email, then structure a clean test: one variable, one metric, one decision rule. Same rigour as the paid test in b5.
Take the welcome email from demo 1. Ask AI for eight subject-line variants across styles: benefit, curiosity, specific, short.
Screen them for deliverability: cut anything with all-caps, excess punctuation, or a misleading promise.
Pick two that differ in one dimension - for example, benefit vs curiosity - keeping the email body identical.
Choose one metric: open rate to test the subject itself, or click/activation if you care about the whole funnel.
Write the decision rule before sending: what open-rate margin makes you keep the winner, and how big a send you need first.
The subject line that opened but never converted. A team picked the highest open-rate subject and celebrated - but it was a curiosity gap that oversold, and almost no one took the next step. When they tied the test to activation instead of opens, a plainer, honest subject won. Match the metric to the goal, not to the ego.
Try it yourself - this week ◐ 30-45 min total
- Finish both tailored welcome sequences (solo and Teams) if you did not complete them live, editing every line for voice and truth.
- Map one more stage of the Cadence lifecycle - the upgrade or the retention/win-back moment - and draft the trigger and message for it.
- Build a subject-line A/B plan for one real email you send: one variable, one metric matched to the goal, a written decision rule.
- Run the consent check on your own email program: is every personalization built on data people agreed to share? Note any gap.
- Draft your emails with placeholders only. Confirm the real merge happens in your ESP, never in a consumer AI tool.
Official sources covered
Taught from public AI-marketing curricula and vendor documentation. Certificates and paid tooling stay with the official programs. This session covers:
Three questions before you go 🎯 ◐ 90 seconds
1 · What is the core idea of lifecycle email?
Lifecycle is about relevance: map the journey (signup -> activation -> upgrade -> retention), decide what each stage needs, and trigger that message when it matters. AI drafts it; you own the map.
2 · You want to personalize a Cadence email. What data is acceptable to use?
Rail two. Personalize only with consented first-party data under GDPR/PDPA, and never paste customer PII into a consumer AI tool - draft with placeholders. Helpful, not creepy.
3 · You are A/B testing a subject line. What is the discipline?
Subject-line tests are A/B tests: one variable, one metric, a decision rule set in advance - and no spammy tricks that hurt deliverability. Match the metric to the goal, not to opens alone.