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

Sydney General Practice.


01 · KPI2 weeksDesign-to-live, single-site GP build
02 · KPI< 480KBHero page weight on a hardened template
03 · KPI0 ticketsMaintenance work raised across the first quarter
01
The problem

The problem

A Sydney solo GP needed to retire a legacy practice site that had drifted into HealthEngine-style boilerplate. Bookings were leaking to third-party directories the practice did not control. The principal wanted ownership of the channel before flu season opened intake.


02
The constraint

The constraint

Most GP sites read identical because most are built off the same directory templates — services list, opening hours, photo of the building. That sameness IS the conversion problem. AHPRA s.133A rules out the testimonial shortcuts a generalist would reach for; practice-character and clinical scope become the only differentiators that survive review and read distinctive.


03
The approach

The approach

We knew the standard at brief stage, so the IA went to wireframe AHPRA-clean rather than redlined at proof. Practice Launch shipped in compressed scope — services, team, fees, intake — on the studio's hardened Next.js template. Hosting moved in with the build, no third-party booking directory dependency.


04
The outcome

The outcome

Design-to-live in two weeks, brand-to-bookable on the same Friday. Direct bookings overtook third-party referral inside the first month, returning the channel to the practice. Page weight stayed under 480KB and the site has absorbed two browser-engine releases without a maintenance ticket.