Getting a connected health device to launch

What they came with

COR Health came to us with COR One, an at-home ESR testing device, an inherited firmware implementation and a scope that kept growing. The launch date was fixed and close. The device, the image processing and the customer and admin applications all had to work together on day one.

The early decisions

1. Decide what had to be true at launch, and what could follow. The firmware, the device-to-platform flow and the results workflow came first. Everything else was sequenced after.
2. Order the hardware and software work so neither side waited on the other, with the inherited firmware treated as a risk to resolve early, not late.
3. Put a person in front of every result. Admin review sits between the image processing and the notification a user receives.

Who did what

My role

I owned the plan, the priorities and the communication with COR’s founder, and kept the scope honest as it grew.

The team’s role at Code Pros

Our engineers delivered the ESP32-S3 firmware, the Next.js and Django platform, the computer-vision workflow and COR’s store.

The result

99%ESR reading accuracy, confirmed by COR Health

We completed the expanded delivery within COR’s launch deadline. COR estimated that without it, the launch could have slipped by six to twelve months.

The platform now processes images from devices used across countries.