Meridian Clinic
A multi-specialty clinic website with online booking and doctor profiles.
How the project moved.
Where we started
The clinic's existing site was three years out of date, mixed staff and departments in confusing ways, and forced every appointment through a phone line the front desk couldn't keep up with.
What success looked like
Redesign the site around patient journeys, not departments. · Ship an online booking system with real-time slot availability. · Publish doctor profiles as first-class content. · Improve local SEO for each clinic branch.
What we learned first
We shadowed the front desk for a day. The most common calls were reschedules and 'is Dr. X available next week?' Both became one-tap flows on the new site.
The shape of the experience
Wireframes were organised around what patients actually search for: symptom → specialty → doctor → slot. Each step reduced questions rather than adding them.
How it looks and feels
Calm, editorial layout. Doctor photography treated respectfully — no stock. Booking flow designed as a linear, uninterrupted path.
How it's built
Built on Next.js with a booking engine wired to the clinic's practice-management system. Doctor availability syncs both ways, so the front desk stays in control.
Across every screen
Booking flow designed mobile-first — most patients book on their phones. Sticky CTAs and fingertip-sized time slots.
- ▸AI-assisted intent classifier on the contact form to route enquiries to the right department.
- ▸Booking confirmations via email + WhatsApp.
- ▸Automated reminders 24h and 1h before appointment.
- ▸Reschedule links that avoid a phone call.
- Manrope — Display · headings
- Inter — Body · UI
Production quality
- · Booking flow designed mobile-first — most patients book on their phones. Sticky CTAs and fingertip-sized time slots.
- · Per-branch local landing pages with LocalBusiness schema.
- · Doctor profile pages with Person + MedicalOrganization schema.
- · FAQ schema on service pages.
- · Google Business Profile hooked into the site content.
- · Static rendering for content pages, dynamic for booking.
- · LCP-focused hero optimisation.
- · Zero third-party trackers on booking flow.
- · WCAG 2.2 AA with a healthcare-content review.
- · Booking flow tested with keyboard and screen-reader.
- · Text sizes tuned for older patients.
- · No patient data stored outside the practice-management system.
- · Booking form submits over HTTPS with rate limiting.
- · PII scrubbed from logs and analytics.
Screens & mobile experience
Notes we keep coming back to.
- 01Healthcare copy has to reassure before it converts.
- 02The front desk knows more about UX than most consultants.
- 03A booking flow succeeds or fails on the first date picker.
Questions about the Meridian Clinic project.
Does this integrate with a practice-management system?
Yes — the booking engine syncs to whichever system the clinic already uses.
Is patient data stored on your site?
No — the site never persists PII. Bookings pass through and live in the clinic's system.
Can we manage doctor availability ourselves?
Yes. The front desk uses the same practice-management calendar; the site reflects it.
Do you handle multi-language?
Yes — we've delivered multi-language health sites in English + one Indian language pairing.
Have a project that needs this kind of care?
Book a 30-minute consultation. We'll talk through what you're trying to build — and whether Siddiq.in is the right studio to build it with you.