← All writing

Why I'm building a Clinic Management tool — and what I've learned so far

I didn't start with a grand vision. I started with a conversation with someone running a small clinic who showed me their scheduling system — a shared Google Calendar, a WhatsApp group, and a notebook. Not because they hadn't heard of software. Because nothing they'd tried actually fit.

I didn’t start with a grand vision. I started with a conversation with someone running a small clinic who showed me their scheduling system — a shared Google Calendar, a WhatsApp group, and a notebook. Not because they hadn’t heard of software. Because nothing they’d tried actually fit.

The problem with existing solutions

The clinic management software market isn’t empty. There are dozens of tools. Most of them are built for large hospital groups or multi-location chains, with pricing and complexity to match. The ones built for smaller clinics tend to be either too simple (basic appointment booking with no operational depth) or too rigid (you have to run your clinic the way the software expects, not the way you actually work).

The deeper issue: most of these tools were built by software companies who interviewed clinic owners once, built a product, and called it “healthcare software.” They weren’t built by people who understood the daily texture of running a 5-person physiotherapy practice.

The daily texture is where all the problems live.

What I’ve learned so far

Three months in, the most important thing I’ve learned is that the problems clinic operators care about are not the problems I expected.

I expected scheduling and billing to be the core pain. They are, but not in the way I thought. The real pain isn’t the absence of features — it’s the friction between systems. Appointments live in one place, patient notes in another, billing in a third. Nobody is doing the work to connect them because nobody has time, and the tools don’t talk to each other.

The second thing I learned: trust is the product, not the software. Clinic managers have been burned by tools that promised to save them time and added overhead instead. The bar isn’t “is it functional?” — it’s “will this actually make my week better, and can I trust that it won’t break when I need it most?”

What I’m building toward

Not a feature-complete platform. A daily-use tool that earns trust before it asks for commitment. Something that works on day one without a three-day onboarding.

I’m still figuring out the right scope. But I know what I’m not building: another enterprise system reskinned for a smaller audience.

That’s the lesson from the supply chain side: enterprise solutions shrunk down are still enterprise solutions. SMEs need something built from their constraints, not ours.