PraxisOS
An AI team for your practice. Not one of them acts without asking.
The practice runs on the two busiest people in it
You're a specialist clinician, and you're also the person the business lands on. Systems, suppliers, staffing, compliance, and the notes you did not finish, all squeezed into one admin day, or the weekend. The most expensive hour in the building is spent on the lowest-leverage work in it.
Reception is the busiest seat you have. New-patient calls, rebooking, chasing, typing details in by hand, all while somebody is standing at the desk waiting. Calls get missed at exactly the times new patients ring.
None of this is a people problem. It’s that the work has nowhere else to go, so it goes to whoever is nearest, at the worst possible moment.
The AI prepares.
Your team approves.
Not one assistant trying to do everything. A team of specialists, each good at one job, taken on one at a time. Every one of them works the same way.
It does the work: a call answered, a recall chased, a note drafted.
It prepares exactly what it wants to change.
Nothing is saved. Nothing is sent.
Your team approves, and then it happens.
The one that gives you your evenings back
You talk to the patient as you always do. It listens, drafts the note and the treatment plan while you work, and hands them to you. You edit and you sign.
- A note, not a transcript
Presenting complaint, examination findings, diagnosis, treatment provided, plan. Structured the way you would have written it.
- The plan as well
Treatment options and an estimate drafted from what you actually discussed, ready for you to price and send.
- You are the author
Nothing reaches a clinical record without a clinician's signature. There is no version of this that files itself.
And the one that answers the phone
Nothing is saved until a person approves it. The AI never writes to your practice software itself, and an emergency goes straight to a human, not to the AI.
What your team actually sees
Nobody turns up for an appointment you never made
The real risk with a phone AI isn't a clumsy sentence. It's a patient arriving on Tuesday certain they were booked, and your receptionist having to tell them they weren't.
“I’ve passed that to a colleague to confirm. You’ll hear from us.”
- “You're booked in for Tuesday.”
- “Your reference number is 1237.”
It can only speak a date or time your own diary handed it, so it has nothing to invent from. And it never learns whether you approved the booking. That happens after the call ends, so it cannot claim you did.
Your AI team, taken on one at a time
You don't take them all on at once. Each one arrives the same controlled way: prepare, approve, record. Nothing new ever turns up ungoverned.
1 · Notes & treatment plans
You talk, it drafts the note and the plan, you edit and sign. Never written without a clinician's signature.
2 · AI Front Desk
Answers the phone, takes new patients, offers real appointments, prepares the record for approval.
3 · Recalls & reactivation
Chases overdue check-ups and brings lapsed patients back: revenue already on your books.
4 · Practice insight
What's actually happening in your practice: missed calls, no-shows, where money leaks, and what you are about to run out of.
Module 1 is the one most principals want first, and it is the slide you have already seen. Because it touches the clinical record, real clinical use waits behind a proper clinical-safety case and medical-device registration.
Meet the rest of the team
All of them in the console your team already has, not four more systems to log into. Three of them here. Pick one to see it.
Overdue patients found, a message drafted for each, and nothing sent until someone approves it.
Chair time, failed appointments and how much of your intake actually converts, with a morning briefing that names the few things worth your attention today.
What you hold, what you are about to run out of, and the reorder drafted for someone to approve before it is placed.
Recalls and practice insight are designed previews of work not yet built. Shown so you can see where this goes, not to suggest they are ready. The front desk, on the earlier screens, is the one that runs today.
Your practice software stays the home of your records
We don’t take a copy of your patient database. We work beside it, holding only what we need to do the work and prove it was done properly.
Tasks, approvals and the audit trail. A patient’s details only briefly, and encrypted, in the window between draft and approval.
Your own database and your own logins, in a UK datacentre. Nothing about your patients is pooled or compared with any other practice.
Nothing. No server, no hardware, nothing installed. A website and a phone. It sits in the dock as an app if you’d rather.
What works today, and what doesn't yet
We'd rather show you a narrow thing that genuinely works than a broad demo that only holds up while we're driving it.
- A call answered and understood
- The caller identified, and the name spelled back
- A record prepared and held for your approval
- A clinical note drafted from a consultation, structured, with every line traceable to something that was said
- Every decision permanently logged
- Real patients: the data-protection assessment
- The link into your software: developer access to it
Both are long poles, and we'd start them with you in week one. Neither will be a surprise later. Using the scribe on real patients has its own gate, which is the clinical-safety work on the earlier slide.
Let us come and see how you work.
- A couple of hours at the practice, watching how the front desk actually runs, where the time goes, and what software you're on.
- Then a demo, shaped around what we saw: a real call on test patients, with you watching the record arrive for approval.
- If it fits, we scope a pilot: one workflow, your practice, and no commitment before that.
PraxisOSIntroductionTest patients → shadow → controlled go-live