The coach launch operations playbook: pre-launch, launch week, post-launch

Most $1M+ coaches lose 15-30% of revenue per launch to operational gaps. Not because the offer is wrong or the audience isn't there. Because the operational layer underneath the launch breaks at predictable points and nobody is owning the breakage.

The breakage is fixable. Most coaches just don't have the team shape or the SOP layer that prevents it. Here is the 3-phase launch operations playbook that holds, with the role allocation and what specifically needs to be running at each phase.

What "operational breakage" looks like during a coach launch

Five specific failure modes that destroy launch revenue.

Failure 1: cart-abandonment recovery doesn't trigger. Customer started checkout, didn't complete. The abandoned-cart sequence never fired (broken automation, missed trigger, opt-in tracking issue). Lost revenue per failure = the cart value, typically $1-5K per abandoned cart at coach price points.

Failure 2: launch-day support overflows. Launch day generates 5-10x normal support volume. The CX team isn't scaled for it. Customers don't get answers to pre-purchase questions in time. They don't buy. Lost revenue = whatever percentage of support-question askers don't convert without an answer.

Failure 3: payment-failure follow-up doesn't happen. Customer's card declined during launch. The dunning flow isn't configured properly or isn't being monitored. Customer never re-attempts. Lost revenue = the full purchase amount.

Failure 4: post-launch onboarding crashes. 500 new students enroll on launch day. The onboarding sequence wasn't built for that volume spike. New students get a generic welcome instead of the personalized first-week experience, churn within 30 days. Lost revenue = the refund rate (often 20-30% within first month if onboarding fails).

Failure 5: VIP/high-tier upsell timing misses. The launch offer has a VIP tier ($X premium price). The upsell sequence to push standard buyers up to VIP doesn't run in the right window (must hit within first 24 hours, often configured for day 3). Lost revenue = the VIP-tier premium across the upsell conversion rate.

Total impact: a $500K launch with operational discipline becomes $350-425K without it. The lost $75-150K is per-launch leakage that's hard to see in real-time and obvious in the post-mortem.

Phase 1: pre-launch (weeks -6 to -1)

The operational setup that prevents most of the failure modes.

Week -6: tech audit.

• Test every automation (welcome sequence, abandoned-cart, payment-failure, post-purchase)
• Verify all opt-in tracking is firing correctly (especially across funnel pages and checkout)
• Audit payment processor configuration (Stripe webhook reliability, retry logic)
• Confirm course platform can handle expected enrollment volume

Week -5: CX prep.

• Pre-write FAQ documents for the launch offer (every objection, every clarification, every edge case)
• Train support specialists on the offer details + the SOPs
• Set up dedicated launch-week support channels
• Define escalation paths (which questions go where, what response times)

Weeks -4 to -2: content + community warmup.

• Pre-stage launch content (emails, social posts, video assets) in the publishing tools
• Verify content ops timing (which emails send when, social cadence)
• Community manager runs warmup engagement in the existing audience

Week -1: rehearsal.

• Run a test purchase end-to-end (does the receipt fire? Does the welcome sequence start? Does the course access provision?)
• Verify all team members know their launch-day responsibilities
• Final tech audit (any changes since week -6 audit?)

Most coaches skip week -6 (assuming the automations “just work from last launch”) and week -1 (assuming testing isn't necessary). The two skipped weeks account for most of the recoverable failure modes.

Phase 2: launch week (the 7-day push)

The operational discipline during the active selling window.

Day 1 (launch day):

• Support specialists at maximum staffing (typically 3-4x normal)
• Real-time monitoring of payment processor, course platform, email deliverability
• Hourly check on conversion metrics + abandoned-cart sequence performance
• Founder available for 2 hours of direct customer engagement (DMs, live Q&A)

Days 2-3 (the second push):

• Mid-launch email sequence sends (typically the "social proof" + "story" emails)
• Cart-abandonment recovery sequence runs (this is where 20-30% of recovered revenue lives)
• Support volume still elevated, staffing remains high

Days 4-5 (the steady phase):

• VIP upsell sequence to standard-tier buyers
• Continued email cadence
• Support volume normalizing to ~2x normal

Days 6-7 (the close push):

• Final scarcity / urgency emails
• Cart-recovery for late-window abandoners
• All-hands monitoring of the cart-close moment (typically the highest-conversion 6-hour window of the entire launch)

The team shape needed for this week is bigger than the team shape needed the other 51 weeks of the year. Most coaches bring in temporary support, which usually means hiring untrained VAs in week -2 (predictably wrong). Better path: have a Pod that's already trained on the operation and can flex up for launch week.

Launch week is when 6 weeks of operational prep pays back. The teams that skip pre-launch tech audits and rehearsal lose 15-30% of revenue and don't know exactly why.

Phase 3: post-launch (weeks +1 to +4)

The operational discipline that holds the new students past the 30-day refund window.

Week +1: payment-failure recovery.

• Daily monitoring of failed payments
• Manual outreach to high-value customers whose cards declined
• Dunning sequence runs (most coaches lose 5-10% of revenue here just from poor dunning)

Week +1-2: onboarding execution.

• Every new student enters the personalized onboarding sequence (not the generic "welcome to the course" one)
• Community manager welcomes each new member individually
• First-week activity tracking begins (students who don't log in within 5 days get gentle re-engagement)

Week +2-3: refund-risk monitoring.

• Identify students who haven't engaged
• Reach out personally (the difference between a refund and a retained customer is often a single outreach)
• Track refund volume against historical baseline

Week +4: post-mortem.

• Document what worked, what broke, what to change for next launch
• Update SOPs based on what was learned
• The deliverable is a playbook for the next launch, not a memory in the founder's head

The post-launch phase typically determines 20-25% of final launch revenue (refund prevention + tier upgrades + saved at-risk customers). It's also the phase most coaches under-staff because they're exhausted from launch week and want to move on.

The team shape that runs this

For a $1M+ coach running 2-4 launches per year:

• 1 Pod Operations Lead owns the launch playbook, the pre-launch audit, the launch-week orchestration, the post-mortem
• 1-2 CX specialists scale up during launch week
• 1 community manager handling member engagement
• 1 content ops specialist running the publishing cadence
• 1 data/admin specialist monitoring metrics + handling payment-failure recovery
• 1 AI automation specialist maintaining all the launch automations + monitoring health

This is the shape of a Standard PodFleet Pod. Without the structure, the coach is the integration layer between every function, which is the failure mode the launch playbook exists to prevent.

What this is worth per launch

For a $500K launch:

• 15-30% recoverable from operational discipline = $75-150K
• Annualized across 2-4 launches per year = $150-600K of recoverable revenue
• Cost of the Pod that runs it: well below the recovered revenue

The math compounds because every well-run launch produces better SOPs for the next one. Year 2 launches typically outperform Year 1 by another 15-25% on the same revenue base, because the operational layer has learned.