LotsSocial has no subscribers yet. So today is a design exercise on a realistic user journey — you are building what will run when the first signup arrives, not something that sends this week. That is deliberate: this is the one channel you cannot bolt on afterwards, because by the time you have signups it is already too late to have welcomed them.
Every other channel rents your audience. Search can derank you, a platform can cut your reach to nothing, a community can decide it is done with you. Email is the one place where the person chose to hear from you and no feed decides who sees it. That privilege is also the constraint.
- Owned, with an asterisk.
- Lifecycle, not broadcast.
- Three questions every email has to answer.
- The welcome sequence leads to the value moment, not a feature tour.
- The sequences worth building, in order of return.
- Restraint is the job.
- Honour the exit.
- Courier — and the boundary that protects the whole channel.
- What this did not cover, and how to go deeper.
1. Owned, with an asterisk.
Day 9 put email in the owned column, and that is right in the way that matters: nobody can algorithm you out of an inbox.
But "owned" oversells it. You hold the address, not the attention. Permission can be withdrawn in one click. Deliverability is decided by mailbox providers who do not answer to you. And a list that is mailed badly stops being an asset long before anyone unsubscribes — it simply stops being opened.
So the accurate version: the one channel where reaching someone does not depend on an algorithm, for exactly as long as they let you. Everything below follows from taking that seriously.
2. Lifecycle, not broadcast.
The default instinct is broadcast — write something, send it to everyone, repeat weekly. It is easy, it feels like activity, and it is how most lists die.
The alternative is lifecycle: emails triggered by what someone did or did not do.
| Broadcast | Lifecycle | |
|---|---|---|
| Trigger | The calendar | The person's behaviour |
| Relevance | Same to everyone, right for few | Right for the person receiving it |
| Effort | Every week, forever | Written once, runs for years |
Written once and running for years is the part people miss. A welcome sequence built properly in September is still working in June without anyone touching it. That is the closest thing to compounding that email offers.
3. Three questions every email has to answer.
If any of the three has no good answer, the email should not exist.
1. Why is this person receiving this? Name the behaviour or state that triggered it — signed up and never activated, activated but not paying, cancelled last week, asked for the thing that just shipped. If you cannot name it, it is a broadcast.
2. What is the one thing they should do? One action, one link. A second link competes with the first.
3. What happens if they ignore it? If the honest answer is "nothing", the email has no reason to be sent.
That third question is the one that kills most drafts, and it should. Most emails companies send fail it and get sent anyway — which is why most inboxes look the way they do.
4. The welcome sequence leads to the value moment, not a feature tour.
Every product has a moment where the person first gets something real out of it. For a social tool it is not signing up or connecting an account — it is the first post going out and looking right without them fighting it.
The welcome sequence has exactly one job: get them to that moment. Not to explain the product. Not to tour the features. To remove whatever is between the person and the thing that makes the product obvious.
Which means the sequence is built backwards from the value moment, and each email earns the next one. If email one does not get read, email two is irrelevant — so email one is not an introduction to your company, it is the shortest path to the first useful thing.
Three or four emails is usually right. The temptation is always more.
5. The sequences worth building, in order of return.
| Sequence | Trigger | Job |
|---|---|---|
| Welcome / onboarding | Signup | Reach the value moment |
| Activation nudge | Signed up, stopped at a specific step | Help with that step, not a general reminder we exist |
| Conversion | Getting real value, not paying | Prompt at the moment paying is obviously worth it |
| "You asked for this" | A requested feature ships | Tell the people who asked that their suggestion caused it |
| Win-back | Cancelled, and something has genuinely changed | Once. Not a discount reflex. |
The fourth one is the most underrated email in software and costs nothing. Someone asked for a thing, you built it, you tell them their request caused it. It converts, and more importantly it makes people believe there is a person on the other end — which is the thing every other email is trying and failing to fake.
6. Restraint is the job.
The instinct is always to send more. Everything about the channel rewards resisting it.
Fewer, better sends. Every email spends attention you cannot get back. A list mailed weekly with nothing to say is being spent down.
Never fabricate urgency. A deadline that is not real gets noticed, and it is remembered longer than the offer.
Never quote a price from memory. Fetch it from the live source or link to the pricing page. A wrong price in an email is a promise you now have to honour or retract.
Never say something was sent when it was prepared. Drafted is not sent. This matters more with agents in the loop, and it is worth checking rather than assuming.
7. Honour the exit.
Unsubscribe is one click, honoured immediately, never guilt-tripped. No "are you sure?", no "you'll miss out", no three-step confirmation.
This is partly decency and mostly self-interest. Someone who cannot leave easily marks you as spam instead — and spam complaints are the thing that damages your ability to reach everyone else. A hard unsubscribe is not a retained subscriber. It is a complaint waiting to happen.
Two related rules. Reply-to should reach a person. A do-not-reply address on lifecycle email announces the relationship is one-way, which is a strange thing to say to someone you want to keep. And a suppression list is not a suggestion — if someone left, they left.
8. Courier — and the boundary that protects the whole channel.
Courier owns email to people who already gave you their address. Its defining rule is a boundary:
Envoy talks to strangers. Courier talks to our list. A cold prospect is never Courier's, and a subscriber is never Envoy's.
That sounds like tidy organisation. It is actually protection. Mailing your existing users from a cold outreach system is how a sending domain and a reputation get destroyed at the same time — one is warm, permissioned, and expected; the other is not. Mixing them contaminates the first with the risk profile of the second.
Courier is built around the three questions from section 3, carries the restraint rules from section 6, and will not quote a price it has not fetched. When a request involves people who never opted in, it hands it to Envoy rather than doing it anyway.
That is the pattern you have now seen across the fleet: every agent is defined as much by what it refuses as by what it does. Tomorrow's is the one with the most to refuse.
9. What this did not cover, and how to go deeper.
Not covered:
- Deliverability infrastructure — SPF, DKIM, DMARC, warming, one-click unsubscribe headers. Tomorrow touches it; properly it is its own subject.
- Newsletters as a channel — a different thing from lifecycle email, with its own economics.
- Segmentation at scale — once a list is large enough to divide meaningfully.
- Design and templates — plain text usually beats a designed email for lifecycle, and people find that hard to believe.
- Testing — subject lines, timing, sequence length.
- Legal — consent, GDPR, CAN-SPAM. Real obligations, not best practice.
Where to go. Sign up for three products you admire with a fresh address and read what arrives over two weeks. You will learn the shape of a good sequence faster from four real ones than from any explanation, including this one.
Today’s task — design the LotsSocial welcome sequence (60 min)
Objective: get a new signup to the value moment.
Evidence: your Day 8 ICP, your Day 7 research on what stops people.
Deliverable: three emails, defined by trigger, plus the value moment named.
Review: Editor and your own checklist.
Signal: what would tell you the sequence worked — and it is not opens.
1. Name the value moment (10 min)
One sentence: what is the first moment a LotsSocial user gets something genuinely useful? Be specific. "They see the value" is not an answer; "their first post publishes to three platforms and reads right on all of them without editing" is.
Everything below is built backwards from that sentence.
2. Design three emails, each by its trigger (35 min)
Use these three triggers — they are the real ones for this product:
- Signed up, has not connected any account.
- Connected an account, has not created a post.
- Published once, then went quiet for a week.
For each, define all eight:
trigger · timing · what state the person is in · purpose · the one action · what you will deliberately not say · success signal · what happens if they ignore it
Then write the email. Subject line and body. Short.
3. Apply the third question honestly (10 min)
For each of your three: what happens if they ignore it?
If the honest answer for any of them is "nothing", say so and cut it. Submitting two emails with a note explaining why the third should not exist is a better answer than three.
4. One line on measurement (5 min)
What single number tells you this sequence is doing its job? Not opens, not clicks — something closer to the value moment.
Then run it through the gate
Editor and your checklist. Nothing sends — there is no list, and there would be nothing to send to.
Then post one line
In #daily-log: your value moment sentence.
Nine different answers to that question will be more useful to me than nine sequences, because it is the thing the whole product has to be built around and I want to see where you each land.
Tomorrow — Day 16: Outreach. Writing to people who have never heard of us. The channel that works before you have an audience — and the one with the most ways to do real damage.