The launch-pipeline operator for solo builders in rapid-build competitions
"I kept rebuilding the launch stack from scratch. Every single contest."
The time that should go into the tool goes into materials instead — and the deadline doesn't move.
"Can you draft me a landing page? Build's basically done — I'll add an example later."
GENERIC AI
"Absolutely — here's a landing page draft:
hero, feature grid, a call-to-action…
We'll swap in the example the moment it's ready."
SHIPPER
"Gate 1 blocks before Gate 2 is reached.
A landing page pointing at a build with nothing to show converts no one — and erodes trust.
BLOCK — Commit one real run first. The page is drafted the moment there's something to point at."
→ Readiness — blocks or passes
→ Leverage — routes by payoff, not by what you asked for
→ Hook — picks one, self-checks against five failure rules
→ Flags — catches what sinks launches
You come back to a plan and drafts.
Pitch blurb · Landing copy · 60-second script
Pitch deck · Judge guide · Duel storyboard
Tier-ordered for the runway you have. Not what you asked for — what earns the effort.
SONAR
Prospect-qualification operator. Scores studios against a 107-point fit framework and returns one verdict.
LIVE AT
[ sonar url ]
SHIPPER
Launch-pipeline operator. Reads a finished build, runs four gates, returns a plan with drafts — or a block.
LIVE AT
[ shipper url ]
A judge can open both before they read this slide.
"Built by a repeat contest entrant."
"Multiple submissions, one pattern: built the tool, scrambled the launch. Wanted to focus on making something good — so I built the thing that handles the rest."
— Roc Lee, ICM
Drop the folder into any Claude project.
Create project → Add slipway/ files → Set instructions → Paste your repo
github.com/[repo]