If you need a new business website, one of the first questions is whether to build it on WordPress or have something custom built from scratch. For most business websites the answer is WordPress, done properly. For some it is not. Here is how to tell which you are.
What you are actually choosing between
WordPress is a content management system: a mature, widely used foundation that lets your own team edit pages, publish news and manage products without calling a developer. A fully custom build is software written specifically for your needs, with no pre-built foundation underneath.
The choice is rarely as stark as it sounds. A WordPress site can be heavily customised, with its own theme and its own code. A custom platform can still include a simple editor for your team. What matters is where the complexity in your business really sits.
When WordPress is the right choice
WordPress suits most marketing websites, brochure sites and small to medium online shops. It is a good fit when:
- The site's main job is to explain what you do, build trust and generate enquiries.
- Your team wants to edit pages, add articles and change images themselves.
- You sell a manageable range of products and need a standard checkout with payment providers such as Stripe or PayPal.
- You want a foundation that many developers already understand, so you are not tied to one supplier.
In these cases a custom build mostly means paying to recreate things that already exist and are well tested.
When a custom build is the better answer
Sometimes what you need is not really a website. It is a business system with a website attached. Look harder at a custom build if:
- Customers need accounts or portals with their own data, permissions and workflows.
- The site has to run complex processes, such as quoting, scheduling or approvals, that do not map onto pages and posts.
- You are juggling several separate tools and want one platform that replaces them.
- Your plugin list is growing mainly to bolt on behaviour the site was never designed for.
Pushing a business system into a content management tool tends to end badly: lots of workarounds, and a site that is hard to change safely.
The hidden cost on the WordPress side: plugin sprawl
The usual way WordPress goes wrong is not WordPress itself but the pile of third-party plugins added over time. Each one is someone else's code that needs updating, and each one can clash with the others. A site with dozens of plugins that nobody dares update is slow, fragile and a security worry.
This is a matter of how the site is built. A well-built WordPress site uses a small number of plugins that earn their place, with custom code for anything specific to your business. Ask any developer how they approach this before you sign.
Questions to ask before you decide
- What is the site for? Write down the three most important things a visitor should be able to do. If they are all reading, contacting you or buying from a catalogue, WordPress is likely enough.
- Who will change it, and how often? If your own team will make changes, a familiar editing screen is worth a lot.
- What does it need to connect to? A CRM, email marketing, booking or payment tools are all possible with WordPress. If the connections are the heart of the project, consider a custom platform.
- Who will look after it? Whichever route you take, it needs updates, backups, security and monitoring. Agree who does that before launch.
- Could another developer take it on? Common technology and tidy code keep your options open.
A hypothetical example
Imagine a small training company. It wants to show its courses, let people enquire and publish the occasional article. That is a WordPress job, and it would be wasteful to build anything more.
Now imagine the same company wants customers to log in, book places on courses, receive certificates automatically and have staff approve special cases. Courses are no longer pages. They are records in a system with rules. A custom platform, or a WordPress site with significant custom development behind it, may suit better. The conversation to have is about the workflow, not the technology.
You can start simple and grow
Choosing WordPress now does not rule out something bigger later. Many businesses begin with a well-built WordPress site and add custom features as they discover what they need. If the requirements outgrow it, the content and the lessons carry across to a larger platform.
The mistake to avoid is deciding by habit: choosing a custom build because it sounds more serious, or WordPress because it is familiar, without looking at what the site has to do.
Let's build something together
Tell us what you're working on, and we'll come back with an honest view of how we could help.