How to Launch a Product as a Team of One

Read any launch playbook and count the implied headcount: someone on ads, someone on email, someone in the community, someone making assets. The classic launch is a team format. Run it solo and you get the launch-week horror story — 4 a.m. asset production between customer questions.

A solo launch needs a different shape, not a smaller version of the team one. Here's the two-week format that works when everyone involved is you.

The premise: assets before calendar

The solo launch rule: nothing is created during launch week. Everything — emails, posts, clips, the walkthrough — exists before day one, most of it derived from a single recording session about the product: why it exists, what it does, who it's for. Launch week is for sending and responding, the two things that can't be pre-made.

Week one: warming (three emails, quiet channels)

Your list is the launch — everything public is amplification. Three emails across the week before:

1. The story — why this product exists, told as the problem that wouldn't leave you alone. No selling; open the loop.
2. The problem, deepened — teach something genuinely useful about the problem the product solves. The belief-shift email, aimed at the launch.
3. The honest preview — what it is, who it's for and not for, what it costs, when it opens. Anti-hype is positioning: exclusions build more trust than promises.

Channels get one story-post and one preview-clip this week. That's enough; warming happens in the inbox.

Launch day: open, then respond

Morning: your best email — short, direct, one link. The thank-you-page and sales-page machinery does the converting; the email's only job is the click. Channels get their pre-made piece: the walkthrough video (recorded — a live webinar is a single point of failure you don't need), the launch post, the best clip.

Then the actual work: answer everything, fast. Launch-day questions are objections in costume, and answering one publicly converts everyone else quietly holding it. Every question also gets logged — that's your objection mine and next quarter's FAQ.

Week two: the middle matters

Solo launches die in the middle — the post-launch-day sag where you're tired and the list is "probably sick of hearing about it." (They're not; open rates say they barely noticed.) Three more emails carry it:

• The objection email (day 3): the two most-asked questions, answered plainly.
• The proof email (day 5): first buyer feedback, or what buyers are doing with it.
• The honest close (final day): launch price ends when you said it would. Real deadline, honored — fake scarcity is trust sold at launch prices.

What a team of one deliberately skips

No affiliates on launch one (recruiting and managing them is a launch of its own — that's what built-in affiliate tooling is for, later). No paid ads to cold traffic (cold conversion needs proof you don't have yet). No live events. No launch-week feature changes, ever.

Afterward, the launch leaves permanent value regardless of revenue: buyers (a different relationship than subscribers), a logged objection list, and a set of assets that become the evergreen funnel. Launch one is the expensive prototype for launch two — price the effort accordingly, and keep the machine you built.