Webflow Review: What We've Learned from More Than 50 Webflow Projects

For most B2B SaaS marketing teams, Webflow is worth it if the setup is tailored to their recurring tasks. We mainly see limits when you need a CMS as a central data source independent of the website, and for teams that want to manage their website as code.

We've been working with Webflow for six years, and our assessment comes from more than 50 Webflow projects. path digital is a Webflow Enterprise Partner. Because we also migrate some clients away from Webflow, we name the limits here just as openly as the advantages.

Three things have been confirmed again and again in these projects.

The setup matters more than the tool. A Webflow website where nobody planned components and CMS fields around marketing's tasks still needs an agency for every new landing page after launch. After its relaunch, hellotax can launch campaigns on its own, without depending on external developers. SAIZ makes changes itself and therefore describes the website as low-maintenance. The same editor leads to a different daily routine when the templates are missing.

Content has to fit the CMS, otherwise it stays hard to maintain. At Converia, the blog lived on a WordPress subdomain, with callout boxes, downloads and tables as special formats. When moving to Webflow, we rebuilt these formats as reusable components and responsive embeds. Otherwise, shortcodes would have ended up in the articles that can no longer be edited sensibly. Today Converia often maintains the CMS with AI support via the Webflow MCP server.

Handover has to happen on real tasks. That's why, with us, your team practices concretely how to add testimonials or build campaign pages. A general training on the editor isn't enough if the first case study or the next campaign then gets stuck again.

What changes day to day after switching to Webflow

With the right setup, your marketing team builds new pages from prepared building blocks and maintains content such as testimonials or use cases itself. Whether that works depends less on the Designer than on the planning before the build. If you're new to Webflow, you'll find the basics in our article What is Webflow?

New landing pages without developers

For a campaign or a webinar, your team combines prepared sections into a new page. The layout sets the frame so your brand stays consistent. This only works if someone planned beforehand which pages marketing builds regularly.

At hellotax, that was the noticeable difference after the relaunch. Before, the team depended on external developers. Today it has control over the website again and can launch new campaigns on its own. Cristian Noguera, founder of hellotax, attributes exactly that to the switch. The higher conversion rate of the relaunch, however, doesn't come from Webflow alone, because messaging and design changed at the same time.

Maintaining content in the CMS

Customer testimonials and use cases get their own CMS collections with fixed fields in Webflow. Your team changes the content there without touching the page layout. A new case study then automatically appears in the right design.

Less operational effort

Webflow bundles CMS and hosting on one platform, and platform updates run through Webflow itself. Plugin updates and server maintenance, as you may know them from WordPress, disappear. Integrations with your CRM or booking tools still remain a planning task that someone has to look after. You'll find a detailed system comparison under Webflow vs. WordPress.

What doesn't automatically get better

A new system doesn't fix an unclear message. If buyers didn't understand what you sell before, they won't understand it any better after moving to Webflow. So you need to clarify positioning and structure before or during the switch.

Experiences of B2B SaaS teams after the switch

Teams that switched to Webflow with us mention two things above all. They change pages themselves, and they spend less time on maintenance.

The hellotax conversion figure is a customer statement about a relaunch in which messaging and design also changed. It therefore can't be attributed to Webflow alone, nor transferred to other websites.

Webflow's downsides from our experience

Webflow has real downsides you should know before switching. The most important are the learning curve in the Designer and the limits of each plan. For teams in Germany, billing in US dollars and a privacy setup you have to complete yourself come on top.

For a typical SaaS marketing team, CMS items are rarely the first limit to bite. Since the plan simplification in May 2026, the Premium site plan includes 20,000 CMS items and 40 collections, at USD 25 per month billed annually or USD 39 billed monthly. Webflow describes this in its help article on the updated site plans (help page as of 31 Aug 2026, checked by us on 9 Nov 2026). More relevant are additional languages via the Localize add-on, more team members via workspace seats, or features only included in the Team plan or Enterprise. The Team plan bundles, among other things, a site with 100 CMS collections, 10 seats and Webflow Localize.

