Custom site, or WordPress and Shopify?
Both answers are correct in different situations. Four questions decide which situation you are in - and one of them matters far more than the rest.
Written by All DigitalPublished Updated
Short answer
Use a template platform when your requirements are conventional: a brochure site, a blog, or a store with standard products and standard checkout. Build custom when your business logic does not match what the platform assumes, when the interface is itself a competitive advantage, or when performance and search visibility are commercially critical. The deciding question is usually the second one: does what you need to do already exist as a plugin, or does it have to be designed?
Start with what the platforms are actually good at
WordPress and Shopify are not inferior technology. They are enormously capable systems that solve the common cases extremely well, and they solve them for a fraction of what a custom build costs. Dismissing them is a sales position, not an engineering one.
WordPress is excellent when the site is mostly content, updated often by non-technical people, with conventional structure. Shopify is excellent when you sell standard products through a standard checkout and want the payment, tax and shipping problems already solved. If that describes you, the rest of this guide is an argument for spending less money than we would like you to.
The four questions
Answer these honestly. A single strong yes on the second or third question usually outweighs everything else.
- Does a plugin already do what you need? Search for it before assuming it does not exist. If one plugin does it well, use it. The cost of custom is only justified when the alternative is three plugins that half-fit and interfere with each other.
- Is your logic unusual? Availability rules, approval steps, compatibility matrices, tiered pricing, multi-tenant permissions. This is the question that actually decides most projects. Planirent needed date-range availability, deposits, operator approval and refunds simultaneously, and that combination did not exist.
- Is the interface itself part of why people choose you? In a category where every competitor bought the same theme, a distinct storefront is a real advantage. In a category where people arrive by recommendation and just need the address and the phone number, it is not.
- How much does speed and search visibility matter commercially? If most of your customers arrive through search, the difference between a page that renders immediately and one that assembles itself after loading a theme and twelve plugins is money. If they arrive through a printed advertisement, it is much less so.
What each option actually costs you
The honest trade-offs, in both directions.
- Template: much lower upfront cost, faster launch, huge ecosystem, and a large pool of people who can work on it later. In exchange you accept the platform's assumptions, ongoing licence and subscription costs, performance limits you cannot fully engineer around, and the risk that a plugin you depend on is abandoned.
- Custom: your logic exactly, only the code your pages use, full control over rendering and indexing signals, and no licence trail. In exchange you pay considerably more upfront, you need a developer for structural changes, and you are responsible for maintenance that a platform would otherwise handle for you.
The migration question nobody asks early enough
If you are already on a platform, the cost of moving is not only the new build. It is the URL map, the content migration, the redirect work, the re-verification and the period afterwards where search results are catching up.
That cost is real and worth paying when the platform is genuinely the constraint. It is not worth paying because the site looks dated - a redesign on the existing platform is far cheaper and carries much less risk. Be clear about which problem you actually have before deciding.
When we tell people not to hire us
We recommend against a custom build when the brief is a conventional brochure site with no unusual requirements, when the budget only covers a custom build by cutting the content and testing that would make it work, or when nobody internally will be available to make decisions during the project. In the last case the platform is not the problem and a custom build will not fix it.
Saying this in the first reply costs us work occasionally. It costs less than delivering something that was the wrong purchase.
Frequently asked questions
No. A well-built WordPress site can rank perfectly well. What harms search performance is the accumulation - a heavy theme, overlapping plugins, unmanaged duplicate URLs from archives and parameters - not the platform itself. A custom build makes those problems easier to avoid; it does not make them impossible to create.
Yes, and it is often the sensible order. Launch on a platform, learn what your customers actually do, then rebuild the parts that the platform is genuinely blocking. Keep your URL structure clean from the start and that later migration is far cheaper.
They solve the editing problem and create a performance one. They ship a general-purpose rendering layer to handle a specific page, and the weight shows. If editing independence is the priority and speed is secondary, that can be a fair trade.
Only if content genuinely changes. A headless CMS can be connected to the pages that need editing while leaving the layout fixed, which is the main advantage over a page builder: editors change content, not structure, so the design cannot be broken by an edit.
Want this applied to your project?
Send a short brief and we will give you a specific answer rather than a general one.
Start a project