Lesson 78.1 earned the opt-in with a clear promise. What happens in the next seven days decides whether that promise becomes a habit. New subscribers are at peak attention and zero orientation: they do not know where to start, what you expect of them, or whether you will flood them. A welcome sequence answers all three — a short series that delivers first value fast, routes each person correctly, and invites a reply.

The vocabulary, in plain language

• Welcome sequence (onboarding): the first few emails a new subscriber receives automatically, in order, before they join the normal rhythm.
• Expectation: what the reader learns to count on — cadence, shape, how to get help, how to leave.
• First value: the smallest useful win you can deliver within days — a checklist used, a sample brief opened, a booking made.
• Preference: a choice the reader makes that lets you segment — beginner versus active builder, local versus remote.
• Reply prompt: an explicit invitation to answer as a human. Replies train the inbox to trust you and give you Lesson 77.4 listening material.

Think of the ByeBuy course map as the model. A new learner should not receive every lesson link at once — that is a flood, not a welcome. They should be routed: "start here based on what you are building," then one best resource, then one template, then a question that sorts them, then the normal Tuesday note. Routing beats dumping.

The five-message shape

Keep it to five. Each message has one job, one link or action, and a reason for its timing:

1. Welcome — why this exists (day 0, immediately). Restate the promise, set expectations (day, shape, reply welcome), give the single best starting link. Subject plain: "Welcome — here is what arrives Tuesdays." No selling.

2. Best starting resource (day 1–2). The most-saved, most-forwarded thing you own — the checklist, the sample brief, the map. One link, one sentence on how to use it in ten minutes. First value lands here or the sequence has failed.

3. Useful use case or template (day 3–4). Show the resource solving one real job: the filing check on a live example, the tailor's care card for the garment just bought. Template attached or linked, with a filled example beside the blank.

4. Question and preference (day 5–6). Ask one sorting question and make answering effortless: reply with a letter, tap a two-option link, pick beginner or active. "Are you (A) learning the method or (B) running briefs weekly? Reply A or B — I read every answer." Every reply segments the next message honestly.

5. Bridge to the rhythm (day 7). Hand off to the normal cadence: what arrives next Tuesday, where the archive lives, how to get help, how to leave. From here the subscriber joins the regular calendar (Lesson 78.3) — no more special series.

Timing rationale: front-load value while attention is hot, then slow down. Days 0–2 carry the promise; days 3–6 earn the reply; day 7 normalizes. Never send all five on day zero, and never stretch onboarding over a month — attention decays and the regular issues start feeling like duplicates.

One link, one action, one voice

Each message obeys the Lesson 77.2 discipline: one idea, one demonstration, one next step. The welcome email links the start page — not the start page plus the blog plus the shop plus the referral program. The template email links the template — not three templates and a survey.

Voice stays human throughout. Write from a person, sign with a name, invite replies, and actually read them for the first hundred subscribers. A founder-read inbox beats a branded "noreply@" by every measure that matters: replies, saves, forwards, and the qualitative signal that tells you which onboarding step confuses people. Automation handles the sending order; it never handles the relationship.

Segment lightly from the answer to message 4. New learners get the beginner follow-up (Lesson 78.3's educational send); active builders get the product follow-up; locals get hours and booking. Two branches are enough to start. Ten branches with no one maintaining them is how welcome sequences rot into contradiction.

Exercise: draft the five-message outline

Create WELCOME-SEQUENCE.md with subject, purpose, action, and timing rationale for each send.

# WELCOME-SEQUENCE.md — [Project], promise: [one sentence from 78.1]

## Email 1 — Welcome (day 0, immediately after signup)
- Subject: ___
- Purpose: restate promise + expectations + reply invite
- One link/action: [start page]
- Why now: ___

## Email 2 — Best resource (day ___)
- Subject: ___
- Purpose: deliver first value in 10 minutes
- One link/action: ___
- Why now: ___

## Email 3 — Use case / template (day ___)
- Subject: ___
- Purpose: show the resource solving one real job
- One link/action: ___
- Why now: ___

## Email 4 — Question / preference (day ___)
- Subject: ___
- Purpose: segment + earn a reply
- Question + answer mechanism (reply letter / 2 links): ___
- Branch A → ___ / Branch B → ___

## Email 5 — Bridge to rhythm (day ___)
- Subject: ___
- Purpose: hand off to normal cadence + archive + exit reminder
- Next issue teaser: ___

Worked mini-example — local product release (ceramics shop, weekly kiln note): 1) welcome + "kiln opens Fridays" promise; 2) care card for the piece just bought; 3) template — "three shelves that fit small apartments" with photos; 4) "A) browsing or B) furnishing now? Reply A/B"; 5) "Friday's note holds two seconds-request pieces — archive here, leave anytime." Each branch routes to the right Lesson 78.3 send.

Finish line: a WELCOME-SEQUENCE.md with five subjects, five single actions, timing rationale, and the branch rule from message 4.

Verify quickly: send all five to yourself over five days. Did you open each for a distinct reason, complete each action in under ten minutes, and know what arrives next? If two emails feel interchangeable, merge them and keep the sequence to four — brevity that delivers beats length that blurs.

Common failure mode: the link avalanche — email 1 contains twelve links "so nothing is missed." Everything is missed. One email, one door.

Check your understanding

1. What job does each of the five welcome messages do, and why does order matter? 2. Why must message 2 deliver first value within days? 3. How does message 4's reply turn into segmentation without building ten branches?

Next

New readers are oriented. Lesson 78.3 gives the ongoing calendar its discipline — launch, educational, update, and re-engagement sends, each with its own job, segment, and success signal.