Start with the closest finished product: alarm and detection devices for connected smoke detection, heat detection, presence sensing or water-leak alarms; V16 Emergency Warning Lights for roadside warning and DGT reporting programs; smart lock products for connected access; GPS pet tracking devices for location services; or AI holographic projection booths for managed interactive displays. The product page shows the main user, configuration and validation decisions.
Clarify the Decisions That Shape Your Connected Product.
Use these answers to choose a product starting point, define what can change, set validation boundaries and prepare a useful first project brief.
Product choice
Choose module-only supply when your team already owns the device hardware, antenna, firmware, app or cloud integration and production validation. Choose a finished-product program when those layers need to be coordinated around one device configuration.
Customization
Depending on the product, customization can cover the enclosure, interfaces, PCBA, wireless bands, antenna, firmware, app identity, cloud accounts, dashboards, alerts, packaging, documentation and production tests.
Brand identity can be scoped across the enclosure, packaging, onboarding, app screens, dashboard, account roles and product documentation. The agreed scope follows the selected product and software model.
Software and platform
Yes, when device identity, authentication, data fields, commands, errors and operating ownership are defined. The integration scope records what stays in the existing system and what changes in the device, firmware or interface.
Source-code access, account control, hosting, APIs, data ownership, retention and operating responsibilities are commercial decisions. They must be written into the project agreement.
Sample and production
A configured sample validates the architecture and core user experience. A pilot adds controlled materials, software versions, field validation, fixtures and repeatable tests. Production starts from an approved specification, released versions and acceptance record.
Provide the closest product, target market, intended users, required functions, software scope, connectivity assumptions and sample goal. Unknown details can remain open until they affect the selected configuration.
Commercial inputs
The target market, enclosure, radio bands, battery, tooling, software scope, tests, packaging, sample goal and order forecast shape certification work, MOQ, schedule and pricing. Final figures require a defined configuration.
Turn the open decisions into a project brief.
Choose the closest finished product, then record the market, functions, software scope and sample goal you know today.