Design-to-launch: intake and evidence form
This form starts a new product, service or variant properly. It captures what is being asked for, who asked, what the customer needs, the target price and cost, and the evidence behind the request, so that design work does not begin on a vague idea. The person who raises the request fills it in and the owner approves it.
When to use it
Use it before any design, sampling or purchase for something new, including a change to an existing product that affects its price, size, ingredients or process. A small request deserves a short form, but it should still be written down and dated.
The template
| Field | What to enter | Source record | Owner |
|---|---|---|---|
| Request title | A short name for the product, service or change | Request note | Requester |
| Raised by and date | Name, role and the date | Request note | Requester |
| Customer need | What the customer is trying to do, in their words | Customer message, call notes | Sales head |
| Target customer | Who will buy it and roughly how many | Enquiry history, market notes | Sales head |
| Target selling price | Price per unit in ₹ and the lowest acceptable | Price list, competitor prices | Owner |
| Target cost | Highest cost per unit in ₹ and the margin expected | Past costing sheets | Accounts lead |
| Deadline | Date by which it must be available and the reason | Customer commitment, season | Project lead |
| Reference material | Photos, samples, drawings or competitor products | Shared folder | Design lead |
| Limits | Machine, space, skill, material or budget limits that apply | Operations plan | Operations head |
| Approval to start | Owner's decision, the budget for design and trials in ₹, the date | Approval note | Owner |
How to fill it
- Customer need: quote the actual words from a customer, not your own view of what they should want.
- Target selling price and Target cost: write rupee figures per unit. If the cost is not known yet, write your best estimate and mark it as an estimate.
- Deadline: give the date and its reason. A deadline with no reason is hard to defend when the scope grows.
- Reference material: keep copies in one named folder and list the file names here.
- Limits: include any licence, labelling or safety approval the product might need. Check the current rule on the official portal or with your CA before acting where it concerns a regulated product.
Example row
| Field | Entry |
|---|---|
| Request title | Half-litre cold-pressed groundnut oil pack |
| Customer need | "Our shop customers want a smaller bottle than the one litre, under ₹250" |
| Target selling price | ₹235 per bottle |
| Target cost | ₹185 per bottle, margin about ₹50 |
| Deadline | 1 Dec 2026, before the winter order season |
| Approval to start | Owner, budget ₹15,000 for samples, 16 Oct 2026 |
Review and sign-off
- The owner reviews and signs the form before design starts; the accounts person checks the cost figures.
- Look at all open requests together each month and drop those that have lost their reason.
- Escalate when the target cost is above the target price less the margin you need, when the deadline cannot be met with current limits, or when approval is needed for spending above the budget.
Keeping it up to date
- Add a dated note each time the request changes, including the price, cost or deadline.
- Link the form to the brief, specification and later test reports so one folder tells the whole story.
- Keep requests, approved or declined, for the period your CA or the law requires.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →