One primary text and a hope is not a launch. It is a draft that escaped.
What belongs in a package
- Offer and margin notes
- Who it is for (even roughly)
- Creative angles, not a single hero image forever
- Landing experience that matches
- Email or SMS support if you have them
- Stock reality for the SKUs you will push
- Success criteria and a kill rule
Yes, that is more work up front. It is less work than untangling five unrelated tests that all “kind of” ran.
Soft launch
Start with limited spend or a narrower audience. Confirm tracking and fulfilment nerves. Then open the aperture. Ego launches go wide on day one. Operators earn width.
If your team still drops assets into a void, introduce a single review step. The review checklist is deliberately short. Use it.
What soft launch is not
It is not “launch broken and hope”. It is limited blast radius while you confirm tracking and fulfilment nerves. Then open the aperture.
Questions people actually ask
How soft?
Enough to learn, not enough to hurt if something is wrong. Depends on AOV and risk.
Package template (copy into your doc)
- Offer + margin note
- Primary SKUs + cover snapshot
- Audience sketch
- Creative angles (3+)
- Landing URL + proof it matches
- Email/SMS support yes/no
- Success metric + kill rule + owner
When to skip soft launch
Tiny tests with trivial spend and zero inventory risk can go faster. Everything that touches a major hero SKU, a sitewide code, or a new tracking setup deserves the gate. Be honest about which launches are actually big.
If you want stock, ads and the morning list in one place: that is what we built Ralph for — a growth operator for Shopify, with review before anything ships. Not magic. Fewer tabs. See Ralph · Docs