For a long time, I believed something that most founders and innovators in health tech believe, like an unspoken rule of logic, that if you build something that genuinely improves clinical results, reduces workload and shows real value, then adoption will follow.

Most health tech products in India do not fail because the technology is weak. They fail because the system they are trying to enter is far more complex than any software architecture. That system is human, layered, political and invisible to those building from the outside. I did not understand this early enough.

The Illusion of Rational Decision-Making

When you first approach a hospital with a health tech solution, everything appears structured. There are meetings scheduled, product demos, formal committees and approvals. There are follow-up emails and procedural steps that give the entire journey a sense of order. It gives the impression that decisions are made based on data, outcomes and efficiency. But under this formal structure lies a very different reality. In many Indian hospitals:

• Decisions are not really democratic
• Authority does not always match job titles
• Agreement does not guarantee action

You may walk out of a meeting thinking you have secured approval, only to realize weeks later that nothing has moved forward because what you heard was a “yes” in conversation and not a “yes” in power.

Authority is Not Always Visible

One of the most common assumptions in health tech sales is that authority is tied to designation. If someone is a department head, administrator or senior clinician, they are thought to be the decision-maker. But hospitals here do not really function through such hierarchies alone.

A senior consultant who does not attend your demo might still hold more power. A department head might agree publicly but resist implementation privately. An administrator might support you but lack the authority to push adoption.

And sometimes, the real decision-maker is not even in the room. This is where many products get misread. They optimize for the visible layer such as the meeting, the demo and the formal approval team, while completely missing the invisible architecture of influence that actually governs adoption. Here, influence often matters more than designation. If you do not get this early, you don’t lose because your product is weak but because you were never speaking to the real system in the first place.

“Yes” Does Not Mean Adoption

Getting positive feedback is one of the most misleading signals in health tech. In hospital systems, saying a direct “no” is mostly avoided because rejection can feel socially or professionally uncomfortable. So instead, you get a soft “yes” one that keeps the conversation going without committing to change.

For a builder or founder, this is dangerous because it creates momentum without any movement. You start investing time, putting more effort and bringing plans for a future that was never formally agreed upon.

We once had strong clinical buy-in with great pilot results and clear value, but nothing changed or moved around. It taught us that a system that improves outcomes can still fail if it questions seniority, disrupts informal processes or exposes workarounds that everyone depends on.

Alignment is the Real Challenge

In India, healthcare innovation discussions mostly focus on affordability and access. These are critical issues, but they are not the only barriers or sufficient explanations for why adoption fails. Even the most affordable, accessible and effective solution will struggle if it does not align with:

• Institutional priorities, what the hospital is actually trying to optimize for.
• Power structures, who benefits from change.
• Cultural norms, how decisions are made, communicated and delayed.
• Workflow realities, how work actually happens vs how it is documented.

Without this alignment, even the best product becomes a mere external object trying to enter a closed system.

If you do not know who the real decision-makers are, you are not selling to a hospital, you are just demoing to it. This demoing does not guarantee transformation. It requires alignment across invisible layers of authority. Without that alignment, your product will continue to remain in a permanent state of under consideration.

If there is one lesson that comes from working inside or around Indian healthcare systems is that you cannot build successful health tech by only optimizing for outcomes. You must also optimize for absorption.

What are your thoughts on it?