Ask the internet whether to build your site on WordPress or go fully custom and you will get two camps shouting past each other. One says WordPress is bloated and amateur; the other says custom builds are expensive over-engineering. Both are selling something. The useful answer depends entirely on what your company actually needs the website to do — and for most growing companies, that answer is clearer than the debate suggests.
,I build primarily on WordPress with Elementor, and I also know when a project genuinely needs something else. So let me give you the honest decision framework rather than a sales pitch for either side.
,What will your team need to change without a developer?
,This is the question that decides most cases, and it is almost always underweighted. After launch, who updates the site? If the answer is a marketing person who needs to add a blog post, swap a headline or publish a new landing page without calling a developer every time, that points hard toward WordPress. Its entire advantage is that non-technical people can safely maintain it.
,A fully custom site can be faster and leaner, but it often means every small change goes back through a developer. For a company that updates content regularly, that is a tax that compounds — and a reason many "superior" custom builds quietly go stale.
,What does your site actually have to do?
,Be honest about the real requirements, not the imagined ones.
,- A marketing site, blog, landing pages and lead capture? WordPress handles this superbly.
- Standard integrations — forms, analytics, a CRM, basic e-commerce? Well-trodden ground on WordPress.
- A genuinely custom web application, complex real-time features, or a bespoke product experience? That is a different project, and WordPress is the wrong tool.
Most growing companies are in the first two buckets and think they are in the third. The ambition is real, but the website they need right now is a marketing site that converts — and over-building it costs money and time that would be better spent elsewhere.
,Is "WordPress looks generic" actually true?
,It is true of bad WordPress, which is most of it — because most WordPress sites are a stock theme with the colours changed. That is where the platform's reputation comes from. But the platform is not the ceiling; the craft is. A WordPress site designed and built properly, with custom layouts and real attention to typography and performance, is indistinguishable from a custom build to everyone except the developer who opens the hood.
,The "looks generic" problem is a design problem, not a platform problem. Done by someone who designs rather than assembles, WordPress produces sites that look like nobody else's.
,What about speed and performance?
,A legitimate concern, because WordPress can absolutely be slow — when it is overloaded with plugins and a heavy theme. It can also be fast when built with discipline. Performance is mostly a function of how the site is built, not which platform it runs on. This is one reason I design and build in the same hands: a site designed without regard for how it will be constructed tends to become bloated, whereas building and designing together keeps it lean.
,So how should you actually decide?
,What are the real ongoing costs of each?
,The build quote is only the first number. What a platform costs over the years that follow is often the more important figure, and it is where the two paths genuinely differ. A well-built WordPress site has a modest, predictable running cost: hosting, a handful of licensed plugins, and occasional maintenance. More importantly, your own team can make most changes without paying a developer each time, which over a few years is a substantial saving in both money and speed.
,A custom build can be leaner to run in pure hosting terms, but it usually concentrates the cost in developer dependence: every change, however small, is a ticket for someone technical. For a marketing site that changes often, that dependence adds up quietly and can exceed the apparent savings. The honest comparison is not build cost versus build cost; it is total cost of ownership over three to five years, including the value of your team being able to move without waiting.
,- Build cost — the visible number, and the least important over time
- Running cost — hosting, licences, maintenance
- Change cost — can your team edit it, or does every tweak need a developer?
- Dependence cost — how trapped are you if your developer moves on?
How do you avoid the platform becoming a trap?
,The real fear behind the platform question is being locked in — stuck with a site you cannot change, cannot leave, and cannot understand. This is a legitimate worry, and it applies to both paths. A WordPress site stuffed with obscure plugins and undocumented custom code can be just as much a trap as a bespoke build only its original developer comprehends. Lock-in is not really about the platform; it is about how responsibly the thing was built and handed over.
,Avoiding the trap is a matter of discipline: a clean build, a sensible and minimal set of dependencies, organised files, and documentation clear enough that another competent professional could take over. I build so that a client is never hostage to me — the site is theirs, the access is theirs, and the knowledge of how it works does not live only in my head. Freedom to leave is, paradoxically, one of the things that makes clients comfortable staying.
,What should you ask a developer before you decide?
,Rather than asking "WordPress or custom," which invites a biased answer, ask questions that reveal whether the person is matching the tool to your situation. Ask who will be able to update the site after launch, and how. Ask what it will cost to run and to change over the next few years. Ask what happens if you want to leave, and whether you will own everything. Ask them to justify their recommendation in terms of your business, not their preferences.
,A good answer is specific to you and honest about trade-offs. A bad answer is a blanket rule — "I only build custom" or "WordPress is always best" — that tells you more about the person's habits than your needs. The platform is a means to an end, and the end is a site that serves your business and your team for years. Keep the conversation there, and the right choice usually becomes obvious.
,Start from how the site will live after launch, not from the technology. If your team needs to maintain and grow the site themselves, you want standard integrations, and you need a marketing site that converts and looks genuinely yours — WordPress, built well, is the pragmatic and often superior choice, and I will build it to look nothing like a template. If you have a genuinely bespoke product experience or application requirements, that is a custom build, and I will tell you so rather than forcing it onto the wrong platform. The goal is the right tool for your situation, not a trophy for the fanciest stack.