Your course can't teach someone who isn't there

The welcome that sets expectations, the rescue that catches someone going quiet, and the completion that lands while they still feel it. Built on real triggers and real actions, on your own course, in about an evening.

See what's inside

3
Modules: 8
Practical lessons: Free
No card required: 1-to-1
A coach reviews your work

Nobody stops because the teaching was bad

Think about the last online course you paid for and didn't finish. You probably weren't disappointed by it. You watched a couple of trainings, thought it was good, meant to come back on the Tuesday, and then a week passed and the tab was closed and that was that.

That is what is happening to your students right now, and it is almost never a content problem. Someone joins on a Thursday with real intent, and intent has a half-life of about two days. Someone finishes their first training feeling good and has no specific reason to open it again tonight rather than next week. Someone hits the training that requires actual work and postpones it once, which is usually forever.

None of those three moments can be fixed by recording a better video. They're fixed by something noticing — and by a message that names the exact next step rather than asking how you're getting on.

By the end you can

Name the exact moment your own students go quiet, from your course's activity rather than from a guess
Read any automation as one sentence: when this happens, if this is true, then do these things
Write a welcome that sets expectations and gives one specific next step, with a second email two days later for the people who haven't started
Write a rescue that reads as a next step rather than as encouragement, and know the inactivity window that's a nudge instead of nagging
Close a course by naming what the student built and the question it leaves them with, without turning the finish into a pitch

What you'll cover

1
Module 1 — When, if, then
Where students actually stop, the three parts every automation is made of, and how to write one that doesn't sound like software.
2
Module 2 — The three sequences every course needs
Welcome, rescue, completion. Build all three on a real course. Everything else in the automation catalog is optional; these are not.
3
Module 3 — Capstone: ship one and watch it fire
The timing idea that makes the difference between an email that reads as personal and one that reads as software, and then proof that yours ran without you.

This is for you if

You have a course live and no idea who stopped, when, or why
You know you should have a welcome sequence and have been meaning to write one since roughly last spring
You've watched students join enthusiastically and then never hear from them again
You've written automated emails before and they came out sounding like a receipt
You want the follow-up to still happen in a month where you're too busy to do it yourself

Why this one is different

You build it on your own course

Not a worksheet and not a sandbox. Every training ends on the Automation tab of a course you actually own, and the capstone is a real run with a real log row behind it.

The emails you receive are the lesson

This course's own welcome and rescue emails tell you which trigger sent them and why they're written the way they are. You're on the receiving end of the thing you're building, which is the fastest way to learn what it feels like.

Three sequences, not thirty

The catalog has fifteen actions and two dozen triggers, and you need almost none of them. Welcome, rescue, completion — the course is deliberate about which three are not optional and which everything else is.

Questions

Do I need students before this is worth doing?

No, and building it first is the better order. Sequences written before anyone arrives are ready when the first person does — and the first person is exactly who you can't afford to lose to silence. If you have no course at all yet, start with Your First Course in 5 Days.

How much writing is this?

Three emails, and you don't start from blank. There's a library of full sequences with the copy already written, so most of the work is editing something into your own voice rather than composing from nothing.

Will this make my academy feel automated?

That depends almost entirely on timing and specificity, which is why a whole training is about the delay field. An email that arrives four seconds after a click reads as a system message; the same email two hours later reads as a message. And one that names the exact training someone is on reads as attention, because it is.

How long does it take?

Eight short trainings and about an evening of building, or a week if you'd rather do one at a time. Nothing is locked — everything is open from the moment you join.

What if I set something up wrong and email people too much?

The editor warns you about the one setting that causes it, and every run your academy has ever made is listed with its status, so you can check rather than hope. The course spends a training on exactly this, including the failure nobody notices: an automation that has been quietly skipping every student for a month.

The part that runs while you're doing something else

Eight short trainings, three sequences, and one automation live on your own course by the end of it. Free, and everything is open the moment you join.