WordPress runs an enormous share of the web, which means two things at once: it is genuinely good at what it does, and it is also the default answer people give without thinking about the question.
Here is the comparison without a thumb on either scale.
What WordPress is genuinely good at
- Editing your own content. This is the real reason to choose it. Adding a page or a post needs no developer, and the editor is familiar to a lot of people.
- Publishing regularly. If you are running a blog or news section with any seriousness, WordPress is built for exactly that.
- Not being stuck. Lots of people can work on WordPress. If we disappeared tomorrow you could hand it to somebody else on Monday, which is a real form of insurance.
- Having been solved already. Events, bookings, memberships, online shops: whatever you need, something exists.
What it costs you, and people underestimate
Maintenance is not optional
WordPress and every plugin on it update constantly, largely for security. Unmaintained installs get compromised, not because somebody targeted you, but because automated scanners find them. This is ongoing work forever, and it is the cost people forget when comparing quotes. See what maintenance actually covers.
Plugins are other people's code
Each one is a dependency you did not write, running on your site. They conflict, they get abandoned, and occasionally one is the way in. A site with thirty plugins is carrying thirty small risks and usually a lot of weight.
Speed takes effort
A plain WordPress site is quick. One with a page builder, a slider, a big theme and a stack of plugins often is not, and speed affects both what visitors do and how you rank. It is fixable, but it is work rather than a default.
The editor can undo the design
Give somebody a page builder and eventually a page appears with four fonts and inconsistent spacing. Not a criticism of anyone; it is what happens when a tool offers unlimited freedom and no guardrails.
When a custom build makes more sense
- The site is mostly fixed. If content changes a few times a year, you are paying the maintenance overhead of a publishing system to publish nothing.
- Speed genuinely matters. A hand-built site has nothing loaded that is not needed.
- The requirement is unusual. Once the thing you need does not exist as a plugin, you are writing software anyway.
- You want a smaller surface. Fewer moving parts is fewer things that can break or be exploited.
The middle ground most people actually want
The framing above is a bit false, because the real choice is usually not "WordPress with everything" versus "custom everything".
A modern WordPress block theme is far closer to a hand-built site than the plugin-stacked installs that gave the platform its reputation. The layouts are defined properly, styling comes from a theme file rather than from whatever a page builder emitted, and you still get the editor. Fewer dependencies, most of the benefit.
That is why our own template line ships each design twice: once as hand-built HTML for sites that do not need a CMS, once as a WordPress block theme for the ones that do. Both are generated from the same token file, so choosing one does not mean a different-looking website. It is a decision about how you will maintain it, not about how it looks.
How to actually decide
One question: who is going to change this site, and how often?
If the answer is "us, regularly": WordPress, kept lean. If it is "almost never, and we will ring someone": a hand-built site will be faster, safer and cheaper to run. If it is "it needs to do something, not just say something": that is a third conversation and neither answer fits.
Whichever way you go, budget for maintenance. A website is not a thing you buy once. See what a site really costs, running included.
Tell us how you expect to use it and we will tell you which we would build, and why, including the times the answer is the cheaper one.