Webflow vs Framer, and the sites that should use neither

en 2026-09-25 7 min read

If you are one person putting a marketing site online and you want to keep editing it yourself, use Framer. If the site has more than a handful of pages, structured content and a team who will maintain it after launch, use Webflow. If the site needs more than a builder gives you, a coded build from us lands at step 02, EUR 900 to 1.500, two to three weeks, or step 03, EUR 1.500 to 3.500, three to six weeks, depending on how many pages there really are.

Build it yourself first, and we mean that

Both tools were made for people who do not write code, and both succeed at it. If you have reasonable taste and the patience to learn one interface, you can put a good site online in Framer and pay nothing beyond the subscription.

What you would be paying a studio for is not the tool. It is deciding what each page says, in what order, and what you want the reader to do at the end of it. If that is written down already, the build is the easy half. If not, paying someone to operate a builder buys a prettier version of the same problem.

What Framer does well

Framer gets you from a blank canvas to a live site quickly, and its defaults are good. Motion, transitions and scroll effects are part of the tool rather than bolted on, so a Framer site can feel considered without anyone hand-writing animation. It has a content system for a blog or a case study list, and hosting is included.

The limits arrive later. Control over the underlying styling is looser than Webflow's, there is no code export, and content models beyond a simple list get awkward. A large multi-language site is a stretch rather than a strength.

What Webflow does well

Webflow is close to real CSS with a visual interface on top. Classes, the box model, the cascade: if you understand how the web renders, you can build what you can draw, and the output is predictable. Its content system handles structured collections that reference each other, which suits services, locations and team pages that link together. Localization, redirects, form handling and a restricted editor role for the client are all there.

The cost is the learning curve, and it is a real one. Class naming rots fast in untidy hands, and a neglected Webflow project becomes a liability the next person quotes to rebuild rather than fix.

Side by side

Sites that should use neither

Sometimes a builder is the wrong category of tool altogether.

• Anything with a login. Accounts, dashboards, per-customer data, a members area. That is step 04, EUR 3.500 to 7.500, six to twelve weeks.
• A real shop. Payments, tax rules, stock, invoices and returns belong on a shop platform, and that build also sits at step 04 rather than on a page builder bent into the shape of a store.
• Hundreds of pages generated from data. A catalogue, a directory, a location matrix. Builders creak, then break.
• Deep integration. A CRM, a booking system, an ERP, or an API that must stay in sync both ways.
• Anything you must own outright. A builder site lives inside the builder. Stop the subscription and the site goes offline.

When one of those describes your project, the answer is a coded site. That is what design and engineering covers, and the technical route is written up on our Next.js page.

What ownership actually means here

A Webflow or Framer site is a tenancy: your work sits in their project, and staying online depends on a subscription you keep paying. That is a fair trade for a small marketing site and a poor one for something your business depends on. When we build a coded site, you own the code, the repository and the database. We can host it, agreed per project, and because the code is yours it can be moved.

What it costs to have it built

Two things continue after launch if you want them. Care, EUR 100 to 300 a month, covers updates, monitoring, backups and small fixes, not a redesign and not new features. SEO growth, EUR 500 to 800 a month, is continuing search work. SEO foundation is not one of them: it is a one-off, EUR 450 to 750. Everything is listed on the price list, and a fixed quote follows scoping.

How the work runs

1. Scope and page map, then a fixed quote.
2. Words and structure before visuals, because a layout designed around placeholder text collapses when the real text arrives.
3. Design, then build in code.
4. Review on real devices, then launch and a walkthrough of how you edit it.

The stage that waits on you is copy approval and photography. The timelines above assume you answer while the work is warm.

When to spend less

If you need one page and a form, build it in Framer yourself. It costs less than any invoice we could send.

If your current site works and simply looks dated, ask for design work on what exists rather than a rebuild. Rebuilding a site that already converts risks losing the parts quietly doing the work.

And if the real problem is that nobody finds you, no builder fixes that. SEO foundation at EUR 450 to 750, bought once, tells you whether your pages are even indexed before you pay for a new design. If one of those is your situation, do not buy a new build yet.

Common questions

Can I move a Framer site to Webflow later, or the other way round?

Not as a migration. Layout, styling and interactions are rebuilt by hand, and only text and images carry over. Pick the one that suits how the site will be maintained, because switching means paying for the build again.

Will a site built in a visual builder rank in Google?

Yes. Both output clean HTML and let you set titles, descriptions, redirects and a sitemap, and neither is penalised for being a builder. What decides your ranking is what the pages say, how the site is structured, and who links to you.

Can you build it in Framer or Webflow for us?

We build in code, so what you get is a repository rather than a builder account. If a builder suits the site better, we say so during scoping, and you can build it yourself or hire someone who works in that tool. On a coded build, Care at EUR 100 to 300 a month covers updates, monitoring, backups and small fixes.

Should we just buy a template?

For a small site with a straightforward message, a good template edited carefully is a sensible purchase. It stops making sense when your content does not fit the shape the template assumes.

What happens when we outgrow the builder?

You rebuild. A builder site that carried you to the point where you need logins, integrations or a catalogue has already paid for itself. The rebuild is step 04, EUR 3.500 to 7.500, six to twelve weeks, and the words and structure you refined all come with you.

If you want a straight opinion on which of these your project needs, send us the site you have now and the one you want.