Why great healthtech products still fail without great operators

Innovation gets most of the attention in healthtech. Founders celebrate product launches. Investors celebrate funding rounds. Companies proudly announce new features and partnerships.

These moments matter because they represent progress, but they rarely determine whether a product will succeed in the long run.

After spending more than a decade building enterprise software for hospitals and health insurers, I have come to believe that the work begins after the product has been built. A successful launch does not guarantee successful adoption. In healthcare, building the technology is often the easy part. Getting people, processes, and organisations to embrace it is where the real challenge lies.

One of the biggest assumptions I made at the beginning of my journey was that the healthcare industry was waiting for technology. Looking back, I realise how wrong that assumption was.

The need for better systems was obvious. Many healthcare processes were still manual, information was scattered across departments, and inefficiencies existed almost everywhere. It seemed logical that organisations would welcome technology that could simplify their operations.

The reality was very different. Many healthcare providers were not deciding whether to adopt technology. They were deciding whether they could afford to survive another month. Hospitals were dealing with rising operational costs, unstable infrastructure, and shrinking margins. Technology often competed with far more immediate priorities.

I remember one hospital’s managing director trying to convince us to deploy our Electronic Medical Records solution for free. He didn’t doubt the value of the software; he simply couldn’t justify another expense after spending so much on diesel to keep the hospital running.

Another organisation was genuinely interested until they realised implementation would require purchasing laptops and providing reliable internet access for staff. The software wasn’t the obstacle. Everything around it was.

In another case, discussions ended abruptly when a hospital shut its doors after its landlord increased the rent threefold. Experiences like these forced me to rethink what it means to build healthtech in Africa.

Technology does not exist in isolation

Every product is introduced into an operating environment, and that environment often determines whether the product succeeds or struggles.

Another assumption I made was about the size of the market. Like many founders, I initially believed the opportunity was much larger than it turned out to be. Over time, I realised many healthcare organisations operate relatively small businesses with limited cash flow. Those realities influence how they prioritise investments, including technology.

One particular implementation reinforced this lesson in a way I will never forget.

We were engaged to replace the enterprise software used by a large healthcare organisation. During development, everything progressed according to plan. Our team delivered the agreed functionality, and we were confident as we moved into implementation.

Once deployment began, it became clear that the workflows built into our platform did not fully align with the client’s operational expectations. Addressing those gaps meant rebuilding significant parts of the system from the ground up. It required months of additional work and considerable resources, yet changing the commercial terms midway through the project wasn’t an option without risking the relationship altogether.

We eventually delivered a solution that worked for the organisation, and today they remain grateful for the effort invested in getting there. Looking back, however, that experience fundamentally changed how I think about enterprise software.

Customers are rarely buying software alone. They are trusting you with processes that keep their businesses running every day. If your product doesn’t fit those realities, technical excellence alone will not save the project.

That lesson became even clearer with our very first client. Like many founders, I spent countless hours thinking about features, user journeys, and product roadmaps. Everything looked good on paper. Then the product went live.

Almost immediately, situations emerged that we had never anticipated during development. Users approached problems differently. Existing workflows varied from one organisation to another. New requirements surfaced almost every week. That experience taught us to build differently.

Today, we involve stakeholders throughout development rather than waiting until implementation to gather feedback. Continuous iteration has become part of our culture because experience has shown us that users will always reveal realities that product teams cannot predict from a meeting room.

Technology alone does not transform organisations

After working with 26 HMOs, more than 3,000 healthcare providers, and healthcare operations serving approximately 28 million subscribers, recurring patterns begin to emerge.

One of the most striking is how disconnected many healthcare organisations remain internally. Departments that should work closely together frequently operate independently. Administrative processes are duplicated across teams, creating unnecessary delays and increasing the workload for everyone involved.

Another recurring pattern is the continued dependence on paper records. Even organisations that have invested significantly in digital systems often continue maintaining paper-based processes alongside them. Digital transformation becomes incomplete because existing habits remain unchanged.

This is one of the reasons implementation deserves as much attention as product development.

Technology can bridge operational gaps, but only if organisations are willing and able to change how they work. Infrastructure challenges, financial pressures, and organisational culture all influence that journey. The numbers reflect this reality.

In 2025, our platform processed 819,246 healthcare claims. By June 2026, monthly claims volume had reached 73,491, while more than 50,000 API transactions were processed every day. Across deployments, claims processing efficiency improved by 95%, while manual administrative work, reconciliation, and enrolment processes improved by approximately 97%.

Those figures are not important because they demonstrate scale. They matter because they represent something much more practical.

Less time spent processing paperwork, faster claims, quicker enrolment, reduced reconciliation effort, and more time for healthcare professionals to focus on delivering care instead of managing administrative tasks.

Some of the biggest operational improvements also come from solving problems that most patients will never see.

One recurring bottleneck across implementations has been tariff uploads and service code matching between providers and HMOs. It sounds like a small technical issue, but inconsistent coding structures can slow approvals, delay claims, and create unnecessary reconciliation work. Solving challenges like these often has a greater operational impact than introducing another product feature.

These observations are not unique to our own experience. Kehinde Oladejo, IT Infrastructure and Network Manager at Hygeia HMO, recalls how a ransomware attack forced the organisation to reconsider its reliance on on-premise infrastructure and accelerate its move to the cloud. What started as a security incident became an operational transformation.

Similarly, Dr Kene, Executive Director of Clearline HMO, observed that years of operational experience embedded within the platform helped guide implementation through proven workflows rather than requiring every organisation to learn the same lessons from scratch.

Their experiences reinforce an important point: technology alone does not transform organisations.

Successful implementation requires trust, collaboration, patience, and continuous improvement. It requires understanding that healthcare is not simply another software market. Every deployment affects people, processes, and ultimately patient care.

For founders building technology in healthcare or any other operationally complex industry, my advice is straightforward.

Validate your assumptions before scaling. Prove your concept before committing significant resources. Product-market fit matters far more than ambitious roadmaps.

Healthcare moves differently from consumer technology, logistics, or financial services. Progress should be measured with that reality in mind rather than against industries with completely different operating environments.

Finally, choose your investors carefully. Healthcare rarely delivers the rapid returns many venture investors expect. Founders need partners who understand the pace, complexity, and long-term nature of building sustainable healthcare businesses. Patient capital often creates better outcomes than impatient expectations.

Innovation will always remain important, but after years of building, implementing, rebuilding, listening, and learning, I no longer believe that great healthtech products succeed because they are technically impressive. They succeed because they fit the realities of the people expected to use them.

Obinna Osuji is the co-founder and CEO of Medismarts. He has over 10 years of experience building healthcare technology solutions that help healthcare providers, HMOs, and businesses improve operational efficiency and deliver better healthcare services across Nigeria.