Regimen
← All work/Dental · Website design & build · Hosting & maintenance
Case study

Melbourne Dental Network.


01 · KPI6 sites, 8 weeksNetwork site system on shared template
02 · KPI1 pushNetwork-side promotion across six sites
03 · KPI7th siteAcquired and onboarded with no rebuild
01
The problem

The problem

A Melbourne dental network had grown by acquisition to six sites, each carrying the previous owner's website. Six different booking systems, six fee schedules in six different formats, and one general manager trying to publish a network-side promotion across all of it. Patient complaints about pricing inconsistency were monthly.


02
The constraint

The constraint

Acquisition-built networks inherit chaos — six PMS systems, six fee schedules, six legacy CMSes. Most multi-site agencies treat each site as an island; the harder work is one source of truth on services, fees and capacity, with site managers free to localise inside guardrails. AHPRA dental rules and cosmetic guidance set the copy floor, but the engineering challenge — CMS schemas that render compliant by default — was the actual moat.


03
The approach

The approach

One template, six catchment-tuned instances, single source of truth on fees and services. AHPRA-clean copy patterns built into the CMS field schema, so local site managers couldn't ship a flag-marked claim without override. Hosting consolidated. Booking unified to the network's primary PMS.


04
The outcome

The outcome

Six sites launched on the shared template in eight weeks, fee inconsistency complaints retired inside two weeks of go-live. The general manager now ships a network-side promotion in one CMS push. The template has absorbed a seventh acquisition since, with no front-end engineering required.