Web design · Webflow
Webflow sitesa marketer can ship.
Components and CMS collections for a marketing site. Hosting stays on Webflow so the editor still works.
The short answer
When Webflow is the marketing site.
Webflow is the right build when a marketing team wants to design and publish in one place, and the site is pages, landing pages, and a modest CMS. Case studies, articles, and events fit. A large catalog, membership logic, or a product application does not. We leave the site on Webflow hosting so editors keep the CMS. Exporting a static copy and calling it the handoff throws away the reason you chose the tool.
Marketing sites
Visual control with a ceiling you should respect.
Webflow fits a company site, a campaign hub, or a hospitality brand that updates pages often and does not need a plugin ecosystem. Designers can work in the project. Marketers can work in the Editor if we build components that accept content instead of one-off styles. The ceiling is real: complex filtering, large relational content, and checkout are not what the tool is for.
Choose something else when engineers must own routing, auth, or a shared design system with an app. That is often Next.js. Choose WordPress when you need a deep editorial model, many roles, and hosting you can move. Webflow is a decision about who edits, not a logo on the footer.
- The site is marketing pages plus a CMS of repeating items.
- Someone on the team will have an Editor or Designer seat after launch.
- You do not need a storefront as the core of the same project.
Components and CMS
Collections for anything you will publish twice.
Repeating pages become CMS items: articles, case studies, locations, jobs. The template binds the fields, including the title and the summary, so a new item cannot ship as a blank frame. Static pages are for the few layouts that will not repeat. If a 'static' page is really a campaign you will clone, it should have been a collection.
Components get properties and variants. A hero is not restyled by hand on twelve pages. Interactions stay light enough that the content is readable if they do not run. Staging uses a password. The redirect list lives in the project, and we treat it as part of the build, not a chore for the week after launch.
- CMS fields required for the things the template must show.
- Components with a small set of variants, named in the project.
- Editor access tested by the person who will publish.
What breaks the CMS
A drawing someone has to unpick later.
The failure mode is a beautiful page built as a one-off, then duplicated until the project is a pile of detached styles. The Editor cannot change the headline without breaking the layout, so every request comes back to the Designer seat. You paid for a CMS and then built a poster.
The other failure is handing over a static export, or leaving the staging subdomain public. Editors lose the CMS in the first case. The second indexes a copy of the site. We also see class names that only the original designer understands. The project needs a short map of components, collections, and who may publish.
- No detached styles as the way a landing page gets made.
- No static export as the handoff if the team must keep editing.
- No public staging subdomain.
Editor test
A marketer publishes a CMS item unaided.
Before launch, the person who will own the site creates a CMS item, sets the slug, and publishes it to staging. We watch where they get stuck. If the template required a Designer for a normal field, we fix the component. A training call that nobody can repeat the next week does not count.
We also check that staging is blocked, redirects resolve, and the primary templates have one heading structure. Speed matters on the marketing pages ads will use. A launch review that only opens the homepage on a fast office connection is incomplete.
- A CMS item published by your marketer on staging.
- Staging blocked from indexing.
- Redirects checked against the old URL list.
Example engagement
A B2B software company that could not ship a page.
B2B software company, marketing site in Webflow, product app elsewhere. Every landing page had been copied from the homepage and unlinked from the symbols. The marketer had an Editor seat and still filed a ticket for a headline change, because the text was baked into a component with no property.
We rebuilt the repeating sections as components with a few variants and moved case studies into a CMS collection. The planned window for a marketing site of this shape is 8 to 12 weeks. The marketer published a case study on staging without a designer in the file. The product app stayed on its own stack. This project did not pretend to be the application.
8 to 12 wk
Planned window for the marketing site, not the product app
CMS
Case studies became collection items with bound fields
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
Webflow questions.
Can we host the export on our own server?
You can, and then you lose CMS editing, forms, and the redirect tool unless you rebuild them. If the team must publish without a developer, stay on Webflow hosting. Export is for a special constraint, and we will name what you give up.
Will the site handle a large resource library?
A few hundred CMS items with a simple template is comfortable. A filterable database with many references is the point where we should talk about a different stack. We would rather say that in scoping than after the design is done.
Who needs a paid seat?
The people who design need a Designer seat. The people who only publish CMS items and page copy can use the Editor. We set that split on purpose so you are not buying design access for the whole company.
Can Webflow run our store?
Not as the system of record for a real catalog. A simple embed or a link to a store on another platform is sometimes enough. Checkout, inventory, and tax belong on a store platform. We will not fake a store inside a marketing site.
Do you lock the client out of the project?
No. You should own the project and the hosting. We keep access as editors or designers while we are building, and the handoff includes the component map. A site you cannot log into is not finished.
More in this lane
Other Web Design platforms.
Talk through webflow.
One conversation. A diagnostic. A plan you can kill if it is not the work.