For the past year, I have been building Medly.
In truth, I have been building toward it for much longer than that. Medly is not the result of one idea on one afternoon. It is the product of years spent moving through medicine, public health, business, education, law, and software, and gradually realising that many of the same problems keep showing up in slightly different forms. Access is harder than it should be. Care is often more expensive than people can comfortably manage. Systems are fragmented. Patients are expected to navigate too much on their own. Clinicians are often forced to work around poor design rather than being supported by good systems.
Medly came from that frustration, but also from a belief that the system can be better built.
I started working on Medly because I could see a gap between what digital health often promises and what patients actually experience. Too often, healthcare is described as accessible simply because it can be reached through a phone or a laptop. That is only part of the story. Access also means affordability. It means clarity. It means knowing where to go, what is appropriate, what is not, and being able to obtain care without being buried in friction, confusion, or cost before you have even started.
That is where the idea of affordable telehealth in Australia started to matter more and more to me. Not as a slogan, but as a practical problem worth solving properly.
Over the last year, I have built Medly largely as a one-man band, which sounds romantic until you actually live it. It means wearing every hat at once. Founder, clinician, strategist, policy writer, systems architect, content creator, tester, reviewer, problem-solver, and the person who still has to make the final call when something breaks. It means long nights, lost weekends, constant context switching, and a running mental list of ten things that all matter and all compete for attention.
Some parts of that journey have been deeply rewarding.
There are moments in any build where scattered pieces begin to lock together and you can finally see the thing becoming real. A workflow starts doing what it was supposed to do months ago. A clinical pathway begins to feel coherent. A system that once existed only in your head becomes something another person can actually use. Those moments matter because they are the rare points where effort becomes visible.
Other parts have been brutal.
There is a particular kind of fatigue that comes from trying to build something ambitious without a large team behind you, especially in healthcare, where the stakes are higher and the details actually matter. It would have been much easier to build something lighter, thinner, faster to launch, and easier to market. Plenty of people do exactly that. But I did not want to build another front-end that looked smooth while the underlying model remained clinically shallow. I wanted Medly to be built around governance, structure, boundaries, and the reality that a healthcare service should do more than process transactions.
That choice has made the journey slower, heavier, and more expensive in time and energy. I still think it was the right choice.
One of the things I have learned in building Medly is that the public usually sees the least difficult part of the work. They see a homepage, a price, a booking flow, a polished screen, a few clean words. They do not see the months spent thinking through the things that sit underneath it all. What should happen before a consult even begins. What information should already be gathered. How risk should be recognised early. How a doctor should enter a consultation better briefed. How a service should draw boundaries around what telehealth is and is not suitable for. How a platform can try to reduce friction without reducing care to something careless.
That hidden layer is where most of the work has been.
I have poured an enormous amount into designing a service that does not just look simple on the surface, but is actually structured underneath. For me, that is the difference between building a website and building a health service. One is interface. The other is responsibility.
There is also a social side to Medly that matters to me just as much as the operational side.
I do not believe affordability in healthcare is a side issue. I think it is one of the central issues. When the cost of seeing a doctor keeps climbing, people do not stop needing care. They wait. They put symptoms off. They convince themselves it can probably wait a bit longer. They hope it settles. They try to work around it. They seek help later than they otherwise would have. That pattern has consequences, and not all of them are visible immediately.
That is part of why affordable telehealth in Australia matters so much to me. Used properly, telehealth can reduce some of that friction. It can make care easier to reach for the right problems, at the right time, in the right way. It does not solve every access issue and it should not pretend to. But it can still remove enough barriers to make a real difference.
Medly has been built around that premise: that digital care can be simpler without being careless, and that affordability should not have to mean a stripped-back or poorly governed experience.
I have also wanted Medly to reflect a different philosophy about technology in healthcare. I am not interested in adding complexity for the sake of sounding innovative. I am interested in building systems that are useful, accountable, and clinically sensible. Technology should support care, not perform theatre around it. It should help patients navigate the system more clearly and help clinicians spend more of their time on judgment rather than admin. That is the standard I have been trying to build toward.
The good times in this journey have come from seeing that vision start to take shape. The bad times have mostly come from the distance between vision and capacity, which is where most founders live for longer than they admit. There have been delays, trade-offs, setbacks, second-guessing, and periods where the mountain looked much bigger from up close than it did from far away. There have also been moments of real encouragement, particularly when other people immediately understand what Medly is trying to do and why that model matters.
That matters to me because Medly was never meant to be noise.
It was meant to be a serious attempt to build something better, something more considered, something that respects both the patient trying to get care and the clinician trying to provide it.
Now, after a long build, Medly is reaching the point where it can step out of planning and into the real world. That part is exciting, but it is also sobering. Launching is not the finish line. It is the point where the real test begins. Real patients. Real operational pressure. Real feedback. Real accountability. That is how it should be.
I am proud of what Medly has become so far, but more than that, I am clear about what I want it to contribute to. I want it to be part of a broader shift toward more affordable telehealth in Australia, built with thoughtfulness, clinical structure, and a real understanding of what patients are actually facing.
Medly is my attempt to build that kind of service. Not a shortcut. Not a gimmick. Not a shiny layer over the same old problems.
A real healthcare service, built carefully, with patients at the centre of it.