Questions to Ask When Launching a New Product
For the team taking a product to market. Twenty questions to work through before the launch date, covering who is expected to buy it, pricing, what support and billing can actually handle on day one, and how you would know it had failed.
The questions
Open any question for the note
Who do we expect the first buyer to be, and why them?
Why ask it
A named segment with a reason attached is workable; anyone who needs this is not. If the answer covers three different types of buyer, the launch will produce three half-messages and reach none of them properly.
What are those people doing today instead?
Why ask it
The real competitor is usually a spreadsheet, an assistant, or tolerating the problem, rather than another product. Knowing the substitute tells you what your messaging has to overcome and how much switching effort you are asking for.
What do we know from people who have actually used it, not just seen a demo?
Why ask it
Interest expressed in a research call is close to worthless as a predictor of purchase. Ask how many people completed a real task unaided, what they got stuck on, and how many came back a second time without being prompted.
What one sentence do we want a customer to repeat to a colleague?
Why ask it
If the team cannot produce that sentence, the launch materials will each invent their own and the positioning will blur. Test it by saying it to someone outside the company and asking what they think it does.
What are we charging, and how did we get to that number?
Why ask it
Pricing derived from costs or from a competitor's list price is a guess dressed up as arithmetic. You want evidence: what people currently pay for the substitute, what they said when a real number was put in front of them, and what happens to margin at a discount.
In numbers, what has to happen for this to have been worth building?
Why ask it
Agree two or three figures with dates now, while nobody is defending anything. Launch success is otherwise assessed by sentiment, and sentiment after any launch is a mixture of relief and disappointment.
What is the smallest launch that would teach us the most?
Why ask it
A limited release to one segment, region, or existing customer group gives you real usage data with recoverable consequences. Ask what specifically we would learn from a full launch that a staged one would not tell us.
Who has to be ready before we announce: support, sales, billing, documentation, legal?
Why ask it
Launches are usually delayed by the function nobody consulted, and it is often billing or legal review. Ask each function what they need and by when, in their own words, rather than assuming a shared date is enough.
What can support actually answer on day one, and what will they escalate?
Why ask it
Support seeing the product for the first time in launch week is the most common self-inflicted wound available. Ask for the top ten expected questions with approved answers, and who is on call for the ones not on the list.
Has anyone completed a real purchase end to end, with real money?
Why ask it
Checkout, tax calculation, invoicing, entitlement, and renewal all break in ways that are invisible in staging. Do a live transaction, including a refund and a plan change, before anyone announces anything.
How is a potential customer going to find out this exists?
Why ask it
Push for the specific channels with owners and dates rather than a list of tactics. Launches frequently assume an audience that only exists if somebody does the work of assembling it, and that work has a lead time.
What is the plan for the first ten customers, individually?
Why ask it
Early adopters are your best source of testimonials, objections, and product corrections, and they are reachable by hand at this stage. Deciding who calls them, and when, converts a launch into a feedback loop.
Which of our existing customers will be annoyed by this?
Why ask it
New tiers, new pricing, or a feature that used to be included all create a group with a legitimate grievance. Identify them before launch and decide what they are being offered, because they are the ones who post publicly first.
What do we say to people who ask for the thing we cut?
Why ask it
Every launch ships without something, and the answer will be given dozens of times by people who were not in the decision. Write the honest version: what is not there, whether it is planned, and what to do meanwhile.
What happens when it breaks in front of a customer?
Why ask it
You need a named on-call person, a way for support to reach engineering, and a decision about what customers are told. Launch weeks concentrate unusual load and unusual usage patterns, so this will be tested.
What legal, regulatory, or substantiation limits apply to what we say?
Why ask it
Comparative claims, performance figures, and anything touching health, finance, or safety generally require evidence and review. Getting a claim approved takes days; retracting one after publication costs considerably more.
Who has the authority to delay the launch, and on what criteria?
Why ask it
Without a named person and a written bar, launch dates hold on momentum alone and known problems get shipped. Agree the criteria in advance, because judging them the night before is when everyone becomes optimistic.
What is the rollback plan, and who decides to use it?
Why ask it
Some launches can be quietly reversed and others cannot, and the difference matters most where announcements, pricing changes, or migrated data are involved. Establish what is genuinely irreversible so you know where the care needs to go.
What are we going to stop doing in order to support this?
Why ask it
Post-launch work is consistently underestimated: support volume, bug fixes, sales enablement, onboarding calls. If nothing is being dropped, the team is planning to absorb it through overtime and the quality of everything else will fall.
Three months from now, what would tell us this failed, and what would we do about it?
Why ask it
Deciding the failure signal in advance is what makes it possible to act on it rather than explain it away. Also agree the response options now, whether that is repositioning, repricing, or discontinuing, while nobody is personally attached to the outcome.
Working Through a Launch
Practical guidance for the conversation itself
Before You Set a Date
Write the Announcement First
Draft the customer-facing announcement and the pricing page before the launch plan exists. If the sentences are hard to write, the positioning is not settled, and no amount of campaign planning will fix that. It also surfaces the claims that will need evidence or legal review, which is the longest lead time in most launches.
Get Ten Strangers Through the First Five Minutes
Watch people who have never seen the product attempt the primary task without help. Do not answer their questions; note where they stop. Almost every avoidable launch problem is visible in that exercise, and it costs a day. Teams that skip it discover the same problems in public a fortnight later.
Interview the Functions That Get Blamed Afterward
Support, billing, and legal know exactly what will break because it broke last time. Ask each what they need and how long it takes, and put their lead times into the plan rather than around it. This is also the cheapest way to find out that the launch date is already impossible.
Set the Numbers and Take a Baseline
Two or three measures with dates, recorded somewhere durable, before launch. Without a baseline the review in three months becomes an argument about interpretation, and the loudest interpretation is usually the one belonging to whoever most wanted the launch.
Launch Readiness Checks
- 1A real purchase completed with real money, including invoice, refund, and plan change.
- 2Support armed with the top ten expected questions and approved answers, plus an escalation path with a name on it.
- 3Sales able to describe who this is not for, which prevents the worst kind of early customer.
- 4Documentation and pricing page live and reviewed by someone who did not write them.
- 5Any claim requiring substantiation reviewed and approved, in writing.
- 6Monitoring and alerting in place for the new paths, not only the old ones.
- 7A named on-call owner for launch week, and a decision on what customers are told during an incident.
- 8The list of existing customers affected by the change, with their message already drafted.
Warning Signs in the Answers
- A target customer described in terms broad enough to include almost everybody. Broad targeting is usually the absence of a decision rather than the presence of ambition.
- Evidence that consists entirely of people saying they liked it. Enthusiasm in a research call and willingness to pay are only loosely related.
- A date chosen for a conference, a quarter end, or an executive's calendar. Ask what would be cut to hold it, and you will find out what is actually being sacrificed.
- Nobody able to name who can delay the launch. That means it cannot be delayed, which means known problems will ship.
- Support and billing hearing about the launch from the announcement. Every hour saved by not consulting them costs several in the first week.
- A plan that ends on launch day. The work that determines whether the product survives happens in the month afterward.
- Any pricing conversation where nobody has said a number out loud to a real prospective customer.
Common Pitfalls
Launching to Everyone at Once
A staged release to one segment or region gives you real usage, a small support load, and the ability to fix the obvious problems before the wider audience sees them. Full launches make sense when there is a genuine reason for simultaneity, and otherwise concentrate all the risk into a single week with no recovery room.
Confusing Launch Activity With Demand
Announcement traffic, sign-ups, and press coverage all spike and then decay regardless of whether the product is any good. Look instead at second-week retention, repeat use, and conversion from trial. The launch spike tells you about your distribution, not about your product.
Neglecting the Existing Customers
Adding a paid tier, changing what is included, or shipping something that overlaps with what people already bought all generate a specific and vocal grievance. Decide in advance what those customers are offered, and tell them before the public announcement rather than after they read it.
Treating Post-Launch as Someone Else's Problem
The team that built it is the only group that can triage the first weeks properly, and if they have already moved to the next project the support burden lands on people who cannot resolve it. Hold capacity deliberately for four to six weeks and say so in the plan.
Skipping the Review
Three months on, go back to the numbers you wrote down and read them honestly, including the ones that measured the wrong thing. This is uncomfortable and it is the only mechanism by which an organisation's launches get better rather than merely more frequent.