There is a certain snobbery about purchased themes in this industry, and it is mostly unearned. A good theme customised properly is the right answer for a great many business sites, and pretending otherwise usually means selling somebody a larger invoice than they needed.
It does break down, though, and it is worth knowing where.
When customising a bought theme is the right call
- Your site does what thousands of sites do. Pages, a blog, a contact form, maybe a shop. This is solved; buying the solution is sensible.
- You need it live soon. Weeks instead of months.
- The budget is finite and you would rather spend the difference on photography or ads, both of which will do more for you than bespoke markup.
- You want to edit pages yourself without a developer, and the theme's editor does that well.
For most small businesses all four are true, and the honest recommendation is a good theme, properly customised, with the saved budget spent on content.
Where it genuinely breaks down
- Speed, past a point. Multipurpose themes carry the code for every demo they ship. You can mitigate it; you cannot remove what the theme fundamentally loads — see why your WordPress site is slow.
- When you are fighting it. If getting the design you want means overriding the theme at every turn, you are paying custom-build prices for a worse result. This is the clearest signal there is.
- Unusual functionality. A booking flow tied to real availability, a configurator, an integration with software you already use. Bolting these onto a theme costs more than building properly.
- Brand that has to be exact. If the design is a real asset rather than a nice-to-have, a theme will approximate it.
- Abandonment risk. You are depending on someone else to keep updating it. Check the theme's update history before buying, the same way you would a plugin.
The rule that prevents the usual disaster
If you customise a theme, the changes go in a child theme — never in the theme's own files.
Edit the parent directly and the next theme update overwrites everything. People then stop updating to protect their changes, and an un-updated theme becomes the security hole that gets the site defaced. We see this one constantly, and it is entirely avoidable by doing it correctly on day one.
If somebody is customising a theme for you, ask whether they are using a child theme. The answer tells you a lot.
The middle option worth knowing
Between a bought theme and a bespoke build sits a lightweight starter theme with the design built on top. You get markup without a decade of accumulated options, full control of the design, and no dependency on a third-party vendor — usually for meaningfully less than a from-scratch build.
For a business that has outgrown a theme but does not need custom engineering, this is often the right answer and it rarely gets offered.
How to tell which side you are on
Ask what the site has to do that a thousand other sites do not. If you can answer in a sentence, that is the case for custom. If you cannot, buy the theme, spend the difference on photographs and words, and come back to it in two years when you actually know what you need.
We work both ways and will say which we think fits. WordPress customization covers the theme route; tell us what the site has to do and we will tell you which one it is.