I started building Medly almost a year ago now, although the truth is that the idea has been forming for much longer than that.
Like most things worth building, it did not start with a polished business plan or some neat founder story. It started with frustration. Frustration at how hard it can be for ordinary Australians to access timely care. Frustration at how often healthcare feels slow, expensive, fragmented, and far more complicated than it should be. Frustration at how digital health, despite all its promise, too often reproduces the same problems in a shinier format.
Medly is my answer to that.
It has become the place where almost everything I have learned across medicine, business, public health, law, education, and software has converged into one system. Not just a website. Not just an app. A full digital health organisation built from the ground up around a fairly simple idea, which is that healthcare should be more accessible, more affordable, safer to navigate, and easier for both patients and clinicians to use.
That sounds obvious, but in practice, it isn’t.
Over the past year I have spent an extraordinary amount of time building the parts that most people will never see. Clinical logic. Governance structures. workflows. Patient pathways. Doctor-facing systems. Safety layers. Documentation. Policies. Content. Technical architecture. The operational scaffolding that allows a healthcare service to function properly, not just look polished on the surface.
That has been one of the hardest parts of this journey. People often see the final interface and assume the product is the work. It is not. In healthcare, the real work is often everything underneath it. It is thinking through what happens when something goes wrong, what should happen before a doctor even joins a consult, what information should already be available, how a patient should be guided, where risk should be identified, and how to reduce friction without compromising standards.
That is the kind of system I wanted to build.
I did not want to create another digital front door that is fast but clinically thin – there are too many script mills and tick and ‘n’ flick clinics… I didn’t want convenience without structure. I did not want a model that made life easier for the platform by making things harder for patients or clinicians. I wanted to build something that respected both sides of the consultation.
So Medly has been built around a different philosophy. Patients should be able to access care without unnecessary complexity. Doctors should not be walking into a consult cold when a safer and more efficient workflow can brief them properly first (just like a registrar/resident presenting to the consultant). The system should be simple on the surface, but rigorous underneath it. If digital health is going to mature in Australia, I think that is where it needs to go.
The sacrifices involved in getting to this point have been real.
Building a healthcare company as a one-man band is not glamorous. It means long days, late nights, weekends disappearing, and constantly shifting between roles that would normally sit across an entire team. Founder, clinician, strategist, operator, product lead, policy writer, reviewer, tester, content creator, problem-solver. Some days it feels energising. Other days it feels completely irrational.
There have been very good moments. Those small points where a workflow finally clicks into place, when a system starts behaving the way you pictured it months earlier, when other clinicians understand the model immediately, or when the whole thing starts to feel less like an idea and more like an actual organisation.
There have also been difficult moments. Bootstrapping forces clarity, but it also forces trade-offs. Time becomes brutally expensive. Every decision matters. Every month of development has a cost. Every new feature competes against runway, energy, and the practical realities of life. There is no giant buffer. No large team absorbing the pressure. No comfortable distance between the vision and the responsibility of making it real.
That said, I do not think this kind of pressure is always a disadvantage.
It forces you to work out what actually matters. It strips away a lot of noise. It makes you build carefully. It makes you think harder about sustainability, governance, and what patients genuinely need rather than what sounds exciting in a pitch deck. Medly has not been built for hype. It has been built to function in the real world.
And the real world is exactly why I think this is important.
Australia is at an inflection point in healthcare. People are feeling cost pressure everywhere. Access pressure everywhere. Time pressure everywhere. When care becomes too slow, too hard to navigate, or too expensive, patients do not stop needing help. They delay care. They put up with symptoms longer than they should. They ration appointments. They turn to the wrong channel because the right one feels out of reach.
That is more than just a health problem, it is a social problem, an economic problem – a crisis.
Affordable, well-structured digital care will not solve everything, and it should not pretend to. But it can reduce friction in a meaningful way for the right types of care. It can make it easier for patients to ask for help earlier. It can make clinicians more efficient without turning the consult into a conveyor belt. It can create a model that is both more humane and more operationally sensible.
That is the lane Medly is trying to occupy.
If you look through the Medly telehealth service, what you will see is not just another generic health platform. You will see the early version of a care model I think should become far more common, one that takes clinical governance seriously, one that values patient and clinician safety, and one that is trying to keep healthcare affordable without reducing it to a commodity.
There is also a broader mission underneath it. I want Medly to contribute to a version of digital health in Australia that is more thoughtful, more accountable, and more patient-centred than much of what currently exists. That means asking harder questions about what should be automated and what should not, where structure improves care, how affordability can be preserved, and how digital health can be built in a way that earns trust rather than just assumes it.
That trust matters to me a lot.
Medly is not a side project. It is not a quick experiment. It is the product of years of experience across multiple disciplines, and one intense year of building with very little distance between the idea and the execution. It reflects what I have seen in hospitals, in leadership, in education, in policy, and in the real practical failures that occur when systems are designed around convenience, cost shifting, or speed alone.
Launching now does not mean the work is finished. It means the real work begins.
Medly is now at the point where a private effort becomes public. Where a system starts meeting real patients, real clinicians, real operational pressure, and real feedback. That is where the next stage of Medly starts. Improving it. Stress testing it. Expanding it carefully. Keeping what works. Fixing what does not. Staying honest about where digital health helps and where it still falls short.
I am proud of what has been built so far. I am also very aware of how much more there is to do. Like any bootstrapped startup, it can be rough around the edges. There are aspects to improve for patients, doctors and operational staff.
But after almost a year of building, refining, second-guessing, sacrificing, learning, and pushing forward, Medly is launching. At last.
If you want to see what I have been building, you can visit Medly or explore the Help Centre to understand more about the model behind it. Or reach out to me directly.
I built Medly because I think Australians deserve a healthcare experience that feels simpler, safer, and more accessible than what too many are currently left with.
Now it is finally ready to begin.