Custom practice software, built around how your practice works

If your practice software feels rigid, or built for a kind of practice that is not quite yours, you have probably assumed custom software is only for hospital groups. It is not. Between 2024 and 2025 I built a practice platform for healthcare professionals, with a focus on dental and orthodontic practices. Here is what that actually involved.

Why Practices Outgrow Off-the-Shelf Software

South Africa's medical practice management market is dominated by a few players: Healthbridge, Solumed, GoodX, and a handful of others. They serve thousands of practices with standardized software.

The problem is standardization.

Your workflow is not standard. A physiotherapy practice operates differently from a dental practice. A multi-practitioner medical practice operates differently from a solo-GP practice. A medical aesthetics clinic operates differently from all of them. Off-the-shelf software picks one workflow and forces everyone into it.

Your billing is complex. Medical aid billing in South Africa has specific requirements: ICD-10 codes, NAPPI codes, tariff management, medical aid scheme rules, gap payments, patient co-payments, cash patients, accounts receivable management. The off-the-shelf system handles the common scenarios. Your practice has uncommon scenarios.

Your integration needs are specific. You want your practice management system to connect to your booking system, your website, your accounting software, your stock management, and maybe your patient communication platform. The off-the-shelf system integrates with its own ecosystem and nothing else.

Per-user pricing adds up as your practice grows. As you add practitioners and admin staff, monthly per-user fees for software that does not quite fit keep climbing. At some point, the ongoing cost of not-quite-right software exceeds the cost of building something right.

What I Built, in Plain Words

The platform runs the whole patient journey in one place: patient records with medical history and consent controls, multi-scheme medical aid support with benefit tracking, bookings across several practitioners with patient self-booking, billing from quote to invoice with medical aid claims, clinical notes, 32-tooth dental charting and orthodontic treatment tracking with before-and-after photos. Behind it sits an API with more than 300 endpoints.

What a Practice Actually Needs First

Not every practice needs every module. Start with the piece that hurts most. For most practices, that means: patient records, bookings, billing and medical aid claims, and clinical notes. Everything else is a later phase.

POPIA and Compliance

Medical practice software in South Africa must comply with POPIA. This is not optional and it is not a checkbox exercise.

What this means in practice:

• Patient consent must be recorded before processing personal information
• Access controls must limit who can see what (a receptionist does not need access to clinical notes)
• Data must be stored securely with appropriate encryption
• Patients have the right to request their data and to request deletion (with medical record retention exceptions)
• Breach notification procedures must be in place
• The practice must appoint an Information Officer

A custom system can be built with POPIA compliance designed into the architecture. An off-the-shelf system may or may not meet your specific compliance requirements.

How It Starts

I quote privately once I understand your workflow and integrations. It starts with the written plan (a fixed fee, agreed in writing), then a fixed price for the first piece. You pay per piece of work, and you're never committed to more than one piece. See how I work.

The Build-vs-Buy Decision

Custom makes sense when:

• Your practice workflow is genuinely different from what off-the-shelf software supports
• You are a multi-practice group where the cost savings at scale justify the investment
• You need integrations that the off-the-shelf vendors do not support
• Per-user licensing costs at your scale make custom development cost-competitive
• You want to own your data and your system, not rent it

Off-the-shelf makes sense when:

• Your practice is small and your workflows are standard
• You do not have the budget for custom development
• You need to be operational quickly (custom takes months, off-the-shelf takes days)
• The off-the-shelf system genuinely fits your needs without significant workarounds. If an off-the-shelf system fits your practice, use it.