Skip to content
← Engineering notes

Prototype to production

From proof of concept to production: what has to change

14 November 2026 · Shalaka engineering team

A proof of concept is built to answer one question quickly: does this work? It often runs on a development kit, in a 3D-printed box, with firmware that was flashed over USB by the engineer who wrote it. That is the right way to build a PoC. It is also why a working demo is still a long way from a product. This is the list we go through when a PoC is approved for production.

Firmware

  • Over-the-air updates with a way back. Two firmware slots (A and B), a check that the new image boots and connects, and an automatic rollback if it does not. A failed update in the field should never need a site visit.
  • Security. Secure boot and flash encryption where the chip supports them, unique credentials per device, and JTAG and serial debug ports closed or locked.
  • Behaviour on power loss. What happens if power drops during a write, an update or a relay operation. The unit should come back in a known state.
  • Logs you can read remotely. Reset reasons, error counters and firmware version reported with the data, so field problems can be diagnosed without a laptop on site.

Hardware

  • Test points and a test jig. Every unit off the line should be powered, programmed and checked in a fixed sequence, in under a few minutes, by someone who did not design it.
  • Design for manufacture. Component placement and footprints that the manufacturer’s process can handle, panelisation, fiducials and markings.
  • Sourcing. Each part checked for availability, lifecycle status and a second source. A single-source part with a long lead time can stop a production run.
  • Enclosure and environment. An ingress rating that suits the site (IP54 indoors in a dusty plant, IP65 or IP67 outdoors), heat in a closed box, condensation, cable entry and mounting.

Process and paperwork

  • Approvals. EMC, electrical safety where the product needs it, and wireless approval for any radio. Pre-compliance testing before the formal test saves expensive repeats.
  • Provisioning. How each unit gets its serial number, its credentials and its link to a customer account, at the factory or at installation.
  • The handover pack. BoM, pick-and-place files, Gerbers, assembly drawings, test procedure and the firmware build instructions, so the manufacturer and your own team can work without us if they need to.

None of this is visible in a demo, and most of it is invisible to the end user. It is the difference between a hundred units that work and a thousand that keep working.


If you have a proof of concept that works and a production run ahead, book a discovery call.

Tell us what you are building.

A 30-minute discovery call with an engineer. We reply within 48 hours.

Book a discovery call