Playbook · Relaunch
Plan to relaunch a product that failed the first time
A second launch fails the same way as the first unless the underlying problem actually changed.
- 8 ranked moves
- 4-week sequence
- For products with a documented first failure
Plan to relaunch a product that failed the first time: what should you actually do?
Relaunching a failed product only works if you've fixed the actual reason it failed, not just added new marketing. Start by interviewing 10 people who tried and left, name the real cause, and only relaunch publicly if that cause is genuinely fixed. Rebrand the release as a specific, narrower version rather than a generic relaunch of the same broad promise.
Last updated 3 August 2026
| Play | Effort | Cost |
|---|---|---|
| Interview 10 people who tried it and left | 1-2 weeks to complete 10 calls | $500 in incentives |
| Name the specific failure cause in one sentence | Half a day | $0 |
| Narrow the relaunch scope instead of repeating the broad promise | 1 week | $0 |
| Rebuild the product fix before any relaunch marketing | Varies — 2-8 weeks depending on the fix | Varies by engineering scope |
| Re-engage past users privately before a public relaunch | 2-3 days | $0 |
| Rename or re-position if the brand carries too much baggage | 1 week to decide, 2-4 weeks to execute if renaming | $0-$5,000 for a rename and new domain/branding |
| Launch to the narrow segment quietly before going wide | 2-3 weeks | $0 |
| Only announce publicly once the narrow segment shows real traction | Ongoing | $0 |
A product that already failed once carries baggage a brand-new launch doesn't have: past users who churned and told their network why, a market that's already formed an opinion, and a team that's understandably nervous about repeating the same mistake. Relaunching well means treating this as a fundamentally different situation from a first launch, not a bigger, louder version of it.
This plan is for a product or feature that shipped, got real usage or signups, and then clearly failed — stalled growth, churn spike, or a shutdown — where the team now believes they've found and fixed the actual cause. If you haven't identified the real cause yet, do that first; a relaunch without a diagnosis just repeats the failure with better marketing.
- — A product with a documented first launch and a clear failure signal (churn, stalled signups, negative feedback)
- — A specific, testable theory for what went wrong, not a vague sense of 'it didn't land'
- — Access to at least some of the original users or signups to re-engage
- — A team willing to narrow the scope of the relaunch rather than repeat the original broad promise
If nobody on the team can name the specific reason the first launch failed, don't relaunch yet — spend two weeks on user interviews first. A relaunch without a diagnosis is just a second failure with more marketing spend behind it.
The moves
Ranked, highest return first.
Work down the list. Each one names the first step so there's nothing to plan.
- 01
Interview 10 people who tried it and left
Internal theories about why a product failed are usually wrong or incomplete. The people who tried it and churned know exactly what didn't work, if you ask them directly.
First step: Pull a list of everyone who signed up and churned within 60 days, and email 30 of them offering a $50 gift card for a 20-minute call.
- Tools
- Your CRM, Calendly, a gift card platform like Tremendous
- Effort
- 1-2 weeks to complete 10 calls
- Cost
- $500 in incentives
- 02
Name the specific failure cause in one sentence
'It didn't resonate' isn't a diagnosis. 'The onboarding required a technical integration our buyer couldn't do without an engineer' is a diagnosis you can actually fix.
First step: After the interviews, write the failure cause as a single specific sentence and get the whole team to agree it's accurate before building anything.
- Tools
- A shared doc
- Effort
- Half a day
- Cost
- $0
- 03
Narrow the relaunch scope instead of repeating the broad promise
Failed launches are often too broad — trying to serve everyone meant serving nobody well. A relaunch that names one specific use case and buyer usually outperforms a second attempt at the same broad pitch.
First step: Pick the one segment from your interviews who came closest to success, and rebuild the pitch, onboarding and pricing around only that segment.
- Tools
- Positioning doc, Google Docs
- Effort
- 1 week
- Cost
- $0
- 04
Rebuild the product fix before any relaunch marketing
Marketing a relaunch before the actual product fix ships repeats the same failure with worse credibility the second time around, especially with past users who'll notice nothing changed.
First step: Ship the specific fix identified in the interviews and confirm with 5 of the original churned users that it addresses their issue before any public announcement.
- Tools
- Your product roadmap tool
- Effort
- Varies — 2-8 weeks depending on the fix
- Cost
- Varies by engineering scope
- 05
Re-engage past users privately before a public relaunch
Past users who churned are your highest-intent audience for a relaunch — they already understood the problem, they just hit a wall. Winning a handful of them back first also gives you a credible 'we fixed it' story.
First step: Email the churned list personally (not a mass blast) explaining the specific fix and inviting them back with a personal note from the founder.
- Tools
- Your CRM, a personal email account for the founder
- Effort
- 2-3 days
- Cost
- $0
- 06
Rename or re-position if the brand carries too much baggage
If the original name is strongly associated with the failure in your market (a public shutdown, bad press, or a widely-known churn story), a new name for the relaunched version can be worth the switching cost.
First step: Ask 5 people in your target market what they remember about the original product name — if it's mostly negative or confused, consider a rename.
- Tools
- User interviews, a naming consultant if budget allows
- Effort
- 1 week to decide, 2-4 weeks to execute if renaming
- Cost
- $0-$5,000 for a rename and new domain/branding
- 07
Launch to the narrow segment quietly before going wide
A loud public relaunch to everyone repeats the original mistake of over-promising to an unproven segment. A quiet launch to the narrow segment first lets you catch problems before they're public.
First step: Launch to the narrow segment identified earlier through direct outreach and existing relationships, not a public announcement, for the first 2-3 weeks.
- Tools
- Direct outreach, LinkedIn, existing customer relationships
- Effort
- 2-3 weeks
- Cost
- $0
- 08
Only announce publicly once the narrow segment shows real traction
A public relaunch announcement with no proof behind it just resets the credibility clock. Waiting for a real result from the quiet launch gives you an actual story to tell.
First step: Set a specific bar (e.g. 10 paying customers from the narrow segment, or 30% week-4 retention) before greenlighting a public announcement.
- Tools
- Your analytics dashboard
- Effort
- Ongoing
- Cost
- $0
Sequence
What to do first, week by week.
Diagnose the real failure cause
Interview 10 churned users, agree on a one-sentence failure cause with the team, and identify the narrow segment closest to success.
Fix and decide on branding
Ship the specific product fix, confirm it with past users, and decide whether the original name needs to change based on brand baggage.
Quiet re-engagement
Re-engage past churned users personally and launch quietly to the narrow segment through direct outreach.
Public relaunch, if earned
Only announce publicly if the narrow segment has hit the traction bar set in week 2; otherwise extend the quiet phase.
Avoid
Where this usually goes wrong.
Relaunching with the same broad promise as the first attempt
A product that failed by trying to serve everyone usually needs to narrow, not broaden, on the second attempt. A tighter, more specific pitch to a segment that showed real interest beats a repeat of the original wide net.
Announcing publicly before the fix is proven with real users
A public relaunch that turns out to have the same underlying problem burns credibility twice as fast the second time. Confirm the fix works with a handful of real users before any public statement.
Skipping interviews with people who actually churned
Internal post-mortems without outside input tend to protect the team's original assumptions. The churned users have the actual answer, if someone asks them directly.
Questions
Common questions.
Should I keep the same product name for a relaunch?
Keep it if the name isn't strongly associated with the failure in your market. If it's tied to a public shutdown or well-known bad experience, a new name for the relaunched version is often worth the switching cost.
How do I know if the underlying problem is actually fixed?
Confirm with 5-10 of the original churned users directly rather than assuming internally. If they agree the specific issue they hit is resolved, you have real signal; if the team just feels confident, that's not enough.
Should the relaunch go to everyone or a narrower group first?
Launch quietly to the narrowest segment that showed the most promise in your diagnosis interviews, and only expand publicly once that segment shows real traction — a specific number of paying customers or a retention benchmark.
How long should the quiet relaunch phase last?
Typically 2-4 weeks, enough time to see early retention or purchase behavior from the narrow segment before deciding whether to go public.
What if past users won't respond to re-engagement outreach?
A low response rate from churned users is itself useful data — it may mean the original failure damaged trust more than expected, or the fix doesn't address what they actually cared about. Treat non-response as a signal to re-check the diagnosis.
More playbooks
Other plans worth reading.
Growth plan for a two-sided marketplace
ReadPlaybook · EventsMarketing plan for a B2B conference or trade show
ReadPlaybook · Pre-launchPlan for building a pre-launch waitlist
ReadPlaybook · ExpansionPlan to grow expansion revenue in a SaaS business
ReadPlaybook · InternationalMarketing plan for expanding into a new country
ReadPlaybook · RebrandPlan for launching a company rebrand
ReadElsewhere on gtm.help
Keep exploring.
Tool guides
What to use, what it costs, when it earns its keep.
BrowseTool comparisons
Head-to-head picks for the calls people get stuck on.
BrowseMarketing checklists
Task lists by business type and competitive situation.
BrowseStraight answers
The growth questions founders ask, answered with numbers.
BrowseGet started
Get this ranked for your business.
Paste your URL and you'll have a plan built from your site and competitors in about a minute.