Practice management software · United Kingdom
Software your practice stands on.
The diary, the client records, the classes, the rooms and the money — one system for the whole of a practice day. What a client record holds and what an appointment asks are yours to decide, from a settings screen, without waiting for anybody to write code.
Plinth is in development and not open to practices yet. There is no sign-up, no trial and no price list. The waitlist is how you hear when there is one.
Product
One system for the whole of a practice day
Reception, therapists, managers and patients all working from the same diary — each seeing exactly as much of it as their job needs.
-
The diary
A day or a week, every clinician or one. A room and a clinician are held by the database itself when a booking is made, so the same slot cannot be given away twice from two screens at once.
-
Classes and groups
Rehab courses, antenatal groups, staff briefings. Setting one to run every week is a single screen, and booking somebody onto a block asks whether they mean this week, all of them, or the next few.
-
The patient's own view
Their appointments, their classes, their details, their receipts. Self-booking stays off until a practice turns it on — one appointment type at a time, never all at once.
-
Messages
Confirmations, reminders and cancellations in the practice's own words. A reminder is queued in the same breath as the booking that needs it, so a booking cannot quietly exist without one.
-
Payments
Take a card for an appointment or for a block of six classes, at the desk or from the patient's own phone. A block of classes is one payment, because that is what was bought.
Your questions
Your questions, not ours
Every practice asks something the last one did not. A physiotherapist wants the mechanism of injury. A counselling service wants the referral route and who else is involved. An osteopath wants three lines about the pregnancy. Plinth has no opinion about any of it, and no list of fields you have to work around.
- Question
- Presenting complaint
- Type
- Long text, at most 2,000 characters
- Asked on
- First assessment, Follow-up — not on Sports massage
- Required from
- 1 April 2026
- Held as
- Health data, special category
- The patient
- Can see it, and can fill it in before they arrive
- It is a real field, not a notes box. Twelve kinds — text, numbers, dates, email, phone, a list to choose from, a list to choose several from — each with its own label, help text and rules about what counts as an answer. Stored typed and indexed, so you can count it, filter by it and report on it later. That is the whole difference between recording something and being able to ask a question about it afterwards.
- Different appointments ask different things. A question belongs to the appointment type that asks it, set up on that type's own screen beside its length and its price. A first assessment can insist on a full history; a half-hour sports massage asks nothing, and nobody is made to answer a clinical question to book one.
- A form you send out is the same questions. Mark a question as one the patient can see and fill in, and it appears on their own portal before they arrive. An intake form is not a separate thing to build and keep in step — it is your questions, with a tick in a box.
- Making something required does not break what you already have. A new required question applies from the day you add it. Records made afterwards must answer it; older ones are left alone until somebody fills it in. Without that, ticking one box would stop reception changing a phone number on two thousand records until every one of them had been revisited — so people learn not to tick the box, and the field never gets used.
- Say what a question holds and the system takes it seriously. Mark one as health data and it is redacted from audit trails, left out of analytics extracts, and refused outright in a message template — because a template is read by whoever receives the mail, and a diagnosis has no business being merged into one.
- Stop asking something without losing the answers. Retire a question and it stops appearing on new records while every answer already given stays readable. The same goes for one option in a list: last year's referral sources still make sense on last year's records.
Rooms
Rooms are not an afterthought here
Most practice software treats a room as a label on an appointment. A real building is not like that — it is let out, shared, and argued over.
- Let a room to an outside hirer. A hirer gets their own sign-in, sees which rooms are free, books one and pays for it. They see nothing of your clients, your diary, your staff or your takings — and that is enforced by the database rather than by leaving a link off a menu.
- Share a room with the practice down the corridor. Two practices in one building can book the same room without either being able to read the other's diary. Free and busy crosses the boundary; nothing else does.
- An unpaid hold lets go. A self-service booking is provisional until it is paid for, so nobody sits on a Tuesday evening they never intend to use.
- A room has an address, not just a name. Which floor, which door, and what goes in the confirmation email — because "Room 2" helps nobody who has not been before.
Data protection
Separation is built in, not promised
Every client record is treated as special-category health data under UK GDPR, which is what it is. That assumption is wired into the database rather than written into a policy document.
- One practice cannot reach another's data. Row-level security on every table, applied to every query by the database itself — not a condition somebody has to remember to add.
- A therapist sees their own caseload. Enforced in the same place and by the same mechanism, so it holds whichever screen or report is doing the asking.
- Reads are audited as well as writes. Who opened a record is as fair a question as who changed one, and the answer is written in the same transaction as the thing it describes.
- Clinical detail never reaches a log. Fields marked special-category are redacted from audit trails, left out of analytics extracts, and refused outright in a message template — a template is read by whoever receives the mail.
- Stored and processed in London. AWS's eu-west-2 region, with a per-practice retention setting that actually deletes rather than hides.
Accessibility
Accessible because it has to be
Plinth is built to WCAG 2.2 AA and EN 301 549 — the standard a UK public body is held to, and the one a private clinic is measured against when somebody cannot use the booking page. Every control has a real label, colour never carries meaning on its own, and the diary still lines up when text is resized to 200%.
That is a condition of every change rather than an audit booked for later. This page is built the same way, and makes no third-party request at all: no analytics, no tracking pixel, no font CDN. The typefaces are served from this domain.
Money
The money is yours before it is anybody else's
A card payment is made on your practice's own Stripe account and settles to your practice's own bank. Plinth never takes custody of it, never holds a balance on your behalf, and never sees a card number — the card is entered on Stripe's own page, not on ours.
Which is why there is no "payouts" screen: there is nothing sitting anywhere waiting to be paid out to you.
Why "Plinth"
A plinth is the block a thing stands on. It is not the part you look at, it carries the weight of the part you do, and you notice it only when it is not there. That is the job.
Waitlist
Tell us you want it
We are not onboarding practices yet. Leave an address and you will hear when that changes — and, if you tell us what you need, when the thing you asked for is built.
We store what you type here and nothing else — no analytics, no tracking, no sharing it with anybody. Ask and we will delete it. The privacy notice says so at greater length.