WordPress runs an enormous share of the web, and it earned that. It is genuinely good software, it is free, and a well-maintained WordPress site will beat a neglected custom one every day of the week. If you came here for a hit piece, this isn't one.
But there's a real problem for anyone shopping for a website right now: almost every studio says “custom design,” and the word covers two completely different things. One means somebody picked a theme, installed a page builder, and arranged your content inside it. The other means somebody wrote the code. Both are honest uses of the word. They produce different websites, they cost different amounts to keep running, and you usually can't tell which one you're buying from the sales page.
Here's how to tell the difference, and how to decide which one you actually want.
When WordPress is genuinely the right call#
Starting here, because it's the honest part and because it's true more often than a custom studio likes to admit. If most of these describe you, hire a good WordPress developer and don't look back:
Choose WordPress if…
- You want to log in and edit pages yourself, regularly, without emailing anyone
- You need a big off-the-shelf feature — a full store, memberships, course delivery, event ticketing — where a mature plugin does in an afternoon what custom work does in a fortnight
- Your budget is meaningfully under $1,900, because a half-built custom site helps nobody
- You publish constantly — several posts a week — and the editing experience matters more to you than the front end
- You already have a WordPress site that loads well and somebody who genuinely keeps it updated — there's no prize for switching
Those are five real ways this decision goes the other way, and we'd rather you heard them from us. What's not on the list is the one most people expect to be — that a custom-coded site traps you with whoever built it. We'll come back to that, because it used to be true and it isn't anymore.
What each one is actually made of#
This is the part nobody explains, and it's where every practical difference comes from. A page-builder site is an assembly: WordPress core, a theme, a page builder, and typically fifteen to thirty plugins, each written by a different company, each on its own release schedule. A custom site is pages of HTML that a browser downloads.
| WordPress + page builder | Written from scratch | |
|---|---|---|
| What's running it | Core, a theme, a builder, 15–30 plugins | HTML, CSS and a little JavaScript |
| How far the design can go | As far as the theme and builder can express | As far as it can be drawn |
| What a visitor downloads | The builder's framework whether the page uses it or not | The page, and nothing else |
| Ways in for an attacker | A login page, a database, and every plugin's code | No login, no database, and only the forms we wrote |
| To keep it safe | Apply updates forever, and check nothing broke — your job | Update a handful of packages — our job |
| Yearly licences | Builder, theme, SEO and cache plugins, most renewing annually | None |
| When one part breaks | The page it was on breaks, often silently | A bad update fails our build, so it never reaches your page |
| Editing text yourself | Log in and type — genuinely good | Send it to us; edits are included in Care |
The tell on a studio's price list#
You don't need to read anyone's code to work out how they build. Look at what they sell alongside the website, because a price list quietly describes the thing it's attached to.
If a studio sells a speed optimisation package as a separate paid service, ask the obvious question: why isn't the website fast when you hand it over? If they sell a schema markup retrofit, ask why the structured data wasn't there at launch. Those services exist, and they're honest work — but they're only products if the normal build reliably comes out slow and structurally thin. On a hand-built site they aren't services you buy later. They're Tuesday.
A speed package is only a product if the thing you built isn't fast.
Three questions worth asking anyone quoting you, in any order, and none of them hostile:
“What will this site be built on?”
A straight answer is a good sign either way. “Custom design” is not an answer to this question — ask again until you hear the name of a thing.
“What happens if I don't buy the care plan?”
On an assembled site, the honest answer is that it slowly becomes unsafe. On a static site, the honest answer is that it keeps working and you lose the backups, monitoring and someone to call.
“What am I still paying for in year two?”
Ask specifically about plugin and theme licences. They renew, they renew in your name, and they're easy to leave out of a first-year quote.
The objection that used to be true#
Here's the one we'd raise if we were you. WordPress is everywhere, so any developer on earth can take over your site. A custom-coded site sounds like the opposite — one studio's private handiwork, and you're stuck with them for as long as you own it.
That worry earned its keep once, back when “custom” often meant a system somebody invented themselves and only they understood. It doesn't describe how websites get written now. Ours are built on Next.js and React — not a private system but two of the most widely used tools in web development, with more people working in them than in any page builder — and the whole thing lives in a code repository in your name. Another developer clones it and it deploys on any modern host. Ask for exactly that in writing from whoever you hire, custom or WordPress, because it's the part actually worth checking.
It's worth knowing which way this one cuts, too. A repository is a thing a developer can read — every decision about your site is written down in it, in order. An assembled site keeps half its decisions inside thirty plugin settings screens and a database, where they can only be found by clicking. Handing that over is the harder job, and it's the one that usually comes with a folder of logins nobody has tested.
Which moves the question to a better one. If either kind of site can be handed to somebody else, what are you really choosing between? Two things, and neither is lock-in. How far the design can go: a page builder can only make the shapes it was built to make, so “custom” inside one means custom within its range — and when your site's job is to look like nobody else's, that range is the ceiling. Written code doesn't have one. And what you're left holding: a WordPress site is genuinely yours too, but it stays a working site because somebody keeps paying attention to it — updates applied, licences renewed, breakages caught. A written one is yours the way a finished thing is yours. Leave it alone for two years and it's still there, still fast, still safe, and still in your name.
A page builder can only make the shapes it was built to make.
So which should you buy?#
One question decides it: do you want to edit this website yourself, or do you want it to be excellent and left alone? If it's the first, WordPress is probably the better buy and we'll tell you so on the call. If it's the second — if the site's job is to make a stranger comparing three companies pick yours — then every gram of weight, every second of load time and every plugin that might break on a Saturday is working against you, and there's no reason to carry any of it.