WordPress or a custom build, and how to tell which one you need
WordPress is not the wrong answer. It is an answer with an ongoing job attached, and nobody explains that job before you buy. Here is what that job is and when it is worth taking on.
Somebody has probably already told you to just put your site on WordPress. It runs an enormous share of the web, every web person knows it, and there is a plugin for anything you can think of. All of that is true, and none of it answers the question you actually have.
The question is not whether WordPress works. It does. The question is what it costs you to keep it working, and who is going to do that job.
What you are actually buying
WordPress is not a website. It is a system for running a website, and the site itself gets assembled out of parts: a theme somebody sells, plus however many plugins it takes to add booking, contact forms, image galleries, spam filtering, backups, and search settings.
Each of those parts is made by a different company on a different schedule. They update whenever they update. WordPress itself updates too, and when it does, the parts have to keep working with it and with each other.
That assembly is why WordPress can do almost anything. It is also the whole source of the maintenance job nobody mentions in the sales conversation.
The job nobody quotes you for
Updates arrive constantly. Most are routine. Occasionally one is a security patch you cannot skip, because an unpatched site is how a small business ends up serving spam links to Google without noticing for a month.
And every so often an update breaks something. A plugin stops talking to the theme, and your booking form quietly stops sending. Nothing goes down. There is no error, no alert, no sign at all from your side of the screen. You just get fewer calls that week, and you assume it was a slow week.
So somebody has to be watching. That somebody is either you, learning enough to keep it healthy, or a person you pay monthly to do it for you. Both are real answers. What does not work is nobody, because a WordPress site with no one minding it does not stay still. It degrades.
The other thing that creeps up on you is weight. Every plugin adds code the visitor’s phone has to download before the page becomes usable. Add enough of them and the site gets slow in a way that is nearly invisible on your office wifi and very obvious on a phone in a driveway. That is exactly where your customers are when they decide whether to wait or hit the back button.
The inherited-site problem
The version of this that costs the most is when the person who built it moves on.
Now there is a site running someone else’s theme and a stack of plugins, some of which were paid licences that expired, and no notes about why any of it was set up the way it was. Nobody has the admin login. Half the time nobody is certain who owns the domain.
Fixing that usually costs more than the original build did, because the first job is not fixing anything, it is working out what is actually there. Any web person will tell you the same, and most of them have inherited a few.
This is not an argument against WordPress. It is an argument for knowing, before you sign anything, who holds the keys and what happens when that person is gone.
When WordPress is genuinely the right call
Pick it when you are going to publish. If you plan to put out posts, project write-ups, or new service pages regularly and want to do that yourself without calling anyone, WordPress gives you a real editor built for exactly that, and that is a good reason to accept the maintenance job.
Pick it when you have someone. An in-house person, an agency on retainer, a family member who does this for a living. The job is not hard when it belongs to somebody.
Pick it when you need something from that plugin ecosystem specifically. Real online store functionality with inventory and payments is a solved problem there and would be an expensive thing to build from scratch.
Pick it when being able to hand the site to any developer in town matters more to you than anything else. That is a real advantage and worth something.
When a custom build makes more sense
A built site is the other shape. Rather than assembling a system that generates pages, someone builds the pages your business actually needs, and what gets served to a visitor is just the finished result.
That suits a business whose site is a handful of pages that rarely change. Your services do not get rewritten monthly. Your service area is your service area. When the content is stable, the machinery for constantly changing it is overhead you are carrying for nothing.
It suits you when speed matters, and for anyone whose customers search on a phone mid-problem, it does. There are no plugins to load because there are no plugins.
And it suits you when you have no interest in being a part-time systems administrator. Nothing to update means nothing to break while you are on a job.
The honest tradeoff: changing a built site means going back to whoever built it, or learning the setup yourself. If you want to rewrite your own copy at 10pm on a Sunday, that is a genuine point in WordPress’s favour and you should weigh it.
The way to actually decide
Forget which one is better, because neither is. Two questions settle it.
How often will this site’s content actually change? Not how often you would like it to. How often it will, given how your week really goes. If the honest answer is a few times a year, you do not need a publishing system.
Who is maintaining it in eighteen months, by name? If you can name that person and they know they are it, WordPress is a reasonable choice. If the answer is a shrug, you are choosing a site that needs weekly attention and quietly planning to give it none.
Everything else is preference. If you want to see how we handle the built-site version, the packages breakdown covers what is included, and the plumbers page walks through what this looks like for one trade specifically.