There is no universally correct answer here, which is inconvenient for anyone selling only one of the two. WordPress is genuinely excellent for a large class of business websites. It is also, quietly, the wrong tool for a smaller class — and the cost of getting that call wrong shows up eighteen months later, not on launch day.
What WordPress is genuinely good at
You editing your own content. This is the real argument, and it is a strong one. If you will be adding posts, changing prices, swapping photos or adding pages yourself, a good WordPress build hands you that on day one.
Standard requirements, solved already. A contact form, a blog, a shop, a booking calendar. These are solved problems with mature, maintained solutions. Rebuilding them by hand is usually a waste of your money.
Finding help later. If we vanished tomorrow, you could hire any of thousands of South African developers to pick up a WordPress site. That portability is worth something real.
Where it starts to hurt
Plugin sprawl. Every feature bolted on is someone else's code, on their update schedule, with their bugs. A site running twenty-five plugins is a site with twenty-five things that can break independently.
Performance. WordPress can be fast. Most WordPress sites are not, because a page-builder theme plus a stack of plugins ships an enormous amount of code to do very little. You can fight this. It is a fight.
Doing something genuinely unusual. The moment your requirement stops resembling "a website" and starts resembling "an application", you end up bending WordPress into a shape it was not designed for. That bending is expensive, and it never quite stops being expensive.
The admin nobody warned you about. Core updates, plugin updates, theme updates, security patches. Fine when someone is looking after it. A liability when nobody is.
What "custom-coded" actually means
It does not mean reinventing everything. It means the front-end is written for your site specifically, rather than assembled from a theme and plugins. Practically:
- Only the code your site actually needs gets sent to the browser, so it is fast by default rather than fast after a fight.
- Nothing breaks because a third party pushed an update on a Tuesday.
- There is no dashboard full of settings you will never touch.
- The trade-off is real: content changes usually come back to us, unless we build you an editor. That costs more up front.
A simple test
Answer these honestly:
- Will you genuinely be updating content yourself, monthly or more often?
- Is what you need close to something that already exists — a shop, a blog, a booking system?
- Will the site need to grow in ways you cannot describe yet?
- Is speed a competitive issue for you, or just nice to have?
- Does the site need to do something you have never seen another site do?
Mostly yes to 1–3: WordPress, built properly. Custom design, minimal plugins, and someone maintaining it.
Yes to 4 and 5: code it. You will pay more at the start and less every year after.
Genuinely torn: that usually means the answer is WordPress for now. It is easier to move from a well-built WordPress site to a custom build later than to guess at a custom build too early.
The version nobody offers
There is a third option that gets left out because it does not fit neatly on a menu: a custom-coded front end with a small custom editor for the two or three things you actually change. You get the speed and the control, and you still get to swap the homepage photo without phoning anyone.
It is not right for every budget. But if you have been told your only choices are "template" or "expensive", it is worth asking about.