Included in Custom / Enterprise
Custom & multi-location
Several locations, and a system that already exists
Quoted against scopeSet during scoping
The leak
The distance between a single-location booking build and a group that needs one view across sites.
Multi-location rollouts and PMS, EHR or POS integrations, scoped against your actual systems rather than sold as a package.
Where this sits
This module is part of Custom / Enterprise. It is not sold on its own, because the handoff between it and the module beside it is where revenue actually escapes.
What gets built
The deliverable, stated the way the contract states it
An individually scoped engagement. We map your existing systems, define the integration surface, and quote against that — instead of quoting a tier and discovering the constraints later.
At a glance
- Itemised value
- Quoted against scope
- Build window
- Set during scoping
- Sold inside
- Custom / Enterprise
Yours at handover — domain, accounts, data and source code.
How it works
The mechanism, not the marketing
Trigger on the left, the rule the system applies in the middle, the consequence on the right. Read it as the logic your practice would otherwise be running in someone's head.
scoping · integration surfaceIllustrative interface
| Your existing system | What we establish | Answer you get |
|---|---|---|
| Practice management system | Whether the vendor exposes bookings at all | Yes, partially, or no — before you commit |
| EHR | Read or write access, and on what terms | Written into the statement of work, not assumed |
| POS | Whether payments can reconcile | Confirmed during scoping |
| Second and third location | Availability, providers and reporting per site | Quoted per location |
- Location-aware availability
- One owner-level view
- Quoted against scope
Capabilities
What it does, and why that matters commercially
Location-aware availability and routing
Availability, appointment types and providers per site, with one owner-level view across all of them.
PMS, EHR and POS integration
Bookings and payments reconciled against the system your team already works in, where the vendor exposes a usable interface.
Honest integration feasibility, up front
Some practice management vendors do not expose the data required. We establish that during scoping and tell you before you commit, not after.
Implementation
How this gets built, and when it is done
Same standard as every module: a milestone you can verify yourself, not a status report.
Timeline
Set during scoping
Definition of done
The build is accepted when the client can complete a live booking, receive a reminder, and complete a test payment without error.
Built on
- Scoped per engagement
Deployed on infrastructure registered in your name. You hold the accounts, the data and the source code when the build completes.
Who it matters most for
The practices where this leak is largest
Every practice loses something here. These are the ones where it is the dominant loss rather than a minor one.
Dental practices
Two separate leaks: same-week no-shows, and recall appointments that were never rebooked at all. The second one is larger and almost never measured.
Dental systemsUrgent care clinics
Not primarily no-shows. The loss is staff hours absorbed by manual scheduling, phone triage and the queue that forms the moment the doors open.
Urgent Care systemsVeterinary practices
No-shows sit around 10–12% of booked appointments. Each one is a slot that was staffed, prepared and then paid for by nobody.
Veterinary systems
This module on its own is a smaller answer
It closes one leak. The reason it is sold inside a tier is that the next leak sits immediately beside it, and an unowned handoff costs the same whether or not the module beside it is good.
Questions
Custom & enterprise, in detail
Can you integrate with our practice management system?
Sometimes. It depends entirely on what that vendor exposes. We check during scoping and give you a direct answer rather than an optimistic one.
How is this priced?
Quoted against scope. There is no published range because there is no standard shape to a multi-location integration.
Next step
Find out what your booking flow is costing you
Send the four numbers your practice already has. You get a written figure for the monthly revenue your current flow is leaking, and a recorded teardown of where it goes. Three business days, no obligation, no call required.
- 20 minutes discovery call, only if you want one
- 90-Day No-Show Recovery Guarantee
- 3 new practices a month