Sisu Clinic: How We Built 85+ Pages for a Multi-Country Healthcare Brand on Webflow Enterprise — Over the Holidays

Quick answer: The reason we shipped 85+ pages for Sisu Clinic on Webflow Enterprise in about two weeks over the holidays wasn't speed for its own sake. We got the CMS and URL structure right first — 30+ collections driving every location and treatment page — so the build was assembly, not invention, and Sisu's team could keep launching pages after launch.

By Parth Gaurav, Founder & CEO, Digi Hotshot. Last updated: June 25, 2026.

The setup: an Enterprise build with a holiday deadline

The Webflow team brought us in for Sisu Clinic at the end of December 2021. Sisu is Europe's largest dedicated aesthetic injectable provider — 25+ doctor-led clinics across Ireland, the UK, and the United States, backed by Greycroft, $15M+ raised, 10,000+ clients, partnered with retailers like Harvey Nichols. They had their own design team. What they needed was Webflow development expertise, and they needed it fast.

Two constraints made this harder than a normal build. First, it was a Webflow Enterprise client, so we had to build directly on Sisu's own platform — no starting in our account and transferring it over later, which is how we'd usually de-risk a tight timeline. Second, the deadline. We started on December 25th and launched around January 10th. About two weeks, holidays included.

Here's the part that matters for any CMO reading this. With 85+ pages and a multi-country, multi-treatment site, the obvious failure mode is the page architecture collapsing under its own weight — every clinic and every treatment becoming a one-off page someone has to hand-build and hand-maintain forever. That's the trap. And it's the thing we spent our planning time avoiding.

The one lesson: speed came from the CMS, not from cutting corners

People assume a fast build means a thin build. On a large regulated healthcare site, the opposite is true. The speed came from getting the information architecture right before we touched a single page design.

Sisu's site has two axes that multiply against each other: locations (Ireland, UK, US, Northern Ireland) and treatments. If you build that page by page, you're hand-coding hundreds of near-identical pages and praying nobody needs to change a disclaimer across all of them. So we didn't. We built it as data.

• 30+ CMS collections modelled the real structure — clinics, treatments, and the relationships between them —so a location page and a treatment page are generated from records, not drawn from scratch.
• Location-specific and treatment-specific URL structures were designed up front, so the URLs were clean and predictable from day one rather than retrofitted later.
•  4 Webflow projects split the work so the site stayed organized at that scale instead of cramming everything into one straining project.
• Jetboost real-time filters and search sat on top of the CMS, so a visitor can filter by treatment or find their nearest clinic without a page reload.     

Get that foundation right and the rest isfast because it's repeatable. We built the core framework from scratch in aboutfour days. Then we spent roughly a week on rigorous QA and loading Sisu'scontent — which, on a healthcare site, is where the real care goes. Treatmentcopy and clinic details aren't things you rush. The four-day framework boughtus the time to be careful where carefulness actually counts.

Why this matters more for regulated, multi-location health

If you run marketing for a healthcare brand operating across regions, you already know the page count never stops growing. New clinic opens — that's a page. New treatment launches — that's a page, times every location that offers it. New region, new compliance language. The site is never "done."

A CMS-driven build is what keeps that growth from becoming an engineering bottleneck. When the structure is modeled correctly, your marketing team adds a clinic by adding a record, and every page that should reference it updates itself. That's the autonomy we build for across our B2B work — and on multi-location health it's not a nice-to-have, it's the only thing that scales.

It's also why the relationship didn't end at launch. We've continued to manage Sisu's site and launch new pages since 2022. A site built as data ages well; a site built as 85 hand-made pages doesn't.

The same architecture-first thinking shows up in everything we do for healthcare teams — more on that in our guide to Webflow for healthcare companies — and the Enterprise-specific constraints we hit on Sisu are covered in our Webflow Enterprise guide. If governance and approval workflows are your concern, our piece on Webflow for regulated industries and MLR content governance goes deeper there (forward link — publishing in the same window).

The numbers

FAQ

How did you build 85+ pages on Webflow in about two weeks?

By building the site as data, not as pages. We modeled the structure into 30+ CMS collections so location and treatment pages are generated from records instead of hand-built one at a time. The core framework took about four days; the rest was QA and content loading. The CMS work up front is what made the page count manageable.

What does "Webflow Enterprise" mean for a build like this?

For Sisu, the practical effect was that we had to build directly on the client's own Webflow platform — we couldn't start the work in our account and transfer it over, which is how we'd normally protect a tight timeline. Enterprise is Webflow's custom-priced tier for larger organizations. Our Webflow Enterprise guide covers it in full.

Why use a CMS instead of static pages for a multi-location site?

Because a multi-location, multi-treatment site multiplies. Static pages mean someone hand-builds and hand-maintains every clinic-and-treatment combination. A CMS-driven structure lets the marketing team add a clinic or treatment as a record, and the related pages update themselves — no developer in the loop for routine additions.

What did Jetboost do on the Sisu site?

Jetboost added real-time filtering and search on top of the Webflow CMS. Visitors can filter by treatment or find their nearest clinic without a page reload, which matters when you have records across four countries and a long treatment list.

Is Webflow a good fit for regulated healthcare websites?

For the marketing site, yes — when the architecture is right. The win is giving a small marketing team the ability to publish and update content without engineering dependencies, while a CMS-driven structure keeps compliance language and page templates consistent across locations. We go deeper in our guide to Webflow for healthcare companies.

Want this for your site?

If your healthcare or multi-location site is growing faster than your team can hand-build pages, that's usually a CMS architecture problem, not a headcount problem. We'll do a free audit of your current setup and tell you where it'd break at scale — no pitch, just the read.

Read the full Sisu Clinic case study →