Case study · Clinic consultation booking
A skin clinic's consultations ran on manual back-and-forth. We built a booking pipeline instead.
PrimeraSkin needed a new client to book a consultation without a phone call or a message chain. We built a site where the booking flow itself moves a visitor toward a scheduled consultation.
Built by Alchemetryx · Live client site
01 / The before
A consultation took a conversation to arrange.
Every new client meant a manual conversation before a consultation was even on the calendar. No structured flow existed to move someone from finding the clinic to actually booking a slot.
Manual appointment setting
Consultations were arranged case by case, with no set process for a new enquiry.
Administrative load on the founder
Every booking-related task landed on the founder, on top of running the clinic itself.
No structured intake
Nothing captured what a client needed before the first conversation happened.
02 / The build
A site built around getting a consultation booked.
Treatment pages, a personalised-regimen section, and a consultation flow that runs on its own, so a visitor can move from reading about a treatment to booking a consultation without a phone call.
Built to convert a visit into a booking.
The homepage leads with one action: secure a consultation. Treatments, expertise and social proof sit around that single path, not competing with it.
The consultation flow itself.
A personalised-regimen section structures what a client needs before the first conversation happens, instead of that intake being worked out over a phone call.
What this is, and what it isn't — "Zero-touch scheduling, not a measured savings figure."
Zero-touch scheduling, not a measured savings figure.
If every new client still means a phone call before a booking exists, that's the gap this closes.
This replaced a manual process with a structured one, but there is no baseline number for hours or bookings before this site existed, so we are not stating one. What changed, plainly: appointment setting now runs as a scheduling flow the site handles on its own, not a task that lands on the founder for every enquiry.