M7 — 3 Launch Case Snapshots

Three real launch moves. Two from my own brands — one a physical product whose launch was decided six weeks before the announcement, one a digital product that deliberately has no launch day at all. One placeholder for the first founder out of Accelerator cohort 1.

Case A — Bausele Elemental, April 2026: the launch happened before the announcement

A six-week waitlist build that did all the work the launch day got credit for.

The setup. The Elemental drop was scheduled for 15 April 2026. The public version of the story is the drop day: a new colourway revealed, an evergreen URL flipped live, an email to the database, sales. The operational version is different. The launch wasn’t the drop day. The launch was the funnel that had been running for six weeks before the drop day, which is the reason the drop day had anyone to sell to.

The funnel in operational detail. Top of funnel: Meta ads (a CBO Prospecting campaign at $100-157/day across the build, plus a small TOF Traffic line at $10/day) pointing at a waitlist landing page with one job — collect emails. Middle of funnel: a Klaviyo waitlist flow (ID Ub3upj, live since 9 March) that warmed new subs across 5-7 touches before drop day. A warm-up email to the entire database on 11 April revealing the second colourway. By 14 April the waitlist was at 3,168 subs — past the 3,000 target. Bottom of funnel on drop day: an existing-buyers-first early-access window → waitlist window → public open. The funnel was a sequence of windows, not a single button.

What the numbers said. 150 buyers, AUD $1,200 average order value with no discount, $180K revenue, 16.9x ROAS on $10,618 of Meta spend, 4.67% conversion from the waitlist. The drop day produced the revenue. The six weeks before the drop day produced the conditions under which a drop day could produce revenue. The single most common misreading of this launch — by people who only see the announcement — is to credit the email of 15 April. The email of 15 April converted what the funnel had already pre-qualified. Without the funnel, the same email would have produced a tenth of the result.

The discipline behind the soft-launch-inside-a-hard-launch. The existing-buyers-first window was a soft launch dressed inside a drop event. It let the team see the buy-flow under live load with the most forgiving audience before the public link went out. Any friction surfaced in the first window got fixed before the wider waitlist saw the page. By the time the public window opened, the funnel had been tested twice against real buyers. Most launches that fail in public do so because the founder tested the funnel with friends and family — who forgive everything — and then exposed it to strangers who don’t.

The lesson: A launch event is a moment. A launch funnel is a six-week operation that produces the moment. Confuse the two and the moment produces silence. Build the funnel first, build the warm-up sequence second, treat the drop day as the audit point — not the launch.

Case B — EXITR Toolkit, May 2026: the product with no launch day

The live-URL approach to launching a digital product, in progress right now.

The hypothesis. A digital product priced at $497 with rolling enrolment doesn’t need a “launch day” — and a launch-day model for it actively works against the product. A launch day implies scarcity (only available now), a hero moment (the big reveal), and a campaign sprint (the team pushes for two weeks then collapses). None of those map to a self-paced toolkit that benefits from a quiet, expanding library and a slowly-built reputation. The Toolkit doesn’t have a launch day. It has live URLs.

What that looks like operationally. As I’m writing this, the Toolkit is mid-launch in the live-URL sense. The site is on Shopify. Module 1 is fully fleshed with worksheet, cases and 10 prompts inline. Modules 2-12 are being built and pushed module-by-module — M2 through M6 already pushed, M7 the one you’re reading. There’s no countdown timer. There’s no email blast announcing “Toolkit launches Tuesday”. There’s a URL anyone in the world can reach and a payment flow that works. When a stranger arrives via the Assessment, they enter a funnel: assessment form → reply within 48h with a tier recommendation → if Toolkit is the fit, a private buy link. The funnel runs whether or not anyone is announcing anything.

Why the launch-day model would have been worse. A launch-day model would have forced the build into a single sprint window — pretend everything is ready, push hard for 7 days, deal with the inevitable bugs in public, burn the warm circle on a date that doesn’t matter. The live-URL model lets the product compound. Each module pushed makes the Toolkit more complete; each Assessment reply tightens the funnel; each first buyer surfaces a friction point that gets fixed before the second buyer ever arrives. The launch is the URL going live. The growth is everything that happens after.

The trade-off being made deliberately. The live-URL approach trades visibility for durability. There is no PR moment, no peak in the analytics, no day where everyone in the segment hears about the product at once. In return, there’s no peak-and-trough cycle, no hard cohort window to defend, no team burned out on day 14. For a Toolkit priced at $497 with the strategy of compounding from satisfied first-buyers into word-of-mouth, that’s the right trade. For a $5,997 1-on-1 Founder Lab capped at 8 per quarter, a cohort window is the right model. The product shape decides the launch shape — not the other way around.

The lesson: Before you build a launch, ask whether your product is a launch-day shape or a live-URL shape. Cohort-based, capacity-constrained, scarcity-driven offers want a launch day. Self-paced, library-shaped, compounding offers want a live URL. Choosing the wrong launch model is the most common pre-launch mistake — and the most expensive one, because you only find out after the launch has failed.

Case C — [Founder name], Accelerator cohort 1 (placeholder)

The services / SaaS / personal-brand dimension.

This slot fills the day Accelerator cohort 1 finishes M7. Same convention as M2-M6 — rewritten with a real founder’s funnel diagram, their soft / hard decision and why, their first 10 paying customers and the channel each came from, and the friction point that almost killed the launch but didn’t.

Until then, a working principle from twenty-five years of watching launches succeed and fail:

The founder who fails at M7 isn’t the one who can’t build a website. AI built the website in a weekend. The founder who fails at M7 is the one who built the website and then waited for strangers to arrive. They confused launching the page with launching the funnel. They posted a “we’re live!” message to LinkedIn, watched the like count climb, watched the sales counter stay at zero, and concluded that the offer was wrong. The offer wasn’t wrong. The funnel didn’t exist. The strangers were never going to arrive in the first place, because no path had been built that would carry them from where they were to where the page was.

A founder I worked with in a previous cycle launched a $1,500 productised service with a beautiful landing page. The page converted at 6% — well above benchmark. The launch produced two customers. The reason was visible the moment we drew the funnel on a single page: there were 47 visitors in the entire launch week. The page wasn’t the problem. The 47 was the problem. She had spent six weeks on the page and zero weeks on the path that brought people to the page. The fix wasn’t a redesign. The fix was a one-page funnel diagram with a top-of-funnel number on it — and the honest realisation that her channel mix at the time produced about 50 visitors a week. To hit her launch-week target she needed either a bigger top of funnel, a longer launch window, or a smaller target. She picked the longer window. The launch became a quiet 90-day soft-launch that ended in 11 customers, no discount, and a funnel she could repeat.

The launch a buyer remembers is the one where the funnel was built before the page. The launch they never see is the one where the page was built and the funnel was assumed. The page is the easy part. The path is the work.