“Webflow or WordPress?” is the platform question UK small businesses ask most often, and it is usually the wrong question. Both are tools, and both come with the same underlying decision hiding behind the logos: who owns the site, who can change it, and what does it cost you — in money and in time — to keep it running.
This is an honest comparison from someone who builds neither by default. I work in Astro, Next.js, Webflow and Sanity, and we steer clients away from WordPress for reasons set out below. The useful answer is not a favourite, it is a test: match the platform to what you need to own and run.
What WordPress is genuinely good at
It is dishonest to dismiss WordPress. It powers a huge share of the web for real reasons.
- It is everywhere. A very large number of developers and agencies know it, so you are rarely stuck for help.
- The plugin ecosystem is unmatched. Whatever feature you want, someone has built it, usually cheaply.
- It is open source. You can host it yourself and, in principle, take it anywhere.
- It is cheap to start. A theme and a host can put a site online for very little.
For a brochure site that rarely changes, run by someone who enjoys tinkering, that can be a perfectly rational choice.
Where WordPress fails a small business that is serious about growth
The problems are not that WordPress is bad software. They are that running it well is a job, and the responsibility for that job lands on you.
- Maintenance is permanent. Core, themes and plugins all update, and updates break things. Someone has to apply them, test them and fix what they break. For most small businesses that someone is either a monthly bill or an owner’s weekend.
- Plugins become dependencies. The feature you rely on is often a plugin maintained by a stranger. When it is abandoned, or its licence changes, you inherit the problem. We wrote about this in When the Platform Removes Something You Depend On.
- Security is your problem. The popularity that makes WordPress well-supported also makes it the most-attacked platform on the web. Keeping it patched is not optional.
- Speed needs work. A WordPress site is fast only after caching, image and hosting work that a theme does not do for you.
- It is a time sink. This is the honest reason we stay away. For an SME serious about growth, the hours and the ongoing spend that WordPress demands are usually better spent on the business. It is not the right tool for that job.
None of this means WordPress cannot work. It means WordPress is a project you keep running, and most small businesses did not ask for a second job.
What Webflow is genuinely good at
- Design freedom with no code. A designer can build exactly the layout they want without a developer, which is why it is popular with studios.
- No maintenance. Webflow hosts, patches and scales for you; there are no plugins to update.
- Fast out of the box. Performance is good without the caching archaeology WordPress needs.
- A capable CMS. For blogs, collections and structured content it is more than enough.
For a marketing site with a clear shape and someone who wants to edit it, Webflow is a strong product.
Where Webflow fails the ownership test
Webflow’s trade-off is the opposite of WordPress’s. Where WordPress asks for your time, Webflow asks for your exit.
- Hosting is tied to the platform. You cannot take a Webflow site and host it elsewhere. The site lives where Webflow says it lives.
- The content export is not a working site. You can export the HTML and CMS content, but what you get is a static snapshot, not the tool that ran it.
- Costs scale with success. More CMS items, more traffic, more collaborators — the bill moves up, and you do not have the option to move it down by leaving.
- The more bespoke the build, the harder the exit. Custom interactions and logic make the site less portable, not more.
This is the Rented Ground point in one sentence: with Webflow you are renting a very good workshop. The Exit Test is a ten-point audit for whether you could leave your platform tomorrow — most Webflow sites fail it.
The third option neither camp mentions
The comparison is usually framed as a binary, which suits both vendors. There is a third route: a site built on a codebase and a CMS you own, hosted where you choose. That is the stack we build on — Astro or Next.js for the site, a headless CMS such as Sanity for the content — and it is not only for big companies.
- You own the code and the content. Both are yours, exportable, and hostable anywhere. The Exit Test passes by construction.
- No maintenance treadmill. A static or server-rendered site has no plugin stack to patch.
- Editing is not an afterthought. The CMS is chosen for what your team actually needs to change, and the pages are built around that.
- The cost is the build, not the rent. You pay for the work once; running costs stay low and predictable.
The trade-off is real: you need someone who can build it, and it is not a drag-and-drop canvas. That is the job. Builder, Headless, or Bespoke walks through the three shapes honestly, including when a platform is the sensible answer.
How to choose, in four questions
- What do you actually need to edit? If it is a handful of pages a year, almost anything works. If it is collections, products, areas, case studies or articles, choose for the CMS, not the canvas.
- How fast does it have to be, and stay? Both platforms can be fast; only one of them makes you keep it fast.
- What does it cost to run, and who raises the price? A subscription that scales with your success is a rent increase you did not negotiate.
- Could you leave? The single most useful test. If the answer is no, you are renting, whatever the invoice calls it.
On those four, WordPress loses on time, Webflow loses on exit, and an owned stack wins on both — at the cost of a proper build. For a business that wants to grow without acquiring a platform hobby, that is usually the right trade.
The honest verdict
Choose WordPress if you genuinely want to run a platform and enjoy the upkeep. Choose Webflow if you want a beautiful marketing site with no maintenance and accept that you will never take it with you. Choose an owned codebase and CMS if you want the site to be an asset you control, now and when you sell or move on.
What none of them excuse is skipping the research. The platform should be chosen to fit what your market searches for and what the site has to do, which is a decision that comes before the tool. GroundWork settles that; Build builds against it; Coverage keeps it visible once it is live.