How to plan a new product or service launch
Launching something new is exciting and easy to get wrong. A price set on instinct, a service nobody on the team knows how to deliver, or a design that was never approved can turn a good idea into a loss. This guide gives a simple sequence for planning a launch so that the need, the cost, the pilot and the training are all settled before customers arrive.
The example is a salon chain with four outlets adding a hair-spa service.
Why this matters
A launch spends money before it earns any: products, training, marketing and staff time. Doing the groundwork first costs little compared with a failed launch. Writing down the specification and the cost also stops the "it was supposed to be cheaper" argument after the fact.
Before you start
- A short note of the customer need: who wants this, what they ask for today and what they pay for alternatives.
- A specification: what is delivered, how long it takes, the products used and the quality standard.
- A cost sheet with materials, labour time, overheads and an allowance for wastage.
- A pilot record template to note results and customer feedback.
- A product owner, a technical lead who knows the work, and an approver for price and spend.
Step by step
- Write down the customer need. The product owner collects what customers have asked for, from repeat requests, complaints and competitor offers. Note who the offer is for and what they would pay.
- Document the specification and cost drivers. The technical lead writes what exactly is delivered and in what steps, including the time per customer and the materials per service. List what makes the cost rise, such as imported products or a senior stylist's time.
- Run a pilot. Try the service in one outlet for two or three weeks with a few staff and willing customers. Record time taken, material used, problems and customer comments in the pilot record. The commercial approver reviews it and decides whether the offer is ready.
- Cost it properly and set the price. Using actual pilot figures, the product owner fills the cost sheet and proposes a price with the margin. The approver signs it off and the service is added to the price list and menu.
- Train the delivery teams. The technical lead trains every staff member who will deliver or sell the service, with a practical demonstration and a short check. Keep a sheet of who has been trained and on what date.
- Launch and review. Start with a clear date and a first-month review. The product owner and technical lead compare actual cost, time and feedback against the plan, and adjust the price or the method if needed. If the service involves licences, product registrations or advertising rules, check the current rule on the official portal or with your CA before acting.
Who does what
| Role | What they do | Record they own |
|---|---|---|
| Product owner | Defines the need, proposes price, runs the launch review | Customer need note and cost sheet |
| Technical lead | Writes the specification, trains the teams | Specification and training record |
| Commercial approver | Reviews the pilot and approves price and spend | Pilot record and launch approval |
Common mistakes
- Launching a design or method that nobody senior has approved, so each outlet does it differently.
- Using estimated costs in the price instead of pilot results.
- Forgetting wastage, extra time or returns in the cost sheet.
- Training only the manager, then expecting the team to deliver.
- Skipping the pilot because the idea feels obvious.
How to tell it is working
- Unapproved designs. Count the offers, designs or service variants in use that lack a signed approval, and divide by the total offers in use. The answer should be zero before launch day.
- Cost overrun. Compare the actual cost per unit or per service in the first month with the cost on the approved sheet. Subtract the planned from actual and divide by planned. A positive figure shows a leak: more time, more material or discounts.
- Untrained team. Take the list of staff who deliver the service and count those without a recorded training date. Divide by the total delivering. Aim for zero before the first customer.
Questions people ask
Who owns design to launch?
The product owner owns the launch from idea to review. The technical lead owns the quality of the specification and training, and the commercial approver owns the decision on price and spend.
What is the minimum record for design to launch?
A customer need note, a specification, a pilot record, an approved cost sheet and a launch approval with the date and the names of the people trained. Anything less leaves you guessing later.
When should a case stop?
Stop at the pilot if customers do not want it, or the cost is above what they will pay. Stop before launch if the team cannot deliver it to the standard. Record the reasons, since you may revisit them.
Can a spreadsheet support this stream?
Yes. One workbook with tabs for the need, the specification, the cost sheet and the training list is enough for a small business, as long as only the approved version is in use.
What should the owner review?
Review the pilot results, the cost sheet against the proposed price, the training list and the first month's numbers. Approve the launch only when all four are on the table.