launch operator for course creators.
course creators have a trap nobody warns them about: the course is the fun part. module five gets a fourth polish while the launch email sits unwritten, because building feels like progress and launching feels like exposure.
the launch operator is the skill file that makes the launch a production line instead of a mood: curriculum frozen at good-enough, launch assets sequenced, and a cart date the modules have to meet, not the other way around. paste it once, run it when the launch is the blocker. that is the difference between an operator and another chat thread you cannot reuse.
the course creator's launch trap
the stall pattern is always the same: "i'll launch when the course is done." but a course is never done, there is always one more lesson, and every week of polishing costs a week of enrollment revenue while teaching nobody. the operator inverts the dependency: the cart date is fixed first, and the curriculum ships at whatever good-enough it reaches by then. students buy outcomes and momentum, not module counts, and version two gets funded by version one's cohort.
the second trap is launching to silence. a list that heard nothing for three months gets an "enrollment open!" email and ignores it, not because the course is bad, but because announcing is not the same as warming. the sequence puts the warming before the cart, on dates.
a worked example: the $497 cohort course
before: a notion database of 40 lessons at 80% done, no launch date, a list of 900 that last heard from her in april. after running the launch operator: curriculum frozen at 32 lessons ("the other 8 are the version-two upsell"), a two-week warm sequence (the origin story, one full free lesson, a student result), cart open for five days with a real close, and daily open-cart emails drafted in advance so week-of panic writes nothing. the launch shipped on the date because the date existed before the polish did.
the course launch sequence, in order
| step | asset | the mistake it prevents |
|---|---|---|
| 1 | cart date, fixed first | "when it's done," which is never |
| 2 | curriculum freeze at good-enough | module five's fourth polish eating launch week |
| 3 | warm sequence (story, free lesson, result) | announcing to a cold list and blaming the course |
| 4 | open-cart dailies, pre-drafted | week-of panic writing nothing |
| 5 | real close + version-two note | the cart that stays open until the offer means nothing |
pair it with CLAUDE.md so voice and student language stay loaded, and read the cornerstone guide for why the sequence beats prompt-by-prompt launching.
when to install this one first
launch goes first for course creators when the material exists (even at 80%) and the list exists but no cohort has a date. if the list is the missing piece, install distribution first and come back with an audience to launch to. the free map at /operators/ sorts it in two minutes.
how this differs from channel agent bundles
most agent bundles optimize media buying, email, and creative inside claude code, useful once a course already converts, useless for getting cohort one out the door. gtm operators cover the shipping spine: date, freeze, warm, cart, close. the comparison table has the split.
want the operator map?
five installable job titles for launch, distribution, nurture, offers, and brain architecture. free map by email at /operators/. full pack has all five skill files in one zip.
get the free operator map