- Year
- 2026
- Timeline
- 3 weeks
- Our part
- Full stack build
- Where it was built
- Client project
The brief
An endovascular clinic with the usual medical-practice website problem: slow, outdated, and impossible for staff to change. It needed to build trust before a first visit, be editable by the clinic itself, and rank for local medical searches.
What was actually hard
Three weeks, and the CMS could not be a generic page builder. Treatments, services, team members and posts are different shapes with different SEO needs. Bolting schema markup onto templates means it goes stale the first time staff edit a page, so it had to be part of the data model itself.
What we decided.
- 01
SEO and JSON-LD live in the model
Title, description, keywords and structured data are fields on the content itself. When staff update a treatment page, its schema markup updates with it — there is no second place to forget.
- 02
A schema per content type
Treatments, services, team members and posts each got their own shape instead of being forced through one generic page type. It costs more up front, and it is why staff can actually maintain it.
- 03
Four fields, not eight
Patients were dropping off on the booking form. Halving the fields and adding a progress indicator addressed it — in healthcare, the person filling in the form is already anxious.
- 04
Tracked the taps that matter
WhatsApp and call taps are tracked as conversions. For a clinic those are the real outcome; a form submission is the minority path.
Where it landed
Live, with the clinic managing all of its own content. Built and shipped in three weeks.
How it fits together
- What it is
- Clinic platform + CMS
- Status
- Live in production
- Sector
- Healthcare
- Built in
- 3 weeks
- Editable by
- Clinic staff
- Admin auth
- NextAuth, role-based
- Stack
- Next.jsTypeScriptPrismaMySQLNextAuthTailwindRadix