Webflow describes billing in US dollars in its help article on workspace billing and invoices, and the missing built-in consent banner in its help article on tracking consent. How support works is set out in the Customer Support Policy. Prices and limits can change, so check them on webflow.com/pricing before you decide, and get legal advice on privacy questions.

When Webflow isn't the right choice

Webflow fits less well if you need content as a central data source independent of the website system, or if your team wants to work with Git and code review. It's also worth looking at an alternative if AI agents should work directly in the code or if an upgrade within Webflow no longer meets the requirements. In these cases, we build with Astro and Sanity and also migrate existing Webflow websites there.

Content should also flow into other systems

Webflow stores content in CMS collections that mainly serve the website. Via the CMS API, you can create, update and publish items. The Content Delivery API also delivers published content to other channels, such as apps or email sequences, serving it from a cache.

Still, Webflow remains a website-bound CMS. The data model follows collections and fields you built for pages. The content lives in Webflow, and a later system switch means migrating it. Sanity, as a headless CMS, is independent of the front end: you model content once as a data source for the website, product app and help center, and you keep it when the website system changes. Webflow is enough if the website is the main channel and other systems occasionally read along. A separate headless CMS is worth it when many systems need the same source or you want to decouple content from the website stack.

Your team wants to own the code

Some teams want their website in their own Git repository, with version history and review for every change. With Webflow, the code lives on the platform. If you want to choose your hosting provider freely and switch without a rebuild, Astro serves you better.

AI agents should work along

AI agents can also work in Webflow. The Webflow MCP server gives agents access to CMS content, pages, components, styles and other site data, within existing permissions. You don't need your own Git repository for this. Converia often fills its Webflow CMS exactly this way with AI support.

A code-based setup with Astro has different strengths. Changes live in your own repository, with version history and review before anything goes live. You can choose hosting independently of Webflow, and agents work directly in the code, the way we implement it in AI-native websites. Webflow MCP is a good fit if your team wants to stay in the platform and prepare content or components with AI. Astro is worth it if you want to own the code and have every change go through Git.

The project hits plan limits

Not every plan limit justifies a system switch. If you just need more CMS items, additional collections, languages or seats, an upgrade within Webflow is the obvious first solution, for example from the Premium plan to the Team plan or to Enterprise. The Team plan, for instance, includes 100 CMS collections, 10 seats and Localize.

A switch to Astro with Sanity makes sense when the limit no longer lies in the plan but in the way you work. Typical reasons are a CMS that should serve as a central data source independent of the website system, your own Git repository with code review, or custom code that only runs in Webflow via embeds. Which limit really applies to you can only be checked against the specific plan and your integrations. How a switch works in this case is shown on our page about migrating from Webflow to Astro.

What to clarify before switching

Before switching, clarify which pages your team builds regularly and how much content and how many languages there are. Just as important are the connected tools and a plan for how the old URLs will be redirected. This checklist helps you prepare.

• Capture page types and content volume
• Define languages and planned markets
• Clarify integrations, such as CRM, forms and booking tools
• Define roles: who maintains which content
• Plan the privacy setup with a consent tool and a data processing agreement
• Create a URL list and redirect plan
• Record rankings, organic traffic, conversions and backlinks per URL, so important pages don't get lost in the migration
• Plan handover and training around concrete tasks
• Budget for the Webflow plan and licenses

We describe the migration process in detail in our article on Webflow migration. If URLs change during the switch, our guide to SEO during a relaunch will help.

Our verdict

Webflow is worth it for most B2B SaaS marketing teams if the setup fits their tasks. Anyone who needs content as data in several systems or wants to manage the website as code should take a closer look at Astro with Sanity.

In our projects, the biggest difference comes from the planning before the build. We see websites built in Webflow that still need an agency for every new landing page, because nobody planned components and CMS fields around marketing's tasks. That's why we ask before the design which pages your team builds regularly, and from that come the templates for the time after launch.