WordPress or a Custom Website? How to Decide Before You Commit
A straight comparison of WordPress and a custom-built website for business use — what each one is genuinely good at, the costs people miss on both sides, and a simple way to decide.
Publishing content vs doing workFIG.01
Short answer
WordPress suits content-led sites that non-technical staff edit often — brochure sites, blogs and simple catalogues. A custom build suits sites where the interface does work rather than publishes: portals, dashboards, booking flows, anything driven by your own data. Decide by what the site does, not by the quoted price.
Key takeaways
- Pick by function: a site that publishes content leans WordPress, a site that performs work leans custom.
- WordPress's real cost is plugins — licences, conflicts and the updates someone has to keep applying.
- Most WordPress security and speed problems come from plugins and themes, not from WordPress itself.
- Both can rank well. SEO is not a legitimate reason to pick one over the other.
- If you are already describing user logins, roles and data views, you have stopped describing a website.
This question usually arrives already framed as a budget decision: WordPress is the cheap option, custom is the expensive one. That framing is what leads businesses to a site they outgrow in a year, or to a custom build they did not need. The useful question is different.
Does your site publish, or does it work?
A publishing site's job is to show content — pages, posts, services, case studies — and to let someone in marketing change that content without calling a developer. A working site's job is to do something: take a booking, quote a shipment, show a customer their orders, run a dashboard against your own database.
WordPress was built for the first job and is genuinely excellent at it. Everything it does for the second job, it does through plugins written by other people, which is where the trouble starts.
Where WordPress is the right choice
- Your team publishes regularly — blog posts, news, case studies — and wants to do it without a developer.
- The site is mostly standard pages: services, about, portfolio, contact.
- You need it live soon and the content matters more than the interaction.
- Budget is genuinely tight and the site's job is credibility, not operations.
A well-built WordPress site with a small number of quality plugins is a perfectly good business website, and choosing it is not a compromise. The failure mode is different: it is the site that started simple and now runs fourteen plugins to do things WordPress was never meant to do.
Where a custom build is the right choice
- Users log in and see different things depending on who they are.
- The site reads from or writes to your own systems — inventory, ERP, CRM, courier APIs.
- There is a workflow: a quote request that routes to someone, an approval, a status that changes.
- Performance is commercial, not cosmetic — a slow page directly costs you enquiries or orders.
- You expect the site to keep growing into a product rather than settling into a brochure.
| WordPress | Custom build | |
|---|---|---|
| Content editing | Excellent — built for it | Needs a CMS layer built in deliberately |
| Time to launch | Short | Longer, and phased |
| Upfront cost | Lower | Higher |
| Ongoing cost | Plugin licences, updates, occasional breakage | Hosting and support; no licence creep |
| Custom workflow | Plugin-dependent and fragile past a point | Built to your process |
| Integrations | Fine when a plugin exists, awkward when one does not | Built directly against the API |
| Performance ceiling | Limited by theme and plugin load | As fast as you are willing to engineer it |
| Security exposure | Large, because the plugin surface is large | Smaller, and entirely yours to manage |
| Who can maintain it | Almost any web developer | Anyone, if the code is documented and handed over |
The costs people miss on each side
On WordPress
Premium plugins and themes renew annually, and a site that quietly depends on six of them has a recurring bill nobody budgeted. Updates have to be applied, and occasionally one breaks a page — so somebody has to be responsible for checking. None of this is expensive individually; it is the accumulation that surprises people. Website maintenance after launch covers what this actually involves.
On a custom build
The upfront cost is visible, so it rarely surprises anyone. What does surprise people is that content editing has to be designed in. If nobody asks for it, you get a beautiful site where changing a heading needs a developer. Ask for the admin side explicitly. What a website costs breaks the numbers down further.
Speed and SEO
Both platforms can rank. Google measures the page it receives, not the technology that produced it, and its Core Web Vitals documentation describes those measurements in detail. A lean WordPress site beats a bloated custom one every time.
The practical difference is the ceiling. On WordPress you are optimising within the constraints of a theme and whatever the plugins load. On a custom build you control every byte the browser receives, which matters when performance is commercial rather than cosmetic — the argument in why website speed matters.
Security
WordPress core is maintained by a large team and patched quickly; the WordPress project publishes its security releases openly. The exposure comes from the ecosystem — an abandoned plugin with a vulnerability is on your site until someone notices.
A custom build has a smaller attack surface simply because there is less third-party code, but nothing is patched for you. Either way the basics are the same, and they are covered in business software security basics.
How to decide
Choosing between WordPress and a custom website
Write down what the site must do
Not the pages — the actions. "Customer checks order status" is an action. "Services page" is not.
Count how many of those actions need your own data
Zero or one, and WordPress will almost certainly do. Several, and you are building an application.
Ask who edits content, and how often
Daily edits by non-technical staff push toward WordPress, or toward a custom build with a proper admin area — but somebody has to pay for that admin area.
Price both honestly over three years
Include plugin renewals, hosting, maintenance and the developer time each option needs. The cheaper option upfront is not always the cheaper option.
Check the exit
Whichever you choose, confirm you own the hosting, the domain and the content export before work starts.
If you already have one and it is the wrong one
Moving between the two is routine, and the risk is not technical — it is the rankings you already have. Redirects, URL structure and content parity decide whether traffic survives the move, which is the subject of redesigning a website without losing SEO.
If you are unsure which side of the line your project sits on, describe what the site needs to do rather than what it should look like — send us that description and the answer is usually obvious within a conversation, including when the answer is WordPress.
Frequently asked questions
Is WordPress bad for SEO?
No. Google evaluates the page it receives, not the platform behind it. A fast, well-structured WordPress site outranks a slow custom one. Platform choice is not an SEO decision.
Can a custom website have a content editor like WordPress?
Yes, but only if it is designed in. Ask for it explicitly at the start, otherwise you end up needing a developer to change a paragraph.
We need an online store — does that change the answer?
It changes the shortlist. That decision is between WooCommerce, a hosted platform and a custom build, and it is covered separately in our comparison of Shopify, WooCommerce and custom builds.
How many plugins is too many?
There is no fixed number, but each one is code you did not write and must keep updated. If a plugin exists only to do something your theme should have done, that is the one to question.
Can we start on WordPress and move to custom later?
Yes, and for many businesses that is the sensible sequence. Keep your URL structure clean and your content exportable from day one so the move stays cheap.
/Services in this article
Keep reading
All articlesHow to Structure an Engineering Consultancy Website for Technical Buyers
A practical information architecture for multidisciplinary engineering firms: service taxonomy, project proof, regional pages and qualified consultation paths.
How a Logistics Website Turns Service Pages Into Quote Requests
A conversion-focused structure for freight and logistics websites: services, trade lanes, shipment proof and a quote form buyers can actually complete.
