All insights
MarketingProduct · 4 min read

Launching twice (and why it helps)

Most companies launch once and move on. The teams that get the most attention from a launch launch it twice, and the second one usually outperforms the first.

A launch is treated as a single moment. The team announces, the announcement gets coverage or doesn’t, then everyone moves on. The savvier teams launch the same feature twice, three months apart, and the second launch usually performs better than the first.

Why the second launch works

  • You have real customer stories now, not just "available today."
  • Bugs from the initial release are fixed; demos are smoother.
  • Reviewers have something to actually evaluate, not just a claim.
  • The category has had time to notice the existence of the feature.

What to call it

Not "relaunching" that signals the first one failed. Call it a milestone ("now generally available," "now supports X scenarios," "now used by Y customers"). Each milestone is a legitimate launch in itself.

Most launches under-perform because they’re one-shot. Plan the second one before the first one ships.

Have something that should run itself?

Tell us what runs by hand today. We reply within one business day with a first idea.