In 2017, I walked into a strategy conversation at Omron Healthcare and proposed a future that required the company to think differently about itself. The organization already knew how to build trusted devices. The question was whether it could also become a software and data platform business without breaking the discipline that made those devices trusted in the first place.
That conversation became HeartVoice: a digital-health spin-off that grew into a $16M business across APAC. My role was to lead the engineering build-out, assemble the team, define the architecture, and guide the platform through both delivery and ISO 13485-driven quality work.
The strategic problem was identity
Large hardware companies do not resist software because they dislike innovation. They resist it because software changes operating assumptions. Revenue models shift. Support models shift. Quality systems have to stretch. Existing teams are forced to learn new behaviors while still delivering the old business reliably.
That was the real challenge. We were not only designing a platform. We were designing a credible path for the organization to behave like a data company without abandoning what made it dependable.
Architecture had to support business reality
The platform needed to integrate device data streams, cloud services, partner APIs, and B2B health workflows across multiple markets. That meant making early choices about tenancy, interfaces, and data handling that could survive commercial expansion rather than just pass a pilot.
I approached those decisions with a bias toward systems that could be explained clearly to both engineers and business stakeholders. In a spin-off context, architecture is not only a technical asset. It is part of the investment case.
Compliance could not be delegated away
HeartVoice also had to move through ISO 13485 and wider regulatory expectations while operating across six ASEAN markets. That made quality and traceability central to engineering, not a separate lane owned elsewhere.
Leading the team through that phase required disciplined documentation, risk management, and decision records that could survive scrutiny. In my experience, this is where many corporate innovation efforts fail. They can imagine the product, but not the operating system required to certify it.
The hardest part of launching a startup inside a large company is not the technology. It is convincing an organization built to optimize a known product to fund the thing that might eventually redefine it.
What the outcome actually proved
The commercial result matters. So does the organizational result. HeartVoice showed that a 90-year-old Japanese manufacturer could spin out a digital-health platform business without sacrificing its quality standards. That took more than enthusiasm. It took engineering discipline aligned with strategy.
That is the part I find most transferable. Innovation inside a large company succeeds when concept-stage ideas are turned into compliant, supportable, commercial systems. Everything else is theater.