launch-playbooks
Skill0 starsChanged 2 months agoMITView on GitHub
The 5 launch models (seed, classic, low-ticket paid event, 2-day intensive, hybrid) with a selection tree, phase structure, and KPI gates per phase. Use when mkt-strategist is planning, structuring, or auditing a launch of any kind.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- global/CLAUDE.mdCLAUDE.md
- copywriting-frameworksSkill
- design-mdSkill
- format-carouselSkill
- format-hooksSkill
- format-linkedinSkill
- format-reelsSkill
- funnel-designSkill
- humanizationSkill
- offer-designSkill
- pipeline-brandSkill
- pipeline-campaignSkill
- pipeline-contentSkill
- pipeline-copySkill
- pipeline-landing-pageSkill
- pipeline-luxoSkill
- pipeline-refino-uiSkill
- pipeline-sistemaSkill
- scroll-worldSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Every launch uses one of these five models — avoid improvised hybrids without an explicit, stated reason.
- Distinctive: line 27
No existing audience AND no budget for paid traffic?
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch Playbooks
The 5 Launch Models
Every launch uses one of these five models — avoid improvised hybrids without an explicit, stated reason.
| Model | Best for | Shape |
| Seed launch | First launch for an offer, validating product-market fit | Small audience → free content arc → live/webinar event → cart window |
| Classic launch | Scaling after a seed launch succeeded, existing audience to reactivate | Extended pre-launch content arc → live launch event → cart window |
| Low-ticket paid event | Repeatable weekly/monthly acquisition, largely cold traffic, no existing list required | Paid ticket funds traffic → multi-day event delivers real value → core offer pitched at event close |
| 2-day intensive | High-energy live cohort event, strong live facilitation available | Ticketed 2-day live experience → immersive proof + community → pitch at close |
| Hybrid | Paid-ticket acquisition combined with a longer content arc | Paid ticket funds traffic → classic-style content arc during the event window → cart at close |
Selection Tree
- First time launching this offer? → Seed launch.
- Already validated, with a warm list to reactivate? → Classic launch.
- Need a repeatable, scalable, mostly-cold-traffic model? → Low-ticket paid event.
- Strong live facilitation available and want a high-energy community event? → 2-day intensive.
- Want paid-ticket economics but a longer content arc than a 2-day event allows? → Hybrid.
- No existing audience AND no budget for paid traffic? → Seed launch is the only viable starting point.
Phase Structure (generic across all 5 models)
- Pre-launch — audience building, authority content, no pitch.
- Warm-up / anticipation — proof and story content; objections start getting pre-handled.
- Core content event — the live or scheduled sessions delivering a real slice of the promised transformation; this is where trust converts into buying intent.
- Cart / offer window — the pitch and the buying window, always time-boxed, never indefinite.
- Post-launch debrief — mandatory. Document what worked, what didn't, and update the next cycle's plan before starting it.
Low-Ticket Paid Event — Core Economics
The mechanism: ticket price funds ad spend. Ticket revenue divided by ad spend should reach or exceed 1.0 before traffic is scaled further. The core offer sold at event close is the actual profit center — traffic is already paid for by ticket sales, which is what makes the model repeatable without new capital. Never scale spend beyond what ticket revenue is currently funding. Exact ticket price bands, order-bump structure, and profit targets are set per project pack — this playbook defines the mechanism, not the numbers.
Content-Arc Structure (Classic / Hybrid)
A multi-part content arc building toward the event, each piece building on the last:
- Piece 1 — Opportunity: reframe what's possible, plant the mechanism.
- Piece 2 — Transformation: show the path, address the single biggest objection.
- Piece 3 — Experience/proof: case studies, live demonstration, direct social proof.
Objection-handling belongs inside this arc, progressively, before the pitch — not bolted onto the pitch itself as an afterthought.
Event Format Selection
- Single-session workshop (hours, not days) — use when the transformation can genuinely be perceived in one sitting and the core offer is a natural next step.
- Multi-day event (roughly 5-7 days) — use when the transformation requires progressive implementation, small proof points need to compound day over day, and trust needs to build gradually before the pitch lands.
State explicitly why the chosen format fits the offer — format is a strategic choice, not a default.
KPI Gates Per Phase
| Phase | Gate | Generic sanity-check range |
| Pre-launch | Audience/list growth on pace | Track against the plan's own stated target |
| Core content event | Show-up / attendance rate | Roughly 50-75% of registered is typical; below ~40% signals a warm-up problem, not an event problem |
| Core content event (multi-day) | Retention across sessions | Expect gradual drop-off (e.g., ~30% day one down to ~15% by the final day); a cliff drop signals a content or timing failure, not normal attrition |
| Cart window | Conversion to core offer | Roughly 2-8% of engaged audience is a typical healthy range depending on price tier; below range, diagnose the offer or objection-handling before blaming traffic quality |
| Post-launch | Debrief completed | Binary gate — no next cycle plan without it |
Exact target numbers per phase belong in the project pack; the ranges above are for sanity-checking a plan, not contractual targets.
Mandatory Elements (all 5 models)
- Positioning and target segment documented before any creative work begins
- Offer with a full value stack and guarantee (see
offer-design) - Objection map — universal objections (time, money, trust, fear) plus segment-specific ones, each with a content or copy answer
- Content plan supporting the launch thesis, sequenced across the arc
- Metrics tracked at every phase (see KPI gates above)
- Post-launch debrief document — mandatory, not optional
Quality Gate Before Going Live
- Target segment and offer reviewed and signed off by
mkt-strategist - Funnel mapped (see
funnel-design) - All copy has cleared the
mkt-editorgate - Any paid campaigns created PAUSED per
.claude/rules/ads-safety.md - Explicit human approval obtained before any spend activates or the cart opens
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

