Three Ways to Ship

Your customer said yes. You need hardware in the field by Q1. Not a radio to evaluate, not a platform to compare: hardware, in an enclosure, on a wall, reporting. There are three ways to get there, and each one costs you something different in time, in margin, and in who owns the customer afterwards. Ship a catalog device and you are live in weeks, but what you own is the application. Put your own firmware on someone else's hardware and you own the behaviour and the data. Build your own product and you own all of it, provided you can carry the development and the certification. This session walks all three, with shipped deployments behind each: a sub-500 EUR pilot that caught a production line stoppage in two weeks, real-time OEE on twenty machines that were never networked, and an integrator who kept the customer while we stayed invisible. It closes on two certified products standing on our booth that carry someone else's name, one built to medical requirements and one for explosive atmospheres, and on what the Cyber Resilience Act now asks of whoever holds the record. What you will leave with A way to decide which of the three routes a given project actually needs What each route costs in time to first install, and where the margin sits What certification and per-unit records look like once the CRA applies