Why we built Orla

Ask a physiotherapist where their practice loses money and they will talk about the treatment room: the hour that went long, the patient who needed more than they were charged for. Sit at the front desk for a morning and you see something else entirely. The room is fine. The losses happen in the ten minutes between treatments, and they happen quietly.

Do this arithmetic with your own numbers

We are not going to quote you an industry average, because we are pre-launch and do not have one, and a benchmark invented for a marketing page is worth less than nothing. But you have the figures already:

Take your fee for a standard appointment. Multiply by the number of cancellations last month that nobody managed to refill. That is the first number.

Now take the patients on a care plan with sessions left who have nothing booked. Multiply by the same fee. That is the second, and at most clinics it is the larger of the two — a course of treatment that stopped halfway is revenue that was already agreed and simply never collected.

Neither of those is a pricing problem or a marketing problem. Both are somebody-did-not-have-ten-minutes problems.

Why practice software tends not to help

Most practice management systems are a diary with a database bolted on. They are very good at recording what happened: this patient came, this was charged, this note was written. Recording is genuinely hard and they solved it.

But a system that records the day cannot run the day. When a cancellation comes in at 11:42, a recording system faithfully marks the slot empty and then waits — for a human to notice, open the waitlist, and start ringing. It has done its job perfectly and the hour is still lost.

The difference is not intelligence. It is whether anything in the system is obliged to act when a fact changes. When the 14:15 cancels in Orla, the slot does not sit there waiting to be noticed: everybody on the waitlist who matches it is texted at once, and the first to tap gets it. The desk finds out it happened because the diary shows the slot filled.

That is the whole thesis. A clinic operating system, not a clinic filing cabinet.

What "EU hosted" is actually worth to an Irish clinic

This phrase appears on a lot of vendor pages and usually means "our servers are in Frankfurt". Here is what it is worth in plain terms.

Patient records are special category data under GDPR. If they sit with a processor outside the EU, the clinic — not the vendor, the clinic — is the controller who has to justify the transfer, and who fields the questions if anyone asks. Keeping the data in the EU removes an entire category of paperwork and risk from the practice owner's desk.

But hosting location is the easy half. The harder questions are the ones a clinic only discovers it needs answered when something goes wrong:

• Can you show who looked at a record, not just who changed it? Orla journals reads, and the journal is append-only at the database level — the application role has had UPDATE and DELETE on it revoked, so nobody, including us, can quietly tidy the history.
• Is one clinic's data separated from another's by something stronger than a WHERE clause somebody remembered to write? In Orla the separation is a database policy applied underneath every query, attached to every table that carries a clinic identifier, derived from the catalogue rather than a hand-kept list — so a new table cannot ship unprotected by being forgotten.
• Can you leave? Everything exports. That is one of eleven questions worth asking any vendor, ours included. There is no exit fee and no retention trick, because a product that has to trap you to keep you has told you what it thinks of itself.

Built in Ireland, for how Irish clinics actually bill

Small things that only matter if you work here. Dates read day-first, because a date format that flips between screens is a clinical risk, not a style preference. Receipts carry the practitioner who treated the patient and their CORU registration number, because without those a patient cannot claim on VHI, Laya or Irish Life and will be back at the desk asking for "a proper receipt".

Those are not features anyone puts on a homepage. They are the difference between software written for a market and software translated into it.

Where we actually are

Orla is pre-launch and recruiting founding pilot clinics. The diary, the patient record, online booking, the waitlist engine, reminders, invoicing and reporting are built and running. The AI layers are honestly next phase, and we would rather tell you that than show you a demo of something that does not exist.

If you run a clinic and any of the arithmetic above landed uncomfortably close to home, that is the conversation we want to have.