Realistic timelines for embedded and IoT product development: what each phase involves, what governs the schedule, and which shortcuts genuinely save time versus cost it.
A realistic path from idea to manufactured embedded product is typically measured in months: working prototypes commonly land within the first few months, and production-ready hardware — tested, certified and manufacturable — usually takes six months to a year depending on complexity and certification requirements. Simple module-based devices move faster; certified medical and industrial products take longer. Claims of idea-to-production in a few weeks are describing a demo, not a product.
Rarely the visible engineering. The recurring culprits: changing requirements mid-design (each "small" change ripples through hardware, firmware and test), component lead times discovered late, certification failures that force respins, and the last 10% of firmware — the edge cases and field bugs that separate a demo from a product. Teams that have shipped before build these into the plan; the schedule then survives contact with reality.
Real: certified radio modules instead of custom RF (weeks of certification saved), proven reference designs, parallel hardware/firmware development, and ruthless first-version scope control. Traps: skipping the specification (you'll write it anyway, later, in change requests), skipping EMC pre-scans (the lab will find it for you at £-per-day rates), and hiring the cheapest engineering you can find — the rework loop is the most expensive schedule item there is, a pattern we see weekly in rescue projects.
The same way you get a real cost: a scoped plan against a written specification, with milestones you can verify. Every quote we issue at Inventors Tech comes with one. The first consultation is free — bring the idea, and you'll leave with an honest view of the road, including the parts other timelines leave out. Related reading: what IoT development costs.
Talk it through with an engineer — free, honest, no sales pitch.