The visible cost hides the real cost
The cost of a site isn't its initial quote. It's the sum of build, hosting, plugins, maintenance, security patches and — above all — revenue lost when the site is slow or goes down. That total, over 24 months, is what you should reason about.
Where WordPress still makes sense
WordPress is not a bad choice in itself. For a blog, a simple brochure site, or a project where you must publish fast with no development budget, it's a rational tool. The ecosystem is huge and skills are easy to find.
Where custom takes the lead
- Performance: a custom-rendered site hits Core Web Vitals that layers of plugins almost never allow — and speed weighs on both SEO and conversion.
- Security and maintenance: no constant race to update dozens of plugins, so less attack surface and fewer outages.
- Conversion: every journey is designed for your business goal, instead of being constrained by a generic theme.
- Scalability: adding a feature doesn't mean stacking yet another plugin that slows the whole thing down.
The 24-month calculation
For a basic brochure site, WordPress is often cheaper, full stop. But as soon as the site has to convert, rank and carry your acquisition, custom pays for itself: one point of conversion gained, or a page reaching the first position on Google, is worth far more over two years than the initial gap in quotes.
So the real question isn't "which is cheaper?" but "what role should this site play in my acquisition?". A site that just needs to exist: WordPress. A site that needs to pay off: custom. If you're unsure, a 30-minute audit is enough to decide with numbers, not preferences.
