Comparisons
A paid theme or A custom theme
What I would pick: A customised paid theme, in the large majority of projects, and I say that even though it bills less: you launch sooner, a vendor maintains it, and the budget goes to what converts. A custom one earns its place when the paid theme has been modified so much that updating is impossible, or when the brand needs something no theme in the store does.
The differences
| What we compare | A paid theme | A custom theme |
|---|---|---|
| Time to launch | Short | Long |
| Updates | Published by the theme author | Yours, or whoever wrote it |
| Starting performance | Good or middling, depending on the theme | Whatever you decide; you only pay for what you use |
| Sections for your team to build pages | The theme’s, generic | Your business’s |
| Risk of getting stuck | Low if changes live in their own files | Depends who documented it |
| Up-front cost | Lower | Higher |
What you are actually buying in a theme
It is not the design. It is what your team will be able to do without calling anybody. Two themes can look identical on delivery day and, six months later, one builds a landing page in twenty minutes while the other turns every change into a quote.
That depends on how the sections and blocks are split, and it is exactly the part that does not show in a mockup or in a paid theme’s demo.
Why I recommend the paid one almost always
Because most of the value is elsewhere. With a well-chosen paid theme, customised, you launch sooner, somebody else publishes the updates, and the budget you save goes to what moves the needle: order flow, speed, search.
I have worked that way on large projects: Émolo’s wholesale portal is built on the Prestige theme the store was already using, and the work went entirely into the order table and the per-company access.
The two signals that it is time for a custom theme
1. The paid one can no longer be updated. If the changes are scattered inside the original files and nobody remembers which, every update is a project. There comes a point where rewriting is cheaper than continuing to patch.
2. The brand needs something no theme does. A configurator, a product page that is not a product page, a navigation model of its own. Not “we want something unique”: something specific that no theme in the store solves.
The third route, the one I use most
A paid theme as the base, with everything custom in new files and new sections, never scattered through the originals. That way the theme stays updatable, your work is identifiable, and the next person to touch it knows where to look.
It is the difference between being able to update the theme and not.