Like another airborne disease we are all familiar with, tuberculosis (TB) spreads invisibly through the air. If you catch it and you don’t treat it, you’re likely to die. India has the largest TB burden in the world, with millions of cases diagnosed and over 500,000 deaths every year. Consistent, continuous treatment and management of care is essential to a healthy recovery. This is why the work of Everwell Hub is so critical. Everwell Hub is a comprehensive digital solution for the management of tuberculosis. 1 in 5 newly diagnosed TB patients in the world are managed through the Everwell Hub – making it the most widely adopted solution of its kind in the world.
Andrew Cross co-founded Everwell Health Solutions and has been CEO for most of its existence. He sits down with Aid, Evolved to share what the journey to scale has been like, from the hallowed halls of Microsoft Research to the messy realities of public clinics. At Microsoft Research, he was able to work with cutting-edge tech and world-class researchers. In this environment, Andrew experimented with solutions in computer vision, augmented packaging, and cellular technology.
Then, in 2014, one of his innovations started to stretch beyond the domain of a research lab. 99DOTS, a tool for medication adherence, was seeing significant interest and uptake both by donors and government. Andrew and his small team knew that a research lab would not be the place to scale this technology. So, they set off on their own. This was how Everwell was born.
Everwell’s journey to scale arose from a unique confluence of factors: it was built on a foundation in research and evidence. Andrew’s spin-off from Microsoft was catalyzed by early buy-in from the government. And, serendipitously, Everwell’s birth coincided with a change in health policy around tuberculosis treatment which created new demand for Everwell’s solutions.
But the journey to scale is riddled with challenges. Compared to the research environment, Everwell needed to adapt to support populations at scale which revealed new and different obstacles than at a more limited scale. As one example, their initial approach using incoming calls was blocked by the telecom operators (telcos) because the system enabled patients to call for free, so they had to innovate further to accommodate millions of toll-free calls coming into their system. In today’s conversation, Andrew shares the many ways in which Everwell has needed to adapt and change in order to support the holistic, end-to-end needs of tuberculosis caregivers in India and around the world.
One key learning from his experiences: if you’re scaling innovation, you either need to find environments with the right infrastructure to accept that innovation OR you need build an organization that is able to develop the infrastructure needed to support your innovation
- Andrew developed the initial concept for 99Dots while working at the Microsoft Research Lab in India and specifically within Microsoft’s Technology for Emerging Markets team. He speaks highly of the championship and early advice this team gave him in commercializing the 99Dots digital adherence innovation.
- Bruce Thomas was a consultant for the Gates Foundation who has been a source of support and guidance for Andrew, helping him to develop his leadership skills and business acumen.
- Sriram Rajamani was Andrew’s manager at Microsoft Research. He shared many words of wisdom with Andrew over the years, including this guidance on how to think about marketing: “it’s not about self-promotion. It’s not about you. You’re doing your organization a disservice if you don’t talk about the work. If you think about it as self promotion, you’ll never be comfortable.”
- Andrew enjoys listening to Hardcore History, a long-form podcast that dives deep into major events in history.
If you enjoyed hearing from Andrew, we recommend tuning into these similar episodes:
- Evelyn Castle of eHealth Africa on balancing innovation and infrastructure for large-scale digital health programs
- Rahul Mullick of the Gates Foundation on working with government to scale digital health interventions in India
- Rikin Gandhi of Digital Green on innovating within a research laboratory and the path to commercialization
This is an automatically generated transcript from the full interview. Like humans, machines aren’t perfect, so there may be some inaccurate or amusing transcription errors.
Rowena: Let me just recount. I think there’s there’s three key assets you had right from the get go. One, you had Microsoft Research Technology in your wheelhouse. Two, you had government backing right from the start. And three, you had this change in policy which made regular shots, you know, directly observed therapy infeasible. So there was a change in health policy that really pushed towards the adoption of your system.
It sounds like,very smooth sailing. It sounds like everything just like worked right from the start. Was it just that easy in the first few years?
Andrew: No, of course not. I think I’m just I’m highlighting the fortuitous environment that also helped things scale, because I think that’s, again, for other innovators, they’re often frustrated when things don’t go somewhere. Their idea is great, but it’s still not working. So I think the lesson I’ve learned is that there’s a lot of things that contribute to the success. Of course, you know, you work 100 hours a week, you know, you have a great team, you have a great idea. But there’s also other ecosystem factors that can make or break the success of a project. You know, just talking about some of the challenges, I think specifically for this innovation, early days in a small research setting, you can ensure that everyone has a phone. You can ensure that if anything goes wrong, you can quickly reach out to them and support them. But at scale that that’s impossible. You know, that doesn’t work. And that’s the whole point of the challenge is that there’s not enough humans, health care workers to spend that kind of time on an individual basis. So one thing that didn’t work for us, for example, was the toll free lines. I mentioned this missed call system, which again no longer exists now, and we might be part of the cause for that. But, you know, when it’s a small scale project, you can get away with these missed calls.
Andrew: But obviously the telcos are losing money every time that happens. So, you know, as we started to scale up, the so many missed calls were coming on the hour, the lines that we were rented, these are virtual lines. Again, there’s no phones at offices. These are virtual numbers. So many missed calls were coming on that we actually got shut down or kind of telcos wouldn’t support it anymore. So we you know, that was a big challenge for us immediately had all these phone numbers out in the wild. People were calling and suddenly the calls aren’t going through. So we had to quickly adapt and iterate. And basically the solution was to come up with toll free phone numbers. So now these are paid for by us, not by anyone calling, but they’re they’re hosted lines that they’re paid for. So that was one challenge. Again, something that you would never have seen in a research setting, a small setting. Everything works great or can work great, but at scale you run into new challenge. And that was just one of them. So that was that was a big challenge. I mean, there’s there’s enormous challenges with phone access. For example, again, in a city like Bangalore, you might have very high phone access.
Andrew: And again, things have changed over the last ten years and phone access is increasing. But there’s always or there still is disproportionate access to phones by, you know, by gender, by geography, rural versus urban. So there’s still many people that don’t have a daily access to a phone. So that was something, again, we encountered at scale is how do we have solutions for that population or how do we reframe this technology as rather than something for everyone? This is something for people with access to phones who are comfortable calling, etc. So we had a lot of adaptations and challenges trying to make this as accessible as possible because again, you’re this is for the entire population recovering from TB. So that was another big challenge there. And maybe just last one, since I had three good factors, I can mention three challenges. I think the other one was I mentioned the initial sites where these TB HIV sites and I think you want to feel like, well, in a lot of places, TB and all these different disease verticals have been independent for a long time. And so there’s some overlap, but they don’t always aren’t fully aware of each other’s workflow. Sometimes there’s overlap, responsibilities, sometimes there’s challenges kind of courting those too.
Andrew: So that was an early learning. And just as a fun anecdote, one example was in the TB infrastructure, for example, they had a system of obviously geography. You’ve got a country, a state, a region, a district. There’s all these different ways to break down geography. But on the HIV side, they had the same system, but actually not always the same breakup. You might have a district rename something else in one system or different geographical boundaries. And of course, a lot of these things change over time. But you had disparate systems, so suddenly you have to untangle that. In some ways you’re like, you’re solving census level data or you’re understanding, you know, working with both programs say, look, we both got the same district, there’s different names. We need to think of one or else the programs can’t work together. And part of that’s our role. Part of it’s not our role, but those are some of the challenges, again, that you see at scale. And I think again, with the theme of kind of infrastructure wise, it’s almost like you’re having a step back to an infrastructure level to solve that problem before these innovations can even take hold, because you have to solve this problem of naming a district.
Rowena: Yeah, that makes total sense. Like I think when in your mind you had this 99 dots innovation, you had this thing that was going to do phone calls, you didn’t sign up with us for this with the idea that you were going to renegotiate telco revenue models or that you were going to have to deal with phone access in all these different states. But obviously, if those things aren’t there, then your innovation isn’t going to work. How did these challenges directly affect you or your team? Like what did you what did you do when you came up against those kinds of barriers? Did you expand the scope of the work that you’re doing? Did you bring in partners or like how did you evolve in the face of those challenges?
Andrew: I think for the most part, the challenges are what drove the work. I mean, it’s that’s the interesting part. Maybe that’s the engineer in me or that’s just everyone wants you want to solve interesting problems. And sometimes they’re more interesting than others. But I think that’s what made the work always interesting, is that there’s always something new. You never know what’s going to hit the next day. And I mean, there are worse things that could happen, but these are all solvable problems. So I think mostly drove our team. It was exciting. It was a reason to kind of come together and brainstorm, go back to the whiteboard and let’s rethink this from the beginning or let’s let’s find a solution to this. I think that was a lot of the excitement in the early days and maybe, you know, just kind of again, pivoting $99 was the early work. But of course, what we do now is much broader than that. I think part of the challenge, again, that we ran into at that time was that you’ve got this cool innovation, but it doesn’t connect to all these other pieces I mentioned. There’s diagnoses, there’s drug dispensation, there’s subsidies from the government. There’s all these other pieces that are part of care. And if there are digital systems that are not talking to each other, it also limits the ability to scale this up. Because as a health care worker now I’ve got to learn a new system. I’ve got this 99 point software which I use for this, and I’ve got this inventory software which I use for this, and I’ve got diagnostic software. So it is actually limiting our ability to scale because it was an extra burden, it’s an extra step. So that was one of the other challenges that we faced early on.
Andrew: And kind of the realization was, well, you know, there’s a more basic need here that could enable this innovation in others, which is, you know, core infrastructure, core digital system that integrates all these different pieces of care. Why are we thinking of it here in isolation? It’s connected to this cascade of care, as they call it, this recovery journey that someone’s going on. So we need a broader system that connects all of these pieces to really fully to fully realize the power of any particular innovation. Even today, you’ve got different innovations in diagnostics, new machines, AI, all of these things. But if they’re not connected to a core system, they’re always going to be limited to their impact because you care is holistic and they touch different pieces. So I think that was another challenge that we faced where the exciting solution was, Well, do we want to expand the technology that we built, the platform that we’ve built to cover these other aspects of care cover means and sometimes just integrate. It doesn’t mean rebuild what someone else has already done, but kind of design a common language, a common architecture that they can all speak to each other and help integrate them. So the problem you’re solving is that a health care staff can log into one system and see everything from drug supply to adherence to, again, subsidies, financial subsidies for patients, for registration of new patients. So that was that was another big pivot for us is almost taking a step back to take 20 steps forward and kind of work with the government to design this or redesign or support or kind of modernize, you could say, this digital system for how they manage the entire TB program.
Rowena: I think we’re seeing the glimmers of Everwell Hub in this picture. I want to hear all about that.
But let me also just how that I think something that’s really unique about your approach and I think speaks to the strength of how your organization has evolved, which is I think a lot of tech founders are innovators. They have one innovation and they’re attached to it. They’re stuck to it. You know, like I build this widget, I have this software. That’s the one thing that I do. And that’s what, you know, my company is built around it very much sounds like Andrew. Like you looked at the situation with TB, you were like, okay, I have this one adherence tool, this $99 thing, which is about, you know, the the blister packs and how they work. But then you realize that there was a much broader need. And instead of saying that’s somebody else’s job, you said, what do we need to do to deliver this at scale in India? And then you you did it. And that’s how the journey that that you’ve taken. And that’s I think it’s a very strategic decision. It’s a very it’s a very unusual decision. And it’s it’s very necessary in some of the environments that we work in. And it puts a lot of strain on the organization. You know, it means that maybe you started off wanting to just hire people that would manufacture your blister pack or, you know, man, your toll free call centers. But then, you know, as you started to deal with phone procurement, as you started to deal with HIV in response to the problem that you were facing, you needed to expand your services and the scope of what you were doing.
Andrew: I mean, a lot of it came down to our mission. I mean, our maybe in the early days, it was around championing a product or an innovation, but it really was always about improving the access to health care, supporting the government. Like I said, going back to the model we sort of perfected in the Microsoft research days, there is a domain expert partner who’s telling you what the real challenge is. So you can keep pushing your innovation if you want. But if you’re hearing that there’s another core challenge in your mission is to solve these challenges and improve the overall access to care, then I think decision becomes pretty easy. And so I think for us, you know, we heard loud and clear and saw ourselves that there was another limitation that wasn’t related to original problem space or is related of course, but is something it’s something entirely different. And with our mission to positively impact the TB space in India at the time, then it was pretty clear that this is where we need to need to work and that is at that time broader digital infrastructure for for the program. And I think there’s some, you know, as an innovator, you want to you can’t give up the first time. Someone doesn’t like your idea or the first time it doesn’t work. But, you know, at some point, if you’re hearing there’s a bigger challenge or you’re hearing that something’s not working, then it is your responsibility to kind of pivot or or focus.
Andrew: And for us, again, we want to solve the most interesting and most the biggest problems that technology could solve in the space. And we heard this was it. So we ended up pivoting a lot of our, you know, the other $99 work still lived on. But we pivoted a lot of our attention and time to this more core infrastructure work because we saw a bigger opportunity for impact. And I think, you know, there’s other lessons learned along the way around how, again, a particular innovation, 99 dots at that time had a lot of positive impact around ability to change the drugs and kind of empowerment. But then at some point there’s populations that doesn’t work for us. You need to be willing and able to say, well, it’s not appropriate for that environment, so let’s not push that innovation there. In fact, they need something far different that maybe what someone needs is actually financial subsidies so they can afford food, so that the medication can have its proper effect. And so I think there’s a bit of yeah, I think getting at is you want to kind of stick to your guns in some ways because you can’t again give up the first time you hear. No, but you also need to be flexible enough to recognize when the environment is changing and where you can be most useful if that’s your goal.