It's the question we get more than any other on the discovery call: "Should we build this in WordPress, Webflow, or have you build it custom?" The right answer is rarely the cheapest. It's almost never the trendiest. And it's usually different from what the same business would have picked three years earlier.
This piece is the long version of an answer we keep giving in 30-minute slices. We've shipped client sites on all three platforms — including a few that we later migrated off when the original choice stopped fitting. Here's the honest comparison, including the costs nobody discloses upfront.
The two-paragraph version
If you only read this far: WordPress is the right call for content-heavy sites where non-technical editors will publish weekly and you need the broadest plugin ecosystem on earth. Webflow is the right call when design polish matters more than logic, when your team has a designer-led culture, and when paying a platform fee in exchange for not maintaining infrastructure is worth it. Bespoke is the right call when you have logic the platforms can't model, when long-term platform fees would exceed the cost of building once, or when you need to differentiate on something that can't come out of a template.
The mistake we see most often isn't picking the "wrong" platform. It's picking based on year-one budgets when the decision is really a year-three commitment.
1. WordPress
What it does well
WordPress still runs about 43% of the web in 2026 — and the criticisms in the discourse haven't actually killed it. The plugin ecosystem is genuinely without rival: whatever you need, someone has built it, often three someones. Content management for non-technical editors is the best in class. SEO control through Yoast or Rank Math is mature, predictable, and well-documented. If your business publishes content as part of how it operates, WordPress is hard to beat.
Where it gets you
The pain emerges around year two. Plugin updates conflict. A "Pro" plugin you bought three years ago becomes a subscription, then a higher-tier subscription, then quietly stops being maintained. Page weight creeps up because every plugin loads its own CSS and JavaScript. Security patches arrive constantly and someone has to apply them or you'll be hacked.
None of this is a deal-breaker if you've planned for it. With disciplined plugin choice (we recommend keeping the count under ten), managed hosting that handles patching automatically (Kinsta, WP Engine, or Pressable), and a custom theme built specifically for your site rather than a generic ThemeForest purchase, WordPress will run for a decade. Without that discipline, you're paying maintenance debt that compounds.
Three-year total cost (typical)
- Year 1: £1,500 – £4,000 build · £150 – £400 hosting · £200 – £600 plugin licences
- Year 2: £200 – £600 maintenance retainer · platform costs flat
- Year 3: £200 – £800 maintenance · plugin renewals creep up · possibly £500 – £1,500 to fix accumulated technical debt
2. Webflow
What it does well
Webflow is what design-first teams reach for when they don't want to maintain WordPress and don't want to commission bespoke. It produces clean, fast, accessible HTML out of a visual designer. The animations and interactions are genuinely best-in-class — the kind of work that takes serious developer hours to replicate elsewhere. Hosting is built in, fast, and handles SSL, CDN, and forms without thought. The CMS is reasonable for editorial content.
Where it gets you
Vendor lock-in is real, even though Webflow lets you export static HTML. The CMS data, forms, e-commerce, memberships, and hosting are all proprietary. If you decide to leave, you'll be rebuilding most of the dynamic side of your site from scratch on whatever you migrate to.
Pricing is the other surprise. The site plan is fine. Then you add a CMS plan because you want a blog. Then traffic grows and you need the next tier. Then you add a team seat for a designer. Then you turn on Logic for some forms. Then you add e-commerce. We've seen Webflow bills go from £20 a month at launch to £280 a month two years later — not because the customer was misled, but because each individual upgrade made sense in isolation.
Webflow also has a hard ceiling. If your idea is "we want bookings with custom logic, integrated with our CRM, and a dashboard for staff" — Webflow will fight you the whole way. The right answer at that point is bespoke, not a more expensive Webflow plan.
Three-year total cost (typical)
- Year 1: £2,500 – £7,000 build · £20 – £100/month platform fees
- Year 2: £40 – £150/month as you add CMS items, team seats, traffic
- Year 3: £80 – £300/month if e-commerce or memberships are involved · maintenance is genuinely minimal but the bill is permanent
3. Bespoke
What it does well
Bespoke is what you build when the brief includes logic the platforms can't model. Bookings with conditional pricing. Login areas with role-based dashboards. AI features. Payments with custom flows. Multi-tenant architectures. Anything where the website does something beyond "tell people about us and let them get in touch."
The advantages compound: you own the code, you own the data, hosting costs are typically £8 – £25 a month for years, you can add features at the cost of development time rather than platform tier upgrades, and performance is whatever you want it to be (we routinely ship bespoke sites at sub-1-second Time to Interactive that no CMS could match).
Counter-intuitively, bespoke often ends up cheaper over five years than Webflow for any site with serious dynamic features. The catch is that the cost is concentrated in year one.
Where it gets you
Two real risks. First, dependency on the developer. If your custom site is built by a freelancer who disappears, you're potentially stuck. The mitigation is: pick an agency or studio with continuity (or a sole developer with a well-documented codebase and an explicit handover plan). Second, you have to actually maintain it. Bespoke isn't zero-maintenance — frameworks need updating, dependencies have security patches, browser features change. Plan for ~£500 – £2,000 of maintenance work per year on a non-trivial site.
Three-year total cost (typical)
- Year 1: £3,000 – £25,000 build · £150 – £300 hosting
- Year 2: £150 – £300 hosting · £500 – £2,000 feature additions and maintenance
- Year 3: hosting flat · feature additions on demand
The hidden costs nobody mentions until year three
This is the section nobody puts in their pricing page:
Plugin debt (WordPress)
Every plugin you add is a future security patch, a possible conflict, and a vendor relationship. Plugins get sold to new owners who turn them subscription-only. The sites with thirty plugins are the sites that "feel slow" and "keep breaking."
Tier creep (Webflow)
Webflow's pricing is stair-stepped. Each individual stair is reasonable. The cumulative climb over three years is what catches people out.
Bus factor (bespoke)
If your bespoke site was built by a single freelancer and they disappear, the next developer has to read the codebase before they can change a button colour. Mitigation: documented code, written-up architecture, named technologies a successor will recognise.
SEO debt (all three)
Every platform makes it easy to start with okay SEO and hard to fix it later. By year three you have backlinks pointing at URLs you can't easily change, structured-data markup that's drifted from current spec, and Core Web Vitals that have quietly degraded. Plan for an SEO audit and tune-up roughly every 18 months regardless of platform.
Migration cost
Whichever you pick, statistically you will migrate off it within five to seven years. WordPress to Webflow, Webflow to bespoke, bespoke to whatever ships next. Migrations cost £2,000 – £15,000 depending on size. Building with a clean separation between content and presentation makes migration cheaper later.
A decision framework
Five questions, in order. The first one with a "yes" answer points to your platform.
- Will the site need to do anything beyond display content and collect form submissions? If yes, you're heading for bespoke. Stop here.
- Is the team that will run the site designer-led, with no developer in-house? If yes, lean Webflow.
- Will non-technical editors publish content weekly or more often? If yes, lean WordPress.
- Is page-load performance a competitive differentiator (e.g. you sell to performance-conscious buyers)? If yes, lean bespoke.
- Is your three-year horizon predictable enough to lock into a platform's pricing trajectory? If "yes, predictable" — Webflow or WordPress are fine. If "no, we're going to evolve a lot" — bespoke gives you the most headroom.
What we'd do, by use case
- Solo professional / consultant brochure site — WordPress with a clean theme. Five plugins max. £600 a year all-in.
- Design-led agency or product brand — Webflow. The animations and polish will pay for the platform fee through pitches alone.
- SaaS marketing site (homepage + features + pricing + blog) — Webflow if you have a designer in-house, bespoke (Next.js) if you have an engineer.
- Booking platform / marketplace / multi-tenant SaaS — Bespoke. Anything else fights you.
- E-commerce shop (under 100 SKUs) — Shopify (we didn't include this in the comparison, but it deserves a mention). Don't try to make WordPress do this; don't try to make bespoke do this from scratch unless e-commerce is your differentiator.
- Content-heavy publication or knowledge base — WordPress with a custom theme.
- Healthcare, finance, or legal where compliance matters — Bespoke. The audit trail matters and platforms make it harder.
If you're trying to make this decision for a specific project and want a one-call sanity check, we offer free 30-minute consultations — no commitment, no upsell. Email support@monexapps.com or visit monexapps.com and we'll talk through the right call for your year-three self.
For more on what bespoke actually costs in 2026, see our Buyer Guide. For an example of what we built when bespoke was the right answer, see the Railo case study.