Blog
5 min read
Turning Homeschool Coaching Into a Bookable Product: International School of America
Jun 12, 2026
They all send email, which is exactly why everyone confuses them. The owner who blasts the monthly update as a one-off, hand-sends the same welcome email every time a lead arrives, and saves the big announcement for a newsletter nobody reads until Thursday — they're not bad at email. They're using the right words in the wrong tenses. Broadcasts, newsletters, and journeys differ in one thing only: their relationship to time.
Quick answer: A broadcast is one message at one moment — something happened, tell everyone relevant now. A newsletter is a rhythm — same audience, recurring cadence, relationship by repetition. A journey runs on each person's clock — triggered by what they did, automated from then on. If it's news, broadcast it. If it's a habit, newsletter it. If it should happen every time someone does X, build it once as a journey.
The one-line test
| Type | Clock it runs on | Send it when… | Classic examples |
|---|---|---|---|
| Broadcast | Yours, once | Something happened and the list should know now | Price change notice, new service, holiday closure, event seats open |
| Newsletter | The calendar's, repeating | You want to stay in people's lives between purchases | Monthly tips, seasonal update, behind-the-scenes |
| Journey | Each recipient's, triggered | The same situation recurs and deserves the same response | Welcome series after a form fill, post-booking sequence, win-back |
Misuse is always a tense error: a broadcast doing a journey's job means a human re-sending the same "welcome!" forever; a newsletter doing a broadcast's job means urgent news waiting for the second Tuesday; a journey doing a newsletter's job means automation pretending to be a relationship. Match the clock and each tool gets easy.
Broadcasts: one moment, told well
The broadcast is the simplest and the most abused. Its discipline is the question "did something actually happen?" A new offering, a price change with notice, a closure, a reopening — real events earn a one-time send. "We haven't emailed in a while" is not an event, and lists trained on eventless blasts learn to skim past the eventful ones.
Mechanics that keep broadcasts sharp: send to the people the news is for, not the entire database — an audience built from the relevant segment, or a list for genuinely one-time outreach — and preview the count before sending, because "how many people am I about to interrupt?" is the question that improves drafts. Afterward, review deliveries — a broadcast you can't confirm arrived is a rumor, not an announcement. When you're ready, creating one takes minutes; the craft is all in deciding it deserves to exist.
Newsletters: the rhythm is the product
A newsletter's job is different in kind: nothing needs to have happened. It exists so that when a reader finally needs what you do, you're the name already in their kitchen. That means consistency beats cleverness — a modest monthly note that arrives every month builds more trust than a brilliant quarterly one that arrives when you remember. The cadence is a promise; keeping it is the content.
Make the promise cheap to keep: a reusable template so each issue is filling sections rather than designing from zero, a standing structure (one useful thing, one update, one nudge), and a fixed writing slot the week it ships. Then read the performance the boring way — opens trending, links clicked — to learn what your readers actually want more of. The deeper strategy (list building, content sourcing, the whole engine) is our email marketing guide; the point here is just which jobs belong to the newsletter: relationship maintenance, yes; urgent news, never; per-person responses, never.
Journeys: build the response once
The journey is the only one of the three that runs on the recipient's clock. Someone fills your inquiry form at 11pm Saturday — the welcome arrives at 11:01, the follow-up lands Tuesday, the check-in a week later, each timed from their moment, not your office hours. That's the test for journey-shaped work: if you'd send the same emails every time a situation recurs, you're the automation — build it once instead.
Start with the welcome journey — highest leverage, simplest shape: every new contact gets greeted, oriented, and given a next step while their interest is at its peak (the same dead-zone logic as intake, applied to leads). From there, journeys earn their keep wherever behavior should change what happens next: post-booking preparation, post-purchase onboarding, quiet-customer win-back. Two disciplines keep them honest: read the reports quarterly (an automation nobody audits drifts into irrelevance while still "working"), and reread each journey yearly as a new customer would — automated email ages, and nothing says neglect like a journey referencing last year's offer. For linear cases — a fixed series of emails with no branching — a simple sequence is the lighter tool; reach for full journeys when behavior should alter the path.
The three together: a small system
The types aren't competitors — a healthy small-business email program is usually exactly this stack:
- Journeys handle the predictable: welcome on form fill, preparation after booking, follow-up after delivery. Built once, working nights and weekends.
- The newsletter holds the relationship: one issue a month to the full opted-in audience, modest and reliable.
- Broadcasts cover the actual news: a few times a year, to the audience the news concerns, ideally targeted by your ideal-customer segments rather than the whole list.
One rule binds all three: unsubscribe and contact preferences are sacred across every send type. A reader who leaves the newsletter but stays a client is a fine outcome; a reader who unsubscribed and still gets your broadcast is a complaint — and deliverability damage — waiting to happen.
If you're starting from zero, the order is leverage order: welcome journey first (it compounds from day one), newsletter rhythm second, broadcasts as life supplies actual news. Build in a month what runs for years.
Key takeaways
- Pick by clock, not by content: broadcasts run on your clock once, newsletters on the calendar's repeating, journeys on each recipient's — every misuse is a tense error.
- Broadcasts need an event: "we haven't emailed in a while" isn't one — lists trained on eventless blasts skim past the eventful ones.
- The newsletter's cadence is a promise: modest-and-monthly beats brilliant-and-whenever; templates and a standing structure make the promise cheap to keep.
- If you'd send it every time, you're the automation: recurring situations — new lead, new booking, gone-quiet customer — deserve a journey built once.
- Stack them, don't choose between them: journeys for the predictable, newsletter for the relationship, broadcasts for actual news to the audience it concerns.
- Preferences are sacred across all three: unsubscribes honored everywhere, counts previewed before sending — trust is the channel you're really maintaining.
Frequently asked questions
Can the same message ever be both a broadcast and a newsletter item?
Often — and the order matters. Real news goes out as a broadcast when it happens, then earns a recap line in the next newsletter for the people who missed it. What doesn't work is the reverse: holding news for the newsletter so the issue "has content." The news arrives late and the newsletter trains readers to expect announcements instead of value — both tools get worse.
How many emails should a welcome journey send?
Three to five over two or three weeks covers most service businesses: an instant warm welcome with the promised next step, a how-we-work orientation a few days later, and a gentle check-in if they haven't taken the step. The shape matters more than the count — front-loaded while interest is hot, exits gracefully when the person converts, and never keeps selling to someone who already bought. Reread it quarterly; it's the first impression most of your leads will ever get.
Won't journeys make my business feel automated and impersonal?
Badly written ones, yes — but the impersonal part is the writing, not the automation. A journey email written like you talk, referencing what the person actually did ("you asked about kitchen rewiring"), feels more personal than the generic blast a human sent manually. The honest comparison isn't journey versus handwritten note; it's journey versus the nothing that leads currently get at 11pm on Saturday. Automate the timing, keep the voice yours.
What list size justifies all this machinery?
Smaller than you'd think, because two of the three aren't volume tools. A welcome journey pays for itself with the very first lead it catches after hours, and a newsletter to eighty real locals beats one to eight thousand strangers. The only type that scales with list size is the broadcast — and even there the discipline is the same at any size: send real news to the people it concerns. Start the machinery before the list is big; that's how the list gets big.
Ready to put each message on the right clock? Faster runs broadcasts, newsletters, and journeys from one place — audiences shared across all three, templates that keep the rhythm cheap, and reports that show what's working. Start free and build the welcome journey first.