Product development: agree goals, outputs and next steps
Assessing an idea, building a working prototype and preparing series production are different orders. Describe the product, its users and the current position. A clearly bounded next stage is easier to compare than a general promise of market readiness. Existing products can also be improved in a targeted way.
Define the problem and desired result
What should the product do, and for whom? Describe function, use and important constraints. Separate essential requirements from wishes. For an existing product, specify the problem or intended change. A visual presentation, functional proof and production package are different outputs.
Explain the starting point
The starting point may be an idea, sketch, CAD model, sample or series product. Explain what works and what remains open. Existing records can be reviewed later; no confidential files are required initially. Clarify whether to continue prior work or assess an independent approach.
| Starting point | Useful next step |
|---|---|
| Idea | Clarify requirements and feasibility |
| Concept or model | Define unresolved functions and tests |
| Sample or series product | Bound the change and required evidence |
Coordinate disciplines and interfaces
Mechanics, materials, electronics and embedded software may work together. A housing alone needs different services from a connected device. Assign interface coordination and specify existing components to reuse. Manufacturing equipment, test rigs and supplier documentation are not automatically included.
Specify prototypes by purpose
A visual model may show shape and use without every function. A functional sample may answer selected technical questions without series-like manufacture. Agree the number, variants and test purpose of ordered samples. Material and manufacturing method should serve the goal. A successful sample trial does not automatically establish series readiness or approval.
Plan test criteria and decisions
Define how a stage will be assessed and who decides. Use and target markets may introduce specific requirements; assessment should have a defined scope. Separate internal trials from external testing. Agree what follows a negative result and whether redesign is included.
Agree confidentiality and usage rights
Describe the idea generally at first. Before sharing confidential details, clarify responsibilities, confidentiality and rights to existing and new results. Owning a sample is not automatically the same as using its design or software. Agree transfer to manufacturing partners too. A development quote does not replace an individual IP assessment.
Compare costs by development stage
Compare the same outputs and assumptions. Separate development work from prototype materials, tooling and external testing. State included reviews and revision rounds. A concept price cannot be directly compared with a complete manufacturing package. Possible funding is a separate assessment, not a promised part of a general development quote.
| Item | Clarify in the quote |
|---|---|
| Development | Outputs, variants and revisions |
| Samples and tests | Number, material and test purpose |
| Transfer | File formats, rights and manufacturing records |
Define handover and continuation
Agree the files, samples and evidence to hand over. Record tested variants and unresolved points. Later manufacture needs versions, bills of materials and responsibility for changes. The next supplier should be able to reuse agreed outputs. Plan a clear decision before the next development stage.
- Before comparison. Describe the product, users, starting point and next output.
- Before collaboration. Agree rights, confidentiality, tests and handover.
Frequently asked questions
Is an idea enough for an enquiry?
Yes. Describe its purpose and next stage without confidential detail.
Is a prototype ready for series manufacture?
Not automatically. It may demonstrate only selected functions or shape.
Can only one part be developed?
Yes. Define that part and its interfaces to existing components.
Do I automatically own every right?
That must be agreed. Samples, prior knowledge and new data may involve different rights.
How can quotes be compared?
Ask for the same outputs, variants, tests and handover records.
Are approvals and funding included?
Only under a defined scope. A development quote guarantees neither approval nor funding.
