A launch is a hundred small correctness checks wearing a single deadline. Miss the pricing page's currency and you refund a morning's orders; forget the welcome email and day-one retention sags; skip content protection and your launch week is a piracy distribution event. This checklist compresses the sequence — use it literally, in order, and launch with the calm of someone who has nothing left to forget.
Pre-launch: content and platform (2 weeks out) #
- Course complete: every lesson recorded, uploaded and watched end-to-end by you, at student speed
- Interactivity installed: in-video questions on key lessons, module quizzes generated and reviewed
- Materials attached: PDFs, templates and checklists with annotation enabled
- Security on: secure offline mode, device limits, watermarking — before the first enrollment
- Purchase flow tested: buy with a real card, receive access, enroll, watch on phone and laptop
- Sales page live: outcome-first hero, curriculum as benefits, testimonials, FAQ, price with tiers
Pre-launch: audience (1 week out) #
- Waiting list warmed: three value emails sent, launch date announced, founding pricing stated
- Free session delivered: the live proof-of-teaching that converts the hesitant
- Social proof reserved: three early reviewers with access, testimonial collection ready
- Announcement assets ready: posts, emails and short videos drafted, scheduled, and edited on mobile preview
Launch week and the week after #
Launch day: emails out at your audience's best hour, personal replies to every purchase message, live presence in the community thread, and a bugfix window — you will find three small things, fix them fast and tell students you did. All week: daily engagement (one post, one answered question thread), daily analytics review (where enrollments drop in the funnel), and honest scarcity if you set deadlines. The week after: welcome-sequence emails driving first-lesson completion, testimonial requests to your first finishers, refund-policy honored without friction, and the retrospective — what sold, what stalled, what version two fixes. Launches aren't events; they're the first iteration of a product you're about to improve with real data.