Since 29 January 2026, Webflow has had no native way to log a visitor in. The company switched off User Accounts that day, seven months after it retired Logic, its built-in workflow automation (Webflow Help Center). For a B2B SaaS company that settles the first architecture question before any design work starts: Webflow is the marketing site, and the product, the login and anything that runs per user live somewhere else.
This guide covers what Webflow does well for SaaS, the limits a SaaS site reaches, and four ways to connect the two halves. Figures come from Webflow's pricing page, help centre and developer documentation, read in October 2026, plus two customer stories labelled as vendor material.
What Webflow does well for a SaaS marketing team
The case for Webflow in SaaS is about who can ship a page. A SaaS marketing team publishes constantly: launch pages, comparison pages, integration pages, a changelog, a resource centre. When each waits for a product engineer, the website becomes the slowest part of the go-to-market plan.
Marketer ownership. Webflow's customer stories make that argument with numbers, and they are the vendor's numbers. Greenhouse, a hiring platform, moved more than 1,000 pages off a custom Craft CMS stack and, Webflow says, saw a 40% conversion improvement on demo request pages through Webflow Optimize testing and 50% faster event page creation. Dropbox Sign moved its site off an engineering-managed custom build and reports a 67% decrease in developer tickets, with pages built in a week rather than a month. Treat these as best cases chosen by the seller; the mechanism is real, though: the people who write the page can publish it.
A CMS sized for a resource centre. The Premium plan holds 20,000 items across 40 collections. That covers a blog, case studies, an integrations directory, a glossary, a changelog and a locations or partners index on one site. Our largest Webflow build holds over 1,200 items, well inside the cap.
No server to maintain. Hosting, SSL, the CDN and backups come with the plan. There is no plugin layer to patch, which is the main operational difference from WordPress; our Webflow vs WordPress comparison covers that in detail.
SEO controls in a panel. Titles, canonicals, sitemaps, redirects and per-item indexing are settings, not code. Our post Webflow or Next.js for a Marketing Site? covers where code wins.
We build marketing sites in Webflow and applications in Next.js, so we have a stated bias toward the split this guide recommends. Where Webflow is the wrong tool for part of the job, the sections below say so.
Where Webflow stops: the limits a SaaS site actually hits
SaaS teams rarely meet a Webflow limit on day one. They meet one in year two, when the integrations directory and the localised resource centre arrive together.
| Area | Premium site plan | Team or Enterprise | What it means for SaaS |
|---|---|---|---|
| CMS items | 20,000 | 20,000 on Team; custom on Enterprise | Fine for content, not programmatic pages |
| CMS collections | 40 | 100 on Team | Each content type uses one |
| Reference fields per collection | Up to 10 | 20 on Enterprise | Caps cross-linking between content types |
| Collection lists per page | 40, 100 items each, 3 nesting levels | Same | Large directories need pagination |
| CMS API rate limit | 120 requests a minute | 600 on Team; custom on Enterprise | Product data syncs must batch |
| Site publish through the API | One successful publish a minute | Same | Automated publishes must queue |
| Visitor login and gated content | None since 29 January 2026 | None | Use the product's auth or a membership tool |
| Native automation | None since 27 June 2025 | None | Zapier, Make or your own service |
| SSO and SCIM for editors | No | Enterprise only | A procurement checkbox |
Source: Webflow plans and pricing, Webflow Help Center (Reference Collection field, Dynamic content limits, User Accounts sunset, Logic sunset), Webflow Data API rate limits, read October 2026
Programmatic pages. The 20,000-item cap is generous for content people write. It is not built for 40,000 integration-pair pages generated from a database. That is a code case.
Per-user anything. Quote engines, account-aware navigation, trial status and in-app onboarding cannot run on the Webflow site. Webflow's own advice after the User Accounts sunset points customers to Outseta and Memberstack for gating, and to Zapier and Make for the work Logic used to do.
Lock-in. Code export on a paid Workspace produces static HTML, CSS and JavaScript, but excludes CMS content, code components and localised content, and forms stop working (Webflow Help Center). Content leaves through CSV or the API, not with the export.
The architecture: four ways to connect the marketing site and the product
Every SaaS company on Webflow ends up with two systems on one brand. The choice is how they share the domain.
| Pattern | How it works | Good for | Watch out for |
|---|---|---|---|
| Subdomain split | www.example.com on Webflow, app.example.com on the product stack | Most SaaS companies | Cross-domain tracking and consent |
| Webflow Cloud app at a path | A Next.js, Astro or Vite app mounted at a path such as /tools | Calculators and small tools | Workers runtime limits and partial Node.js support |
| Reverse proxy | Cloudflare Workers or NGINX route paths on one domain to different origins | Docs or a blog under the main domain | Webflow support will not troubleshoot it |
| Headless Webflow CMS | Another front end reads Webflow content through the API | Rarely worth it for SaaS | Loses visual editing |
Source: Webflow Cloud documentation, Webflow Help Center (reverse proxy), Next.js multi-zones documentation, read October 2026
Subdomain split. This is the pattern we would start with for almost every SaaS company. Marketing owns www, engineering owns app, and "Log in" and "Start free trial" are plain links. The cost is shared consent settings and cross-domain tracking, so a trial sign-up is attributed to the page that produced it.
Webflow Cloud. Webflow Cloud deploys an app from a GitHub repository and serves it under a path on the Webflow site's domain, or as an independent app. Framework apps run on Cloudflare Workers, and Webflow's documentation says Node.js APIs are only partially supported. The published limits are tight but workable for marketing tools: 128 MB of memory per worker, a 10 MB worker bundle, a 20-second request timeout and 30 seconds of CPU time per request. The Premium plan includes 15 apps and 2 million requests a month, then $2 per million. An ROI calculator or a migration-cost estimator fits. The core product does not.
Reverse proxy. When the docs or a blog live elsewhere but must sit under the main domain for SEO, a proxy routes paths to different origins. Webflow's help centre documents the setup: publish the Webflow site to an origin subdomain such as wf.example.com, forward path and query string, keep the sitemap pointed at the public domain, and never proxy the webflow.io staging domain. It also says support cannot help configure or troubleshoot third-party proxies. If the other side is Next.js, its multi-zones documentation adds one rule worth knowing: moving between zones is a full page load, and links across zones should be plain anchor tags.
Headless. Another front end can read the CMS through Webflow's content delivery APIs, but that gives up the reason for choosing Webflow: marketers editing the page they see.
Forms, the CRM and the demo path
The demo form is the most valuable element on a SaaS site, and where Webflow's native tools are thinnest.
Webflow forms store submissions and send notifications; routing, enrichment and scheduling belong in the CRM. Webflow's HubSpot app offers three connections. An iframe embed is managed entirely in HubSpot. A developer embed renders the HubSpot form so it can be styled in Webflow, and it requires HubSpot Marketing Professional or Enterprise. Mapping a native Webflow form to HubSpot supports text inputs only: no dropdowns, radio buttons, checkboxes or text areas (Webflow Help Center).
That matters, because a SaaS demo form usually asks for company size in a dropdown. We would use the developer embed where the HubSpot plan allows it, and the iframe where it does not. Our post on demo request conversion rates covers what to ask; the form logic lives in the CRM, not in Webflow.
Feeding product data into the CMS
SaaS sites often publish content that already exists in the product: integrations, templates, changelog entries. Keeping two copies by hand fails within a quarter.
The Webflow Data API allows 120 requests a minute on Premium and one successful site publish a minute (Webflow developer docs). A nightly job that writes changed items, then publishes once, stays inside those numbers for a few hundred items. Team raises the rate to 600 a minute, which matters when a sync touches thousands.
Two rules keep the sync safe. Write only the fields the product owns, so marketing copy added in Webflow survives. And keep the product as the source of truth, because the CMS is a publishing layer. For a sync on the scale of our largest Webflow CMS, over 1,200 items, we would write in batches and publish once at the end, rather than publishing item by item.
When the plan tier changes the answer
Plan tier matters for SaaS because security review arrives with the first enterprise customers.
| Requirement | Premium | Team | Enterprise |
|---|---|---|---|
| Price | $25 a month billed yearly | $2,500 a month, annual contract | Custom |
| CMS collections | 40 | 100 | Custom |
| CMS API rate limit | 120 a minute | 600 a minute | Custom |
| Static pages | 300 | 500 | Custom |
| Hosting uptime listed | Standard agreement | 99.00% | 99.99% |
| SSO, SCIM, audit logs API | No | No | Yes |
| Publishing workflows | No | Yes | Yes |
Source: Webflow plans and pricing; Webflow Help Center, Differences between Enterprise and non-Enterprise plans, read October 2026
The jump from $25 to $2,500 is the steepest step in the pricing. The trigger is usually procurement rather than content: an IT team that requires SSO for anyone who can publish to the company domain, or a security questionnaire that asks for SOC 2 Type II, which Webflow lists among Enterprise features. Webflow's help centre also notes that plans below Enterprise carry no contractual uptime SLA.
Below Enterprise, add-ons cost extra: Optimize, for A/B testing, from $299 a month; Localize from $9 per locale.
What this means for a SaaS team choosing Webflow
Webflow fits a B2B SaaS company when the website is a marketing asset that marketers run and the product is a separate application. It does not fit when the two blur: per-user pages, account-aware pricing, tens of thousands of generated pages.
Four decisions settle the architecture:
- Draw the logged-out line. List every page that needs to know who the visitor is. Those go to the product or a third-party tool; everything else goes to Webflow.
- Pick the domain pattern. Subdomain split by default. Webflow Cloud for small interactive tools. A reverse proxy only when SEO needs docs or a blog under the main domain.
- Model the CMS for year two. Count the content types you will have in two years against 40 collections and 10 reference fields, and decide which come from the product through the API.
- Check procurement early. If your buyers' security teams will ask about SSO for editors or SOC 2, price Enterprise before you commit.
We have built more than 20 Webflow sites in twelve months as a white-label partner to Web Tonic, at two to three weeks each, and we run marketing sites on a four-week process. We quote each SaaS build per project, because a ten-page launch site and a resource centre fed by product data are different jobs. Our Webflow development service page explains how we scope it.
