9 September 2026 / 7 min read
WordPress vs Webflow vs custom code: an honest comparison
Three routes to the same-looking website, and the running costs, ceilings and risks each one hands you afterwards.
- wordpress
- websites
- custom build
Every platform argument is really an argument about who edits the site in a year, and what happens when the site needs to do something the platform never planned for.
The short answer
Choose WordPress when content volume and editor familiarity matter most. Choose Webflow when a small marketing site needs to look sharp and be edited by a designer. Choose custom code when the site is doing real work — accounts, data, calculations, integrations — or when speed and control are the point.
Side by side
| WordPress | Webflow | Custom code | |
|---|---|---|---|
| Best at | Large content sites, blogs, structured listings | Marketing sites with strong visual control | Anything with logic, data or scale |
| Editing | Familiar to most teams | Designer-friendly, developer-light | Whatever we build for you |
| Running cost | Hosting plus plugin licences | Platform subscription per site | Hosting only, usually modest |
| Speed | Good if built lean; poor if plugin-stuffed | Good | Best — nothing to strip out |
| Ceiling | High with custom post types and fields | Reached quickly once logic is needed | Effectively none |
| Main risk | Plugin sprawl and maintenance debt | Platform lock-in and per-site fees | Needs a developer to extend |
What people get wrong about WordPress
WordPress is not slow. Badly built WordPress is slow. A custom-coded build using custom post types, custom fields and hand-written templates — the JetEngine and ACF approach — behaves like a proper content system rather than a pile of pages. What kills sites is twenty-six plugins doing the work a developer should have done.
What people get wrong about custom
Custom does not mean expensive or slow to deliver. Hand-written code alongside AI-assisted delivery compresses timelines significantly, and the result has no platform tax on it. What custom does mean is that changes come through a developer rather than a plugin marketplace.
Deciding in four questions
- Does the site mostly publish content, or does it do work?
- Who edits it weekly — a marketer, a designer, or nobody?
- Will it need accounts, payments, calculations or another system's data?
- What is the plan for the second phase?
Two or more "does work" answers and custom is usually cheaper across three years, even where it costs more up front.