Healthcare2026UA
ELARA Dental Studio
Diagnostics, treatment, implants, veneers and aligners — organised by what the patient is worried about, not by what the clinic is equipped with.
- Website
- Booking
- Services
- SEO

- Industry
- Healthcare
- Engagement
- 5 weeks
- Team
- 1 designer · 1 engineer
- Platforms
- Marketing site · Service pages · Booking flow
01
Challenge
Clinic websites are organised the way clinics are organised — by department and procedure. Patients do not arrive with a procedure in mind; they arrive with a problem and a fear.
Dental care in particular is chosen on trust, and trust is built by being specific about what happens, what it costs and what it feels like — the three things most clinic sites avoid.
- Services
- Diagnostics · treatment · implants · veneers · aligners
- Decision basis
- Trust, not price comparison
- Positioning
- Without pain or unnecessary prescriptions
02
Solution
Entry points are patient-shaped — a problem, a concern, a goal — and each one leads into the relevant treatment path with the procedure, the stages and the time it takes.
Each service page states what actually happens step by step. Being explicit about the process is the single most effective anxiety reducer available, and almost nobody does it.
Booking is short and reachable from every service page, carrying the treatment context with it so the clinic knows why someone is coming.
- Navigation
- By patient concern, not department
- Content
- Explicit stages and durations
- Booking
- Context-carrying, always one step away
03
Architecture
- L0SiteStatic
- L1Service modelStages, durationBooking flowClient
- L2Booking actionServer action
- L3Clinic schedulingExternalNotificationsSMS / messenger
Connections (5)
- Site → Service model
- Service model → Booking flow · context
- Booking flow → Booking action
- Booking action → Clinic scheduling
- Booking action → Notifications
04
UX
The reading order matches the patient's: what is wrong, what is done about it, what it involves, what it costs, who does it.
Nothing is gated behind a phone call. The information a patient needs to decide is on the page, which is what makes the booking step feel small.
05
UI
Calm and clinical without being cold — generous spacing, soft contrast, and photography of people rather than equipment.
Prices and durations are stated plainly in a consistent format wherever they appear.
06
Development
Service pages are generated from a content model with structured data, so each treatment page is individually indexable for the searches patients actually run.
Booking submissions go through a server action with validation, delivering to clinic scheduling and notifying staff immediately.
07
What it does
Concern-led navigation
Entry by the patient's problem rather than the clinic's departments.
Treatment paths
Stages, durations and what actually happens, stated explicitly.
Transparent pricing
Costs presented consistently rather than on request.
Contextual booking
Booking carries the treatment the patient was reading about.
Structured data
Per-treatment markup for the searches patients run.
08
Integrations & stack
Integrations
- Clinic scheduling
- SMS / messenger notifications
- Analytics
Frontend
- Next.js
- TypeScript
- Tailwind CSS
- next/image
Platform
- Static generation
- Server actions
- Structured data
09
Where it landed
- Patient-shaped
- Navigation
- Stated explicitly
- Process
- Carries context
- Booking
- Per-treatment
- Indexing
Stages and durations on every service
A clinic site that answers the questions people are too uncomfortable to ask on the phone.




Every build is designed for the phone as its own experience, not as a narrowed desktop layout.
Got a product that should exist by now?Tell us about it.
Describe what has to change in your business. We will work out what that actually takes — including when it takes less than you think.