Chapter 7: New Product Launch
New product launch cases are tempting because everyone has ideas.
The client could add features, change packaging, run ads, bundle, pilot, partner, or go viral. But a launch is not a creativity contest. It is a business decision under uncertainty.
The question is:
Should we launch this product, and how?
The intuition
A new product succeeds when it solves a real customer problem, fits the company's capabilities, and can scale profitably.
Use this model:
- First test whether customers need it.
- Then test whether this product solves the need better than alternatives.
- Then test whether the economics and go-to-market model work.
- Then decide whether to launch, pilot, change the product, or stop.
The strongest candidates do not jump to marketing. They first ask whether the product deserves to exist.
If you remember one line from this playbook, make it this:
How to recognize it
You are probably in a new product launch case when the prompt says:
- Should we launch a new product?
- The client has developed a new service.
- A company wants to expand its product line.
- A product pilot performed well or poorly.
- The client wants to enter a category with a new offering.
New product launch overlaps with market entry. The difference is emphasis: product launch focuses on customer need, adoption, economics, and rollout of the offering.
The client question underneath
The client is asking:
Will customers adopt this product, will the economics work, and what launch path reduces risk?
The answer should include whether to launch, who to launch to first, how to launch, and what to measure.
The first 2 minutes
Clarify:
What customer problem is the product meant to solve?
Is the goal revenue, profit, retention, market share, brand-building, or strategic learning?
Is this a fully built product, a concept, or a pilot?
Are we deciding whether to launch at all, where to launch first, or how to scale?
The core structure
Use this as the base map. A launch case should answer whether the product deserves to exist before it jumps into channels, marketing, or rollout tactics.
This structure keeps the case grounded. A product can be exciting and still fail because customers do not need it, the economics are weak, distribution is hard, or the launch cannibalizes a better product.
If the answer starts to look like yes, then the case can shift into launch design: which segment to target first, which channel to use, what pilot to run, what metrics to track, and what conditions must be true before scaling.
The analyses that usually matter
Use the analyses to turn the launch idea into a decision, not to brainstorm more tactics. A strong launch answer usually needs a few judgment moves:
- Define the adoption proof: Do not stop at "customers like it." Look for evidence of trial, repeat purchase, willingness to pay, switching from alternatives, and the occasion that would make usage frequent enough.
- Separate love from economics: A product can test well and still be a bad launch if production cost, channel margin, marketing spend, support cost, or returns destroy the unit economics.
- Check the route to the customer: The best product still struggles if the client lacks the channel access, shelf space, sales motion, operations, or support model needed to reach the target segment.
- Size the downside, not just the upside: Cannibalization, brand confusion, quality issues, operational distraction, and competitive response can erase the value of a launch.
- Design the smallest useful pilot: The pilot should test the riskiest assumptions: demand, repeat behavior, price, margin, channel execution, operations, and customer feedback.
- Name scale conditions: The recommendation should say what must be true before a broader rollout, such as repeat rate, margin, acquisition cost, operational reliability, or cannibalization staying below a threshold.
Pilot logic is often useful, but it should not be vague. Launching to a small segment, region, channel, or customer group is only helpful if it measures the assumptions that could actually change the decision.
What weak looks like
Prompt: A coffee chain is considering launching a bottled ready-to-drink latte in grocery stores. Should it?
Weak: "They should launch because customers like coffee, and grocery stores would help them reach more people. They can market it with their brand."
This assumes demand and skips economics, channel capability, competition, and brand fit.
What strong looks like
Strong: "I would evaluate the launch across five areas. First, customer need: who would buy bottled lattes, on what occasions, what alternatives they use today, and whether they would repeat and pay. Second, product fit: whether our product is meaningfully better or different through taste, price, packaging, convenience, and brand trust. Third, economics: reachable market size, wholesale price, production cost, retailer margin, marketing spend, and expected repeat purchase. Fourth, go-to-market: whether the coffee chain can win in grocery through distribution, shelf placement, operations, and quality control. Fifth, launch risk: cannibalization of store visits, competitive response, brand dilution, and what a regional pilot would need to prove before scaling."
This answer treats launch as testable, not magical.
Common traps
Do not assume "new" means valuable. Do not skip customer adoption. Do not forget channel economics. Do not ignore cannibalization. Do not recommend national launch when a pilot would be smarter. Do not focus only on revenue and forget production, support, returns, or quality risk.
Next step
New product launch closes the main case type playbooks. You now have the seven recurring patterns: profitability, market entry, revenue growth, pricing, cost reduction, M&A, and new product launch. Next, move to Bring It to Life. The point now is not to read more material forever; it is to use these patterns together in live cases, because real prompts often blend them.