Gavel Gavel
Experts Guides Skills
Guides
Launch

Product launch strategy: the bets you make before the checklist

A product launch strategy is the set of bets you place before you touch a checklist. The big ones: audience-first or product-first, whether your moat is distribution or the product itself (Evan Spiegel argues software is not a moat), whether to concentrate the launch on one channel, and treating launch as a process you repeat rather than a single event. Below are the strategic bets, cited to operators who made them, and where they disagree on whether to build distribution or the product first.

Why this matters. "Product launch strategy" is searched by founders who sense that a checklist alone will not save a launch, and who need to choose the underlying bet, audience-first versus product-first, before spending a scarce hour.

Ask Gavel, free

Ask Gavel which launch strategy fits your product, audience, and runway.

2 of 3

inflection points, a technological shift, a consumer-behavior shift, or a business-model shift, that must be present for a new product to succeed, per Aparna Chennapragada. Launching on only one is being early, which is the same as being wrong.

Aparna Chennapragada Three Inflection Points

The short answer

The strategic bets a launch rests on

Strategy is choosing these bets before the checklist. Get the bet wrong and no amount of launch-day execution saves it.

  1. 1

    Audience-first or product-first

    Greg Isenberg's ACP sequence bets on building an audience, then a community, then the product, so demand exists before code does. The opposite bet ships first and recruits users by hand after.

  2. 2

    Where the moat lives

    Evan Spiegel's thesis is that software is not a moat, because features get cloned, faster than ever with AI. The durable advantage is distribution and the ecosystem of creators, habits, and hardware.

  3. 3

    Launch as a process, not an event

    Garry Tan treats the first launch as a probe: launch early and often, diagnose, and launch again roughly every three months. Traction compounds on the third launch, not the first.

  4. 4

    Whether the timing is real

    Aparna Chennapragada requires at least two of three inflection points, technological, consumer-behavior, or business-model shift. One tailwind usually means you are early, which is the same as wrong.

  5. 5

    Which hive you launch into

    Seth Godin's bet is to choose the hive first: a tight community of sneezers with an unmet need, selected before you decide what to build, so the product spreads through people who talk to each other.

Strategy is upstream of the plan and the checklist. Decide the bet, then sequence the launch around it.

The cited playbook

  1. 1

    Decide the audience-first bet before you build

    Greg Isenberg's ACP sequence is a strategic ordering rule: build an Audience, convert it into a Community, then launch a Product to it. The bet is that when AI makes building nearly free, demand should exist before the code does, so you grow reach first and ask the audience what to build.

    Greg Isenberg · ACP Funnel
  2. 2

    Treat distribution, not the product, as the moat

    Evan Spiegel's lesson from fifteen years at Snap is that software is not a moat: any feature you ship can be cloned, faster now that AI writes the boilerplate. So a great product is table stakes, and the strategic work is distribution, plus the ecosystem of creators, habits, and hardware a rival cannot copy overnight.

    Evan Spiegel · Distribution is the moat
  3. 3

    Treat launch as a process, not an event

    The strategic reframe is that launch is a verb you repeat, not a day you survive. Garry Tan's cadence is launch early, launch often: the first launch is a probe to diagnose problems and find early adopters, the second is iteration, and the third is when traction starts to compound.

    Garry Tan · Launch early, launch often
  4. 4

    Require two tailwinds before you bet on the launch

    Aparna Chennapragada's gate is that at least two of three inflection points must be present for a new product to succeed: a technological shift, a consumer-behavior shift, or a business-model shift. Launching on only one is being early, which she equates with being wrong.

    Aparna Chennapragada · Three Inflection Points
  5. 5

    Choose the hive before you choose the product

    Seth Godin's strategic move is to select the market before the product: find a tightly knit community with concentrated sneezers, high-velocity communication, and an unmet need, then decide what to offer them. Launching into a chosen hive of connected enthusiasts beats shouting at the masses.

    Seth Godin · Choose the hive

Where experts disagree

Where operators disagree: build distribution first, or the product first

Greg Isenberg

says distribution is the new moat: grow an audience of about a thousand people first, ask them what to build, and launch to a warm market. When AI makes building nearly free, reach is the only scarce, defensible asset.

Paul Graham

says do things that do not scale: get a product worth using into a few hands, then recruit the next users one by one. The unscalable, by-hand work is the distribution, and it teaches you what an audience poll never could.

ChatGPT will pick the fashionable answer. Gavel shows you Isenberg's audience-first bet and Graham's product-first bet, so you spend your scarce hours on the one your launch actually needs.

FAQ

Common questions

What is a product launch strategy?

It is the set of bets you make before the checklist: audience-first or product-first, whether your moat is distribution or the product, whether to concentrate on one channel, and whether to treat launch as a repeatable process. The checklist executes the strategy; it cannot replace it.

Should I build an audience before I launch?

It is one of the two main strategic bets. Greg Isenberg's ACP sequence builds an audience and community before the product, so demand is validated first, which is lower risk when the product is easy to clone. The opposite bet, favored by YC operators, is to ship first and recruit users by hand.

Why do people say launch is a process, not an event?

Because the first launch rarely produces traction; it produces information. Garry Tan's cadence is to launch early and often, diagnose week by week, and launch again roughly every three months. Treating launch as one high-stakes day is the pressure that delays founders and teaches them nothing.

How do I know the timing is right for my launch?

Aparna Chennapragada's test is to require at least two of three inflection points: a technological shift, a consumer-behavior shift, or a business-model shift. If only one is present, you are probably early, and being early is the same as being wrong.

Is distribution really more important than the product?

Operators disagree, which is the point. Evan Spiegel and Greg Isenberg argue software is not a moat and distribution is the durable advantage. Paul Graham and YC counter that a product people want, plus by-hand user recruitment, comes first. Gavel shows both so you can bet the one that fits your market.

Bring your actual numbers. Get a cited answer you can defend.

Try Gavel free

Related guides

Launch

Product launch checklist

The product launch checklist that moves the needle: build the list before launch day, recruit...

Launch

Product launch plan

A product launch plan as a timeline: pre-launch weeks (waitlist, pre-sell), the launch window...

Distribution

Customer acquisition framework

There are only four ways to get customers: warm outreach, cold outreach, content, and paid ad...

Keep exploring

Experts & frameworks

Every operator Gavel cites, with timestamped sources.

Is ChatGPT good for…

The decision-by-decision take on where generic AI falls short.

Playbooks

Multi-expert guides for pricing, PMF, first customers.