Connected devices are a systems problem wearing a hardware costume
The Work, With Dates
Case studies are linked where they exist
Mitsubishi Comfort
A platform transformation across mobile, web, and IoT adapter firmware. We rebuilt the communication layer between the platform and its device fleet and migrated the fleet to AWS IoT Core. The engagement began with an audit in November 2023, started building in February 2024, and is ongoing. Within six months of launch, NPS rose more than 20 points.
Phyn by Belkin
Belkin brought us in in 2016, before there was a product. Phyn monitors a home's plumbing 240 times per second. We built the MVP that proved the idea: device pairing, the sensor data path, the service behind it, and the app. Phyn went to market from there.
Flume
Mobile experiences for connected-home water monitoring, Bluetooth included.
The NPS score increase was remarkable, over 20 points in just six months. But what really impressed us was how ClearSummit connected the technical improvements to real customer experience outcomes.
What This Work Involves
The Four Layers That Have to Agree
A connected product fails at whichever layer was somebody else's job.
Firmware and Fleet
The code on the device and the machinery that keeps thousands of them connected, updated, and telling the truth about their state.
The Data Path
Sensor readings are only useful if they arrive, in order, at something built to keep up. High-frequency telemetry is a backend problem before it is a hardware one.
The App in Hand
The person who owns the device judges the whole system by the app. If pairing is flaky, the product is flaky, whatever the hardware team shipped.
Own the Seam
Most connected-product trouble is an ownership gap.
The hardware team owns the device. The app team owns the app. Nobody owns the seam, and the seam is where connected products live or die. On Mitsubishi Comfort, the fix was not one heroic component: it was rebuilding the communication layer, the app, and the internal processes as one system.
That is what a standing product team is for. One group accountable for the whole path, from the sensor to the screen.
Is This You?
We're a good fit if: You have a device in the field, or one on the way, and the software side needs to catch up with the hardware. Firmware, fleet, cloud, and app need to move together and nobody owns all four.
We're not a good fit if: You need electrical engineering or industrial design. Our work starts where the hardware meets software.
Tell Us About the Device
Describe what it does and where the software side stands. We'll tell you what we think the real problem is, which is sometimes smaller than it looks.