Quick answer
Pre-launch cost is usually a stack, not a single project fee.
Pre-launch requirement = engineering + prototypes + tooling + compliance + inventory + launch work + contingency
Teams usually under-budget because they remember the exciting parts and forget the expensive supporting work that sits around them.
The six blocks most teams should expect
- Design and engineering: concept development, CAD, iteration, testing support, and supplier-ready detail.
- Prototype builds: multiple prototype rounds, fixtures, sample tools, and validation parts.
- Tooling and setup: mould tools, jigs, fixtures, or production setup costs.
- Compliance: test labs, standards work, documentation, and re-test risk.
- First inventory: stock, packaging, inserts, and pre-launch working capital.
- Launch work: imagery, packaging, copy, early commercial assets, and market-entry effort.
Prototype count is usually underestimated.
The first build rarely answers every important question.
Compliance arrives later than expected.
Teams often budget the first test but not the cost of fixing and re-testing.
First inventory is not just product cost.
Packaging, labels, inserts, and freight decisions often land here too.
Contingency is not optional.
It is the acknowledgement that physical product development creates surprises.
How to use the estimate well
- separate pre-launch cost from recurring monthly overhead
- keep the cost blocks visible instead of collapsing them too early
- connect the total to runway and cashflow, not just fundraising ambition