Getting a connected health device to launch
COR Health had a launch date that could not move, an inherited firmware build and a scope that kept growing.
- Based in
- United States
- Sector
- Connected health
- My role
- Scope, priorities, delivery and the relationship with COR’s founder
How it started.
COR Health was preparing to launch COR One, an at-home ESR test. The launch date could not move. The firmware came from an earlier team, and the scope kept growing as the product came together. The device, the results and the apps around them all had to work on day one.
The calls that mattered.
- The call
Decide what had to be true at launch
Not everything could ship on day one. The flow from device to result came first, and everything else was sequenced after it, so the date could hold.
- The call
Treat the inherited firmware as the biggest risk
A problem found late would have moved the launch. We dealt with it early, and ordered the hardware and software work so neither side waited on the other.
- The call
Put a person in front of every result
For a health product, trust matters more than speed. Every result is reviewed before it reaches the user.
What happened.
COR One launched within the deadline. COR estimated that without this work, the launch could have slipped by six to twelve months.
The work continued after launch, with devices now in use across countries.
High quality, on-time, on-budget. They have the highest quality project management. Low friction.
How it was built
My team at Code Pros delivered the firmware, the platform and the computer-vision workflow behind the results, reaching 99% ESR reading accuracy, confirmed by COR Health.
Working through something similar?
A 20-minute call, no preparation needed. Tell me what you are trying to achieve and where things stand.
Book a 20-minute call