How Sisu Clinic Scaled to 25+ Locations on One Webflow Site

Sisu Clinic runs 25+ cosmetic medicine clinics across 4 countries — Ireland, UK, US, and Northern Ireland. Their entire web presence sits on Webflow Enterprise. 85+ pages. 30+ CMS collections. 4 Webflow projects.

And the initial build? Four days.

Here's what that looks like in practice, and why multi-location healthcare websites are one of the hardest problems in web development.

The Problem with Multi-Location Healthcare Sites

If you run one clinic, your website is straightforward. You have a homepage, a services page, a booking page, an about page. Maybe a blog.

Now multiply that by 25+. Across 4 countries. Each location has its own address, phone number, operating hours, treatment menu, and team members. Some treatments are available at certain locations but not others. Regulatory requirements differ between Ireland, the UK, and the US. Pricing structures vary.

Most companies in this situation end up with one of two bad options:

1. 25 separate websites — a maintenance disaster where every brand update means touching 25 codebases
2. One generic site — where location-specific content gets buried or ignored, and local SEO suffers

Sisu needed a third option: one website, one design system, but with location-specific content that felt local to each clinic.

What We Built — In 4 Days

The first version of Sisu's Webflow site was built from scratch in 4 working days, launching on January 10th, 2022. Four working days of active development.

The project kicked off over the holiday period in late December. We shipped a working, live site by January 10th — the timeline was tight because Sisu was moving fast — they'd raised $15M, had 10,000+ clients, and needed a web presence that matched their growth.

The Architecture

4 Webflow Projects

Rather than cramming everything into a single project, we used 4 Webflow projects. This keeps each project manageable and allows location-specific customisation without bloating a single codebase.

30+ CMS Collections

The CMS architecture is the backbone. Separate collections for locations, treatments, team members, testimonials, blog posts, FAQs, and more. Each collection connects to the others through reference fields, so a treatment page can pull in the specific locations where that treatment is available.

85+ Pages

Including location pages, treatment pages, team pages, and informational content. Each location page has geo-targeted content — the right address, the right phone number, the right treatments, the right team members.

Geo-Targeted Content

Different content serves different regions. A visitor in Dublin sees Irish-relevant information. A visitor in New York sees US-specific pricing and regulatory details.

Integrations

• JazzHR and Lever — for recruitment and hiring across multiple countries
• Jetboost — for filtering and search functionality across the CMS
• Shopify — integrated commerce for products sold through the clinics
• Finsweet Attributes — for extended CMS functionality
• SEO-specific setup — location-specific meta tags, structured data for each clinic, and local SEO signals

The Results

25+ Clinics, One Design System

Every Sisu clinic has a consistent brand experience online. When they open a new location, adding it to the website means creating a new CMS entry — not building a new site.

4 Countries, One Platform

Ireland, UK, US, and Northern Ireland. Each with its own regulatory considerations for cosmetic medicine advertising. The CMS structure handles this by allowing country-specific content overrides without duplicating the entire site.

$15M Raised, 10,000+ Clients

Sisu is scaling fast. A website that couldn't handle multi-location complexity would have become a bottleneck months ago. Instead, their marketing team can add locations, update treatment information, and manage content independently.

Webflow Enterprise

Sisu is one of our two Webflow Enterprise clients. Enterprise gives them priority support from Webflow, enhanced security, and the infrastructure to handle the traffic that comes with 25+ physical locations driving online visitors.

What the CMO Said

Spencer, Sisu's Chief Marketing Officer:

"Parth, you are literally the definition of a godsend. Thank you for helping bring our UX strategy and rebrand to life. You're an amazing developer and a joy to partner with!"

How This Compares to Other Healthcare Web Work

Sisu isn't our only healthcare client. We also migrated Wellness Everyday from Joomla to Webflow — 70+ pages, 100% SEO preserved, zero downtime during the transition.

The healthcare vertical has specific requirements that generic web agencies tend to miss: location-specific structured data, treatment taxonomy that maps to how patients actually search, and content management workflows that non-technical clinic managers can use.

Why Multi-Location Healthcare Sites Are Hard

Location Data Has to Be Perfect

If a patient in Cork sees a phone number for your Dublin clinic, that's a trust-breaking mistake. Multi-location CMS architecture has to guarantee that every piece of location-specific data is correct for that specific location.

Local SEO Is a Multiplier

Each clinic location is a separate local SEO opportunity. That means unique title tags, unique meta descriptions, unique structured data (LocalBusiness schema), and unique content for each location page.

Content Updates Are Constant

Clinics add new treatments. Team members join and leave. Hours change for holidays. Pricing updates. The CMS architecture we built for Sisu puts these updates in the hands of their marketing and operations teams.

Regulatory Differences Are Real

Cosmetic medicine advertising in Ireland follows different rules than in the UK, which follows different rules than in the US. The content management system needs to support country-specific overrides without creating a maintenance nightmare.

Key Takeaways

• Use CMS reference fields to connect locations, treatments, and team members — it keeps data consistent across 25+ location pages
• Run multiple Webflow projects instead of one overloaded project when managing multi-region sites
• Build geo-targeted content into the CMS architecture from day one, not as an afterthought
• Give operations and marketing teams direct CMS access for location data updates — developer bottlenecks will kill data accuracy at scale
• Treat each location page as a local SEO asset with unique metadata and structured data

Frequently Asked Questions

How does Sisu Clinic manage 25+ locations on one website?

Sisu Clinic uses a Webflow Enterprise setup with 4 Webflow projects, 30+ CMS collections, and 85+ pages. Each location has its own CMS entry with location-specific data (address, phone, treatments, team), and the site uses geo-targeted content to serve relevant information by region.

Can Webflow handle multi-location healthcare websites?

Yes. Sisu Clinic runs 25+ clinics across 4 regions on Webflow Enterprise. The architecture uses CMS reference fields to connect locations, treatments, and team members, with geo-targeted content for different regions. Each location page serves as a separate local SEO asset.

How fast was Sisu Clinic's Webflow site built?

The initial version of Sisu Clinic's Webflow site was built in 4 working days of active development, launching on January 10th, 2022. This was followed by a QA process and ongoing development as the clinic network expanded.

How does multi-location CMS architecture work for healthcare websites?

Multi-location CMS architecture uses separate collections for locations, treatments, team members, and other content types connected through reference fields. Each location page pulls in its specific data — address, phone number, treatments, team — automatically. Sisu Clinic uses 30+ CMS collections across 4 Webflow projects to manage 25+ clinics across 4 regions, allowing the marketing team to add new locations by creating a CMS entry rather than building a new site.

If you run a multi-location healthcare practice and your website can't keep up with new locations, we built the playbook for this.