We build websites in WordPress, and we build them from scratch in code. So when someone tells you one of them is always the right answer, be a little suspicious — they are usually selling you their preference, not solving your problem. The honest truth is that WordPress and a custom build are different tools for different jobs. The right choice depends entirely on what you are making and who will look after it once we hand it over. Here is how we actually decide.
what each one really is
WordPress is a content management system: you log in, edit your pages, publish a post, swap an image. Around it sits a huge ecosystem of themes and plugins that solve common problems out of the box. A custom build is the opposite philosophy — a site written specifically for you, with nothing in it that you did not ask for. For us that usually means React and Vite, the same stack behind this site. Neither is "better". They are good at different things.
a tale of two briefs
Picture a neighbourhood café that wants a warm site with its menu, story, opening hours and a booking button. That is solved ground: WordPress gets it live quickly, the owner can update the specials themselves, and not a single line of custom code is needed. Now picture a startup that wants a members' area where two kinds of user log in, see different things, and pay monthly. No plugin truly fits that, and bending one to fit usually costs more than building it properly. That is a custom job. Same studio, opposite recommendations — because the brief decides, not our mood.
when wordpress is the right call
- You want to edit it yourself, often, without phoning a developer every time a price or a paragraph changes.
- It's mostly pages, a blog and maybe a shop — well-trodden ground that thousands of sites have walked before.
- Budget matters and you want to be live quickly. WordPress gets you there for less, faster.
- A mature plugin already solves your need — bookings, payments, multilingual — and solves it well.
Most of the small-business sites in our work are WordPress, and that is a deliberate choice, not a compromise. For that job, it is the right tool, and pretending otherwise would just cost the client money.
when a custom build wins
- You're building a product, not a brochure — accounts, roles, logic, something that simply does not exist as a plugin.
- You care about craft — speed, motion, a brand that doesn't look like a theme half the internet also bought.
- It has to scale, integrate deeply, or do something genuinely yours.
Our own site is custom, written in React, because it had to feel like nobody else's. For that brief, a theme would never have cut it.
the trade-offs nobody mentions
WordPress is cheaper to start and easy to hand to a non-technical team — but plugins pile up over the years, and a neglected site gets heavy, slower and more exposed to security holes. Cheap to begin can quietly become expensive to maintain. A custom build costs more up front and frees you from all of that — it stays lean, fast and exactly yours, with no plugin ecosystem to be locked into — but you don't "log in and add a plugin"; when you need something new, you call your developer. The real comparison is never just the first invoice; it is the cost over three years, support included.
there's a middle, too
You don't always have to pick a side. A "headless" setup uses WordPress purely as the editor your team already knows, with a fast, custom front-end bolted on top — the easy writing experience of one, the speed and polish of the other. It costs more than plain WordPress and isn't worth it for a simple site, but for the right project it is a genuine third option, and we will raise it when it fits.
how to choose in one minute
Ask yourself four questions:
- Who edits the site day to day — you, or a developer?
- Is it a brochure, or a product with logic behind it?
- How much do speed, polish and a unique look really matter to you?
- What is the realistic budget over three years, maintenance included?
Your answers usually point clearly one way. We will point you to the option that fits how you will actually use the site — not the one that makes the project bigger for us. It is the same honesty we bring to whether you need an app or just a good website: the right tool is the one that quietly does the job. 👋
