WordPress or a custom website: how to choose

Almost every website project starts with the same question: should we use WordPress, or build something custom? Both are good answers to different problems. The mistake is choosing on habit or on price alone, so this guide gives you a way to decide on purpose, and to know when the honest answer is “it depends on one more thing”.

Start with what the site has to do

List the five most important things a visitor should be able to do on your site. If those are mostly reading, contacting you, booking a call, or browsing your services, a content-managed site covers it comfortably. If they involve logging in, calculating a quote, configuring a product, or interacting with live data, you are describing an application, and a template will fight you at every step.

A useful way to test this: write each requirement as a sentence starting with “A visitor can…”. Requirements that describe reading and sending a message point toward WordPress. Requirements that describe doing something with their own data point toward custom.

When WordPress is the right call

• Your site is primarily content: services, case studies, articles, landing pages.
• Non-technical people on your team need to edit pages without a developer.
• You want a proven ecosystem for forms, SEO tooling, and integrations.
• You need to launch in a sensible timeframe without a large build.
• Your budget is better spent on content and marketing than on bespoke engineering.

WordPress is easy to build badly, though. Heavy themes, plugin sprawl, and unreviewed updates are what give it a reputation for being slow and insecure. A lean, well-structured build avoids most of that: a purpose-built theme, a short list of carefully chosen plugins, and a sensible update routine.

When a custom website is worth it

• You need accounts, dashboards, portals, or workflows behind the site.
• The experience itself is part of the brand: interactive, animated, or highly specific.
• You rely on unusual integrations that a plugin cannot handle cleanly.
• Performance and structure matter enough that you want full control over both.
• The site is really a product, and will keep gaining features over several years.

Custom does not mean “no CMS”. A custom build can still give editors a friendly way to manage content; it is simply designed around your content model instead of adapted to a generic one.

What really drives cost and timeline

People often assume custom is always slower and more expensive. It usually is more work up front, but the bigger drivers of cost on either path are the same: how many distinct page types you need, how much content has to be written or migrated, how many integrations are involved, and how many rounds of review the project goes through.

• Page types: five distinct layouts cost far more than fifty pages that share one layout.
• Content readiness: a site waiting on copy and images stalls regardless of platform.
• Integrations: each CRM, payment, booking, or analytics connection adds design and testing.
• Decision speed: slow approvals extend any timeline more than any technology choice.

Maintenance, security and ownership

Whichever you choose, someone has to own what happens after launch. WordPress needs regular core, theme and plugin updates, backups, and monitoring. A custom site has no plugin ecosystem to keep patched, but it needs developer time for every change and a clear plan for hosting and dependencies.

Ask three questions before signing off on either: who applies updates, who is called if the site breaks, and what would it take to move to another developer? A good answer to the last one, with documentation and code you control, is a sign of a healthy engagement.

A hypothetical example

Imagine a regional services firm with twelve service pages, a team page, and a contact form. The marketing lead updates content weekly and wants no developer involvement. That is a WordPress project: clear structure, frequent edits, standard integrations.

Now imagine a training provider that needs learners to log in, track progress, and download certificates, alongside marketing pages. That is two things: a content site and an application. The sensible design is often a WordPress or similar marketing site for the public pages, with a custom application behind a login.

The questions that decide it

1. Who will update the site day to day, and how technical are they?
2. Will the site’s needs change significantly in the next two years?
3. Does any feature require data that changes per visitor?
4. What does it cost you if the site is slow, down, or hard to change?
5. Do you need the design to do something a theme cannot, rather than simply look different?

You can also mix the two, and you can start on one and move to the other. If you are unsure which side of the line your project sits on, a short discovery conversation, before any design or code, usually settles it quickly and saves far more than it costs.