WordPress or a Custom Build? How to Choose for a Small Business

This question usually arrives phrased as a budget question, and it almost never is one. Both routes can be built cheaply and both can be built badly. What actually separates them is how much your site has to change after it launches, and who is going to be doing the changing.

We build custom by default and put WordPress, Shopify or WooCommerce on the table where the platform genuinely fits. That is a working rule rather than a loyalty, and it is worth explaining, because the reasoning transfers even if you never speak to us.

What each one actually is

WordPress is a content management system: a piece of software that runs on your hosting, stores your pages in a database, and gives you an admin area to edit them. Most of what a WordPress site does beyond that comes from plugins — separate pieces of software, written by other people, that you install and keep updated. A typical small business WordPress site runs a theme plus somewhere between five and twenty of them.

A custom build is a site written for your business specifically. There is no admin area unless one is built, no plugins, and nothing on the page that was not put there deliberately. It does exactly what it was built to do and nothing else — which is both the whole advantage and the whole limitation.

Neither is inherently more professional. A well-built WordPress site beats a badly-built custom one comfortably, and the reverse is just as true.

The four questions that decide it

Work through these honestly and the answer usually falls out on its own.

1. Who edits the content, and how often? If you or someone in your team will be adding posts, changing prices or publishing new pages every week, you want a content management system and WordPress is the obvious one. If the site is six pages that change twice a year, an admin area is a large amount of machinery to maintain for a job an email could do.

2. Does the site need to do something, or say something? Sites that say something — here is what we do, here is where we are, here is how to reach us — are well served by either. Sites that do something, particularly something specific to how your business works, tend to fight the platform. Every custom behaviour on WordPress is a plugin, and every plugin is a dependency you did not write and cannot fix.

3. How much does speed matter to your customers? If your traffic arrives on phones, on mobile data, in a hurry — a takeaway at seven in the evening, a barber shop mid-afternoon, a taxi search on a street corner — then every plugin loading its own stylesheet is costing you. A custom build starts with nothing on the page and adds only what earns its place. WordPress can absolutely be made fast, but it is work you are doing against the grain rather than with it.

4. Who maintains it in two years? This is the question people skip and regret. WordPress needs updating — core, theme and every plugin — and updates occasionally break things. That is a genuine ongoing job. A custom site has far less that can drift, but if you fall out with whoever built it, you need someone who can read their code. Both routes have a version of this risk; they just have different shapes.

Where WordPress genuinely wins

We recommend it, unprompted, in these cases:

You publish regularly. A blog, a news section, a portfolio you add to monthly. This is what WordPress was built for and it is still very good at it.

You have a real product catalogue. Dozens or hundreds of products, with stock, variants and prices that move. WooCommerce or Shopify have solved problems here that are not worth solving again from scratch.

Several people need to edit, with different permissions. Roles and workflow are built in. Reimplementing that for a custom site is real work and rarely worth it for a small team.

You want to be able to hire anyone. There are more WordPress developers than any other kind. If the ability to hand the site to whoever is available matters more to you than how it performs, that is a legitimate reason and we will say so.

Where a custom build wins

The site has one job and has to do it fast. Take the booking, take the order, get the call. The smallest possible site that does that job well will outperform a platform build, and it is cheaper to keep running.

Your business does something the platform has no concept of. Lesson blocks with cancellation windows, quotes that price on dimensions, a booking flow that behaves differently on a Sunday. On a platform each of these is a plugin, a workaround, or a plugin plus a workaround.

You want less to go wrong. A site with no plugins has no plugin updates, no plugin conflicts and a much smaller surface for anything to break or be exploited. For a business that cannot afford a website outage during service, this is worth more than it sounds.

Local structure matters more than volume. A handful of genuinely well-built pages for the areas you actually serve, each with correct markup, does more for a local business than a large site with a plugin generating them.

The cost that shows up later

Both routes have a build cost you can compare on a quote. What people underestimate is the second number.

A WordPress site typically carries recurring costs: hosting, often a premium theme, and often several plugin subscriptions that renew annually. Individually they are small; together they are a standing bill, and they arrive whether or not you touched the site that year. There is also maintenance — keeping everything updated — which is either your time or somebody's invoice.

A custom site's recurring cost is usually hosting and the domain, and that is the end of the list. Changes cost money when you make them, rather than continuously. That suits some businesses and not others, and it is worth working out which one you are before you choose.

Our own numbers are on the pricing page — sites are priced by page count and everything else is quoted at an hourly rate. We publish them so this comparison can be done with at least one real figure in it rather than none.

The short version

If you publish often, sell a catalogue, or need several people editing with different permissions, use WordPress and use it properly. If your site has one clear job, needs to be fast on a phone, and changes rarely, a custom build will be smaller, quicker and cheaper to keep.

And if someone tells you one of these is simply better than the other without asking what your site has to do, that tells you something useful about them rather than about the platforms.