There are two very different ways to build a WordPress site. One is to buy a ready-made theme and put it together with a page builder, dragging blocks around. The other is native WordPress: developing the theme from the ground up, using only what the platform offers and code written specifically for that project.
Both are legitimate and suit different situations. The problem is choosing without knowing what you're trading off — because the difference between them almost never shows up on launch day, but a year later.
1. Customisation without limits
A site built from scratch is designed around what the business needs, not what the bought theme allows. There are no spare blocks nobody uses and no missing features forcing you to install a plugin. The result matches the approved design instead of approximating it.
With a bought theme, the process commonly runs in reverse: the design is decided by what the theme does. In practice, the company's site ends up looking like hundreds of others.
2. Performance
Commercial themes are built to serve everyone, which means loading code for cases your site will never have. Add the page builder and the plugins it drags along with it, and it's common for a simple page to weigh several megabytes before it shows a single line of text.
A bespoke theme loads what's needed and nothing else. The difference shows up most on mobile, and speed counts towards how search engines rate the site.
3. Security and maintenance
Every plugin installed is third-party code running on your site, with the updates and the vulnerabilities of whoever wrote it. The more there are, the bigger the exposed surface and the higher the odds that an update breaks something.
A site with few dependencies is easier to keep up to date. But careful: “bespoke” doesn't mean “no maintenance”. Any site needs security updates, backups, and someone accountable for them.
4. Evolving over time
When the business changes, the site has to change with it: a members' area, a bigger catalogue, a link to the invoicing software. On a site built from scratch, that's ordinary development work. On a bought theme, it depends on whether the theme's author thought of it — and when they didn't, the usual fix is yet another plugin on top.
There's also a risk that gets forgotten: commercial themes and builders can stop being maintained. When that happens, the site is left dependent on code that no longer gets updates, and migrating away is always more expensive than doing it properly the first time. Cases like Credimax, with its calculators, CRM and links to other systems, don't get solved any other way.
When a bought theme is perfectly enough
It would be dishonest to say it's never worth it. A bought theme is a good option when the budget is tight, when the site has few pages and little functional ambition, or when an idea needs validating quickly. In that case, choose a theme with recent updates, install as few plugins as possible, and expect to rebuild the site once the business grows.
The decision should be made based on what comes next, not just the upfront cost. If you need help making it, this is exactly what we talk about in websites, in bespoke web development, and in online shops, where the weight of plugins gets paid for in lost sales.
2026 note
This article was written when Contágio's own website was still a WordPress build, and the comparison it makes — building from scratch versus a bought theme and page builder — still holds. What's changed is the starting point: these days we also work with bespoke platforms, and the choice is no longer between different ways of using WordPress, but between a familiar content management system and a platform built for the case at hand.
There's no single answer. For a corporate site the client updates themselves, a well-built content management system is still the sensible choice; for a product with its own rules, integrations or volume, building pays off. The criterion is the same one as the rest of the article: what the site needs to do, today and two years from now, and who's going to maintain it.
Not sure which path is right?
Tell us what the site needs to do, today and two years from now. We'll tell you honestly whether a theme will do, or whether building pays off.