ByeBuy.ai
BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY · BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY ·
CURRICULUM
← BYEBUY NOTES

September 13, 2026

LAUNCH, UPDATE, AND EDUCATIONAL EMAIL HAVE DIFFERENT JOBS

ByeBuy.ai artwork for Launch, Update, and Educational Email Have Different Jobs

Lessons 78.1 and 78.2 built the relationship and the onboarding. Now the weekly question: what do we send Tuesday? Beginners send "something" — a mixed update-launch-apology that fits nobody. Working builders send one of four email types, each with its own job, segment, and measure. This lesson teaches the four, the matching rule that keeps them honest, and a four-send calendar you can actually hold.

Four jobs, four shapes

  • Launch email — act now on something time-bound. A release, a booking window, a cohort, a limited run. Shape: the offer in the first three lines (what, when, availability, price or condition), proof fast, one action, deadline stated once. Success signal: completions — bookings, orders, signups — not opens.
  • Educational email — learn something useful even if you never buy. One taught idea with evidence: a filing check, a care method, a workflow. Shape: question → demonstration → template or checklist → soft pointer to the product that makes it easier. Success signal: saves, forwards, replies, clicks to the resource.
  • Product update — use what you already have better. New feature, changed hours, fixed friction. Shape: who it affects, what changed, what to do differently, where to get help. Sent to people the change touches — not the whole list. Success signal: adoption or avoided confusion (fewer support notes).
  • Re-engagement note — check whether the relationship still fits. For readers silent 60–90 days. Shape: short, human, one question plus an easy exit. "Still want the Tuesday filing check? Reply YES to stay, or leave here — no hard feelings." Success signal: honest replies plus clean unsubscribes. A smaller, willing list beats a large, silent one.

Mixing jobs is the standard failure. A launch buried inside a three-section newsletter ("news, tips, and oh — kiln opens Friday") asks the skimmer to excavate the deadline. A lecture inside a launch ("first, the history of ceramics…") asks the buyer to study before acting. One send, one job.

Message match plus beginner segmentation

Message match means the email continues its own premise: subject, opening, proof, action, and destination all serve the same job. A subject promising "two Friday rush slots" must open on slots, show the booking proof, and link the booking page — not the homepage, not the about story. Lesson 72.2's landing-page rule applies inbox-side: every extra scroll between promise and action costs completions.

Segmentation at beginner level needs only two cuts:

  • New versus active. New learners (from the Lesson 78.2 branch) get educational sends and orientation pointers. Active builders or customers get launches and updates tied to what they already use. A new learner who receives "v2 migration notes" learns only that this list is not for them.
  • Interested versus silent. Readers who opened or clicked recently can receive the launch; the long-silent get the re-engagement note first, not the hard pitch. Pitching the silent teaches spam filters, not people.

Two segments, honestly maintained, outperform six imagined personas in a spreadsheet nobody queries. Tag by behavior you can observe (signup source, branch answer, purchase or booking, recent engagement) — not by guesses about personality.

Local release: four sends in order

Take the ceramics shop's small Friday kiln release as the reusable pattern:

1. Educational (Tuesday prior): "Three small-shelf pieces that survive apartment moves" — photos, care notes, template. Segment: whole willing list. Destination: guide page. Signal: saves and replies naming a favorite. 2. Preview / launch (Friday 9am): "Kiln opens at noon — 14 pieces, two already reserved" — first lines carry count and time, three photos, one booking link. Segment: engaged plus local. Signal: reservations by 6pm. 3. Customer follow-up / update (Sunday): only to buyers — "your piece, its care card, and pickup hours." Shape: gratitude, care, pickup path, help contact. Signal: smooth pickups, zero "where do I go?" replies. 4. Re-engagement (following month, to the silent): "Still want Friday first-looks? Reply STAY or leave here." Short, signed by the owner. Signal: stays, honest exits, two replies that become the next educational topic.

Notice the order: teach → invite → serve → prune. Each send's destination matches its job, each segment matches its readiness, and the silent are asked rather than shouted at.

Exercise: calendar four sends, not "send something"

Create EMAIL-CALENDAR.md with four sends across the next 30 days. Each row names its job, segment, destination, and signal.

# EMAIL-CALENDAR.md — [Project], next 30 days

## Send 1 — Educational
- Subject working title: ___
- Segment: ___ / Destination (exact link): ___
- Job in one line: ___
- Success signal + target: ___

## Send 2 — Launch
- Subject working title: ___
- Segment: ___ / Destination (exact link): ___
- Availability/deadline stated: ___
- Success signal + target: ___

## Send 3 — Update
- Subject working title: ___
- Segment (only affected): ___ / Destination: ___
- What changes for the reader: ___
- Success signal: ___

## Send 4 — Re-engagement
- Subject working title: ___
- Segment (silent 60–90 days): ___ / Exit link tested: ___
- Question asked: ___
- Success signal (stays + clean exits): ___

## Guardrails
- Max sends/week: ___ / owner: ___ / review date: ___

Worked mini-example — Research Desk monthly: educational ("the footnote check," whole willing list → checklist page), launch ("template pack v2, this week" → engaged segment → template page), update ("citation export changed — here is the new click path" → active users only → help page), re-engagement ("still researching weekly? stay or go" → silent → reply/exit). Four jobs, four measures, no mixed-purpose mush.

Finish line: an EMAIL-CALENDAR.md with four sends, each carrying job, segment, exact destination, and success signal, plus weekly cap and owner.

Verify quickly: cover every row except subject and destination. Can a teammate still tell which job it is and who should receive it? If launch and update are interchangeable, the jobs are blended — split them.

Common failure mode: the megaphone default — every send to the entire list "so nobody misses out." Everybody misses out: newcomers get migration notes, customers get beginner guides, the silent get louder pitches, and the engaged get diluted value. Segment or shrink.

Check your understanding

1. What is the job and success signal of each of the four email types? 2. What does message match require from subject through destination? 3. Why are two honest segments better than six imagined ones?

Next

The calendar is set. Lesson 78.4 closes the class with honest measurement and respectful retention — delivered, clicks, replies, conversion, unsubscribes, deliverability, and the monthly keep/change/stop review.

ARTICLE DISCUSSION

JOIN THE
CONVERSATION.

0 COMMENTS

BYEBUY ACCOUNT ACCESS

Sign in

Use your account to save routes and make the catalogue yours.

Enter your email and we’ll send a secure sign-in link and code.

NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY · NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY ·