What to check before you inherit a custom app
What to check before you inherit a custom app: code and deploy-key control, tests, patches, and whether a fix can ship tomorrow.
·
4 min read
Online booking for clinics is a solved problem for most practices, so off-the-shelf is usually the right answer. You'd build your own only when the way you take bookings is part of how the clinic actually works: several sites, clinical intake, rules about who can book what, or patient data you need to control. Here's how to tell which side of that line you're on.
A subscription booking tool gives you a live diary, a booking page, reminders and payments without a development project. Tools such as Fresha, Phorest and Timely exist because so many salons and clinics need roughly the same thing. Someone else fixes the bugs, handles the mobile apps and keeps it running at 2am.
For a single-site aesthetics or physio clinic with a clear treatment menu, that's hard to beat. I'd tell most owners in that position to pick one, set it up properly and spend their budget on the website that sends people to it.
The honest limitation is that you're renting someone else's idea of how a clinic runs. When your process doesn't match theirs, your staff end up working around the tool with notes, spreadsheets and phone calls.
The warning signs are usually operational, not cosmetic. Receptionists re-key bookings into a second system because the booking tool can't talk to your records. Consultations and treatments need different rules (a consultation first, a cooling-off period, a practitioner with the right qualification) and the tool can only approximate them. Patients fill in the same medical history on paper every visit.
Data is the other one. Health information is special category data under UK GDPR, so you need to know where it's stored, who can see it and how you'd get it all back if you left. Some platforms answer those questions well. Some make leaving painful, and you find that out only when you try.
And per-seat or per-location pricing can climb as you add practitioners and sites. That's not a reason to build on its own, but it changes the sums once a group reaches three or four clinics.
A custom booking system is software written around your clinic's rules. It holds your treatment types, your practitioners and what each is allowed to do, your intake forms and your sites, and it connects directly to the systems you already use rather than through exports.
When we build one, the clinic owns the code, the repository, the cloud account and the data from day one, and it's hosted in UK or EU regions by default. We start with a focused first release that takes a few weeks and is priced after a scoping conversation, then add to it release by release, so you're never paying for a big-bang project before anything works. You can read more on our software development page.
The trade-off is real. You now own a piece of software, which means someone has to maintain it, and a first release won't have every feature a mature product has built up over years.
If you run one clinic and your team isn't fighting the booking tool, stay off-the-shelf and put your effort into the website. That's where new patients decide whether to book at all. We build and manage clinic websites for practices such as Faha Aesthetics, and linking a site to the booking tool you already use is the sensible default.
If you're running several sites, re-keying bookings, or keeping clinical rules in people's heads because the software can't hold them, that's the point to look at online booking for clinics built around how yours works. Buy the diary until the diary starts running you.
Not sure which side you're on? Tell us how bookings work in your clinic today and where they go wrong, and we'll give you a straight view on whether to keep what you have, fix the website or build something. Start a conversation with Eight Mile.
What to check before you inherit a custom app: code and deploy-key control, tests, patches, and whether a fix can ship tomorrow.
·
4 min read
What a website quote should include beyond the build: hosting, domain ownership, care and who fixes the site at 2am.
·
4 min read
The agency that built your website has disappeared. How to recover access, move hosting and DNS into the business, and choose care or a rebuild.
·
4 min read
Leaving a freelancer with your AWS root login is a risk even after a good build. How to take back control with named IAM, MFA and a handoff.
·
4 min read
CRM for a small firm off the shelf or built: when HubSpot-class tools fit, and when a system on your own job data serves trades and clinics better.
·
4 min read
Uptime monitoring for a small business website only works with a named engineer and response path. What a care plan or managed hosting should cover.
·
3 min read
If your website form still emails one person's Gmail, enquiries vanish when they're away, and a shared lead list with an owner fixes it.
·
4 min read
Who actually owns your business domain name? How to check the registrant and account holder, and move both into company hands.
·
4 min read
GDPR and cookies on a small business website: when cookies need consent under the 2026 rules, and how long to keep contact form data.
·
4 min read
How to approach moving off Wix or Squarespace without losing your Google ranking, from exporting content to setting up 301 redirects.
·
4 min read
Still running the business on Microsoft Access? The signs it's holding you back, and when to keep it, move to a product or rebuild it.
·
4 min read
Connecting your job system to Xero or QuickBooks: when an export is enough, when a connector fits, and when a custom integration pays.
·
3 min read
Why your business doesn't show up on Google Maps: verification, categories, mismatched details, service areas, your website and reviews.
·
4 min read
How much does a small business website cost in the UK? What drives the price, how DIY, freelancer and agency compare, and how Eight Mile prices sites.
·
3 min read
Field team software fails without offline-first: vans need capture, queue, and sync that works when signal dies.
·
3 min read