Written by: Snider Mugese, Villgro Africa’s Director of Finance and Operations

Villgro Africa recently participated in the International Maternal and Newborn Health Conference (IMNHC) knowledge café, and one uncomfortable truth kept resurfacing:

Most health innovations don’t fail because they’re bad.
They fail because they’re built in isolation.

And in healthcare, isolation is expensive.

Because while we debate innovation pipelines, the reality is this:

  • Sub-Saharan Africa accounts for ~70% of global maternal deaths
  • Nearly 1 million newborns die every year in the region, largely from preventable causes
  • Over 50% of health innovations in low- and middle-income countries never scale beyond pilot stage

We don’t have an innovation problem.
We have an adoption and scale problem.

The myth of the “brilliant solo innovator”

Let’s get this out of the way:

If you’re building health tech like a Silicon Valley app, you’re already in trouble.

Healthcare is not:

  • One user
  • One buyer
  • One decision-maker

It’s a messy, interdependent system of: Patients. Nurses. Doctors. Regulators. Procurement. Biomedical engineers. Governments.

And here’s the catch: each of them has veto power.

Bundling is survival

One of the sharpest insights from the room:

Single solutions don’t solve system problems.

Yet most innovators are still building like this:

  • One device
  • One app
  • One feature

Meanwhile, the health system is dealing with:

  • Workforce shortages
  • Fragmented data systems
  • Supply chain gaps
  • Financing constraints

So your elegant solution? It becomes just another layer of complexity.

What actually works is bundling:

  • Devices + data + care pathways
  • Maternal and newborn care packaged as an integrated service
  • Solutions designed to work together, not compete

Because here’s the reality:
Health systems don’t buy products. They adopt solutions that reduce friction.

Collaboration is the unfair advantage

A clear pattern from models like Health Tech Hub Africa and Villgro Africa:

Not just acceleration, orchestrated collaboration.

What actually moved the needle:

  • Peer-to-peer learning grounded in reality
  • Strategic partnerships
  • Regional thinking from day one, not “we’ll expand later”

And here’s the uncomfortable truth:

The winners weren’t the smartest in the room.
They were the most connected to the system they were trying to serve.

Where good ideas go to die

Two groups mapped the innovation journey. Different frameworks, same graveyard.

The breaking point: Deployment. Scaling. Real-world use.

Not ideation. Not prototyping.
The moment you leave your controlled environment, things fall apart.

Why?

  • You didn’t design for different contexts
  • Your cost structure collapses outside donor-funded pilots
  • Your “user” was never actually the user

And here’s the data behind it:

  • Less than 1 in 3 digital health solutions in LMICs achieve sustained integration into national systems
  • Many innovations fail at the “last mile” not because of technology, but because of workflow, training, and financing gaps

The real problem: you’re building for the wrong person

One brutal insight:

The person using your product is often not the one choosing or paying for it.

And yet, most products are built like:

  • The midwife is an afterthought
  • The workflow is ignored
  • Integration is “phase two”

There is no phase two.

If your solution adds even 5 extra minutes to a frontline worker’s workflow in an already stretched system, it won’t be used.

Not because it’s bad.
Because it’s impractical.

The adoption gap no one budgets for

Everyone loves prototyping.
No one budgets for behavior change.

And that’s where things fall apart.

What actually kills scale:

  • Low user understanding and training gaps
  • Poor integration into workflows
  • Pricing misaligned with local health system economics
  • Weak distribution and market access strategies

And the big one:

Manufacturing cost ≠ market reality

A device that costs $50 to produce but targets a system that can only pay $10 is not innovative.

So what actually works?

Not glamorous. But effective.

  1. Co-create like your life depends on it

Because your product’s life does.

  • Engage frontline workers early (midwives, nurses, CHWs)
  • Involve regulators before you need approval
  • Design with the system, not for it
  1. Build for integration, not disruption

If it doesn’t plug into existing systems (clinical workflows, health information systems), it’s dead on arrival.

  1. Think in bundles, not features

Solve the full problem, not your favorite slice of it.

  1. Design for sustainability from day one
  • Price realistically
  • Reduce dependency on continuous grant funding
  • Align with existing financing mechanisms (public, insurance, out-of-pocket realities)
  1. Collaborate strategically

Not “let’s partner” energy. Real alignment:

  • Shared regulatory pathways
  • Shared distribution channels
  • Shared market entry strategies

The uncomfortable conclusion

Most health innovations don’t fail because founders aren’t smart.

They fail because:

  • They underestimate the system
  • Overestimate the product
  • And try to scale alone

If you’re still building solo in healthcare, you’re not scrappy, you’re inefficient.

Africa doesn’t need more pilots.

It needs:

  • Fewer, better-integrated solutions
  • Stronger collaboration across the ecosystem
  • Innovations designed for real-world adoption, not controlled environments

But let’s also be honest about something we don’t say enough:

Even the right solution, at the right time, solving a real need… can still struggle.

Capital doesn’t always flow where logic says it should. Adoption isn’t guaranteed just because the problem is obvious.

  • Health systems are constrained.
  • Procurement cycles are slow.
  • Budgets are tight.
  • Decision-making is fragmented.

So even when you get the product right, you still have to fight for alignment.

Alignment with:

  • Policy priorities
  • Funding flows
  • Institutional incentives
  • And the people actually delivering care

And that’s the real work.

Because building the product is only half the job.
Getting it adopted; that’s the system navigation game.