Skip to content
Adjacent — we have the machinery

The clinic half of a business we already run.

An optical practice is a clinic. Patients, appointments, a practitioner, a recorded examination, a recall when it is due, and a fee that has to reach the accounts correctly.

We run a patient-facing clinical workflow in production every day — but inside optical practices, where the examination is an eye test. Appointments, patient records, clinical history, recalls and billable professional services are live software, not a proposal. What we do not have is anything general-medical: no diagnosis coding, no medications or allergies, no vitals, and practitioners are staff users rather than credentialed clinicians. For a dental or diagnostic practice that is real build work, not configuration.

Sound familiar?

A week in this business.

If three or more of these are true, the problem is usually not the tools. It is that none of them talk to each other.

  • The appointment book is paper, or a shared calendar nobody trusts
  • No-shows are noticed, but never counted
  • Patients who are due a recall are the ones you never call
  • The clinical record and the invoice have no connection to each other
  • Consultation fees get discounted at the counter and nobody sees the pattern

What we’d build

The parts that matter here.

Appointment diary per branch, with type, duration, practitioner and status
Arrived, completed, no-show and cancelled tracked as real states, not notes
Patient records with contact, account and visit history
Clinical measurements captured per visit, with full history and trend over time
Recalls that close against the appointment that answers them
Billable professional services with fees, tax profile and a revenue account
Rules for when a fee is mandatory, waived, or needs approval to discount
Documents stored against the practice, encrypted at rest

Which route

Configure something proven, or build it?

Most vendors answer this the way that suits them. Here is how it usually goes in this sector — and we will tell you plainly which side you are on.

Open-source ERP

Usually faster and cheaper

Rarely a good fit. Clinical scheduling and records are not what a generic ERP is shaped for, and the appointments module is thin.

How we do this

Custom build

When the standard parts run out

The usual answer. We would start from the scheduling, patient and billing machinery that already runs, and build the clinical layer your discipline actually needs.

How we do this

Questions

Do you have experience outside optical?
Not in delivery. The clinical workflow we operate is real and running, but every patient on it is an optical patient. We would be learning your discipline while building — which is fine if we both plan for it and are honest about the timeline.
Can it hold full medical records?
No. There is no diagnosis coding, no prescribing, no allergies or vitals. It holds structured measurements per visit with history. If you need a full electronic health record, that is a larger build and a different conversation about regulation.

Other sectors

Tell us what isn’t working.

Thirty minutes, no deck. We’ll tell you what we would do — and say so plainly if software isn’t the answer.

Book a call

Talk to us

Book a call