Webflow

A Webflow website with a CMS your team can manage

Webflow is a website platform with a visual editor and a CMS built around collections, plus APIs for managing that content programmatically. It suits sites where a team regularly adds content. Your plan determines what is possible.

Discuss your website

Webflow centres on the CMS, and therefore on your plan

This page is for organisations where several people add content: news, case studies, vacancies, locations. The issue is often not the design but the content: it grows, and every new page needs to be as well structured as the first.

In Webflow, you work with collections: groups of items with the same fields and a shared template page. The number of collections and items you can use depends on your plan, and the Basic plan has no CMS. The plan is therefore a design decision, not an afterthought.

What we consider with Webflow

Four considerations that work differently in Webflow than on other platforms.

Collections and their limits

We design the collections and fields alongside the pages, then compare the expected number of items with your plan’s limit. This prevents you from running into a cap a year later.

Content through the API

Webflow has APIs that can bring content into the CMS from elsewhere, such as vacancies from another system. Those APIs have a limit on requests per minute for each plan; we account for this when volumes are high.

Ecommerce

Webflow has its own ecommerce plans with a limit on the number of products and variants. The basket and checkout can be designed. It suits a smaller shop within a Webflow site; we do not promise features that are not documented.

Web apps alongside the site

With Webflow Cloud, a web application, for example built with Next.js, can run alongside or under a path of your Webflow site. This lets a calculator or bespoke feature belong to the site without Webflow having to provide it itself.

Customer accounts are no longer available in Webflow

Webflow offered customer accounts under the name User Accounts, previously Memberships. Since 29 January 2026, this has no longer been available on any site, including through the API. Webflow points to third-party services.

If you need a member area or customer portal, this means using a third-party service or a bespoke web app alongside the site. If your current site still runs on the old accounts, a replacement is needed.

Three situations where Webflow is a strong fit

Possible applications, not completed commissions.

Job listings that update themselves

Problem

Vacancies sit in a recruitment system and are copied to the site by hand. A filled vacancy can remain online for weeks.

Solution

A Jobs collection in Webflow, populated from the recruitment system through its API. New vacancies appear and filled positions disappear.

Data involved

Job title, department, location, description, status and the link to the application form.

Value

The site shows what is genuinely open, without anyone having to remember it.

Depends on

Whether the recruitment system has an API, how many vacancies are live at once, and which Webflow plan is needed for that number of items.

A knowledge base maintained by a team

Problem

Five people write articles, but every article looks different and old ones cannot be found.

Solution

Collections for articles, topics and authors, with fixed fields and a template page, plus overviews for each topic.

Data involved

Articles, topics, authors, imagery and the references between them.

Value

Every new article fits the design and can be found through its topic.

Depends on

The expected number of articles in a few years, and who receives which permissions in the CMS.

A calculator that belongs with the site

Problem

Visitors want to know what something will cost or deliver for them, but the calculation is too complex for a simple form.

Solution

A small web app through Webflow Cloud, under a site path, that performs the calculation and appears in the same style.

Data involved

The visitor’s input, the calculation rules and, where needed, rates from another system.

Value

The calculator belongs with the site, without a separate environment that looks different.

Depends on

How complex the calculation rules are, whether data needs to be stored, and what Webflow Cloud requires for this.

Webflow suits a growing CMS, less so member areas

This is a good fit if

A team regularly adds content in consistent formats
Content also needs to come from other systems
You want to manage content visually, without code
A small shop or web app belongs alongside the site

This is less suitable if

You need customer accounts or a member area and do not want a third-party service
Your range is larger than the ecommerce plans allow
Your site rarely changes and does not need a CMS

If Webflow is not a fit, we consider WordPress for substantial content with independent hosting, Shopify for a larger shop, or a bespoke web app for a member area.

From content model to a site your team can manage

Content model. Which collections, which fields and how many items, now and in a few years. This determines the plan.
Design. Pages and template pages for every collection, on phone and desktop.
Build and CMS. The site in Webflow, the collections configured, and existing content migrated.
Integrations and web apps. Content through the API and, where needed, a web app through Webflow Cloud, tested with realistic volumes.
Permissions and handover. Who can do what in the CMS, guidance for the team, and an agreement on management.

What we need for a proposal

With Webflow, the content model determines both the proposal and the plan.

Which types of content you have, and roughly how many items of each
Who adds content, and how often
Whether content needs to come from other systems, and which ones
Whether visitors need to buy or sign in
Your current Webflow plan, if you already have a site
Only during the build: access to your Webflow workspace through your own account, which you add, never through your password

What a Webflow site costs depends on the content model

Figures are included in the proposal. These factors determine them.

Collections and items. The number of content types and items, and the plan they require.
Design. The number of pages and template pages with their own design.
Integrations. Content coming from other systems through the API.
Ecommerce or web app. A shop within Webflow, or a web app through Webflow Cloud.
Migration. Existing content that needs to fit into the new collections.

Recurring costs

The Webflow plan, including CMS
An ecommerce plan, if a shop is added
Third-party services, for example for customer accounts
Management and ongoing development as agreed

Questions about Webflow

Which Webflow plan do I need?

A plan with CMS as soon as you use collections; Basic does not include it. Which one you need depends on the number of items and collections, and on ecommerce. Webflow sometimes changes names and limits, so we confirm them when preparing the proposal.

My site still uses Webflow customer accounts. What now?

They have not been available since 29 January 2026. We discuss which third-party service or bespoke web app will take over the member area, and which data needs to move across.

Can my team create pages itself?

Adding and updating items in collections, yes. New types of pages outside collections require more knowledge of Webflow; we agree what your team will handle during handover.

Beyond Webflow

Website design. Webflow alongside other platforms, and how we choose.
API integrations. Content that enters your Webflow CMS from other systems.
Custom apps. A member area or feature that Webflow does not provide itself.

Tell us which content your team maintains

The types of content, how much of it there is, and whether it needs to come from other systems: this helps us define the content model and suitable plan.

Discuss your website