Webflow goes further than people think.

It handles large sites. The biggest one we run is a senior living community with around 100 pages across five CMS collections, covering articles, events, residences and more, with a 70-post publishing program the client’s own team maintains. Webflow’s enterprise tier adds SSO and SCIM provisioning, SOC 2 Type II and ISO 27001, page branching, and shared component libraries across multiple sites. The ceiling most people have in mind is the ceiling of how their site was set up. It is not the ceiling of the platform.

Choose Webflow if your marketing team needs to publish without a developer and your content is a set of related collections. Choose WordPress if you need server-side logic, user accounts and permissions, or a data model that outgrows collections. We build both, so the recommendation does not depend on what we would rather sell you.

When the application owns its own data. If the site needs accounts, permissions, or records that users create and edit, Webflow is the wrong layer and we will say so before the build instead of after. Same goes for a real storefront, which belongs on Shopify, and for gated member areas.

It is driven by structure rather than size, which is why two sites that look the same size can be priced very differently. What moves it is the number of CMS collections and the integrations, not the page count. A 100-page site built from five well-modeled collections costs less than a 20-page site where every page is bespoke. Taking over an existing site starts with an audit.

Six to ten weeks for a build, one to two weeks for an audit of an existing site. What drives the range is how many CMS collections the site needs and whether the content for them exists yet.

You do, from day one. We set up the Webflow workspace in your name at the start of the project and work inside it as invited collaborators. Your card is on the plan, not ours. If you stop working with us, nothing has to move: we leave, the site stays exactly where it is.

You pay Webflow directly for hosting and the CMS plan. We do not mark it up or bill it through. Beyond that, the running cost is whatever support you want from us. Webflow sites go on the same support plans as everything else we build, and with no core to patch and no plugins to update, that work is changes and improvements instead of maintenance.

Yes, and it starts with an audit. We go through the class structure, the CMS collections, the interactions and any custom code, then tell you what you actually have: what is reusable, what has to be rebuilt, and what each path costs. We did exactly this for a martial arts school whose previous site had been compromised by malware. The replacement went live fast because the audit came first.

Yes. Indigo Yoga Studios syncs its class schedule from Mindbody in real time. Elite Sound Events routes enquiries straight into its CRM. Where the site has to talk to a booking system, a CRM or a scheduler, that work runs alongside the build instead of being bolted on after launch.

Yes, with real work. Your content exports as CSV from the CMS. Your design does not, so a move means rebuilding the front end on the new platform. We structure collections so the export comes out clean, which makes the move a rebuild instead of a retype. Anyone who tells you a Webflow site ports over is selling you something.

Yes, if you have a marketer. That is the honest version. The Ohio Eastern Star Home publishes around 70 articles plus events and residence pages without us touching the site, because somebody there owns that job. If nobody on your team owns the website, no platform fixes it, and you would be better served by a support plan than by a promise about self-service.

We build to WCAG 2.2 AA as a matter of course — semantic markup, keyboard-operable components, visible focus states and real contrast — because retrofitting those into a finished site costs several times what building them in does. Where you need the work evidenced rather than assumed, for a procurement review or a demand letter, that is a full ADA compliance and accessibility audit, and it is its own engagement.

Buy a template if the site is five pages and will stay five pages. The cost shows up later. A template arrives with a class structure built for someone else’s content, so the first time you need a page it was not designed for, you either fight it or rebuild it. In-house works if the person doing it has done it before. Webflow is visual, but class naming and CMS modeling are architecture, and the sites we get asked to take over are almost always the ones where that part got skipped.