Andrew Kwak
Most businesses face the same decision at some point: build the website on a platform such as Wix, Squarespace, Shopify or WordPress, or have it developed to spec. The builder is faster and cheaper on day one, which is why it is usually the right first step. The question is what happens in years two and three, when the site has to carry bookings, quotes, customer accounts or the systems behind the counter.
This piece lays out what builders do well, where they start to cost you and how to tell which side of the line your business is on.
What builders do well
Speed to launch. A site with a few pages and a contact form can be live in a weekend, with hosting, SSL certificates and platform updates handled for you.
Low upfront cost. A subscription and a template cost far less than a build, and the monthly fee is predictable.
Good enough for many businesses. If the site's job is to show who you are, what you do and how to reach you, a builder does that job well and will keep doing it for years.
Where they start to cost you
1. Security you do not control
Templates and add-ons are shared by millions of sites, which makes them a target. Every plugin or app you install is code written by someone else and updated on their schedule. One abandoned add-on can expose customer data, and you may not find out until a customer tells you.
2. Speed drops with every add-on
A booking widget, a review feed, a chat bubble and an analytics script each load their own code. Page speed falls, and Google's ranking signals follow. Sites with a heavy add-on stack routinely score poorly on Core Web Vitals compared with a lean build.
3. Updates that break things
Platform, theme and plugin updates are not optional. One update changes something another depends on, and a five-minute fix becomes a lost afternoon. The more add-ons you rely on, the more often this happens.
4. The workflow has to fit the template
Builders are designed around the common case. A quoting flow with three approval steps, pricing that depends on postcode, or a customer portal with different views per account type usually means custom code bolted onto the platform, which combines the constraints of both.
5. A ceiling on data and integrations
Large catalogues, complex business rules and connections to accounting, inventory or CRM systems push a builder past what it was designed for. The answer becomes a workaround, then another workaround, then a rebuild.
6. Costs that were not in the plan
Paid plugins, premium tiers, transaction fees on some platforms, and a developer on call when something breaks. The subscription looked cheap. The total rarely stays that way.
Where custom development pays off
1. Built around how you operate
Only the features you need, shaped around how the business actually runs. As the business changes, the codebase changes with it instead of fighting you.
2. Security by design
No long tail of third-party add-ons. The attack surface stays small, and access controls can be as fine-grained as your data requires.
3. Performance you can measure
Only the code you need ships to the browser, so pages stay fast. That helps search ranking, conversion and hosting costs at the same time.
4. Your brand, not a theme's
Design decisions serve your customers rather than the template. Small details add up to a site that feels like yours.
5. Ownership
You own the code and the data, and you can fix, improve or replace any part of it on your own timeline.
6. Integrations as part of the brief
Payments, CRM, accounting and internal tools connect cleanly from the start, not through a plugin marketplace.
How to decide
| Question | A builder is enough | Build to spec |
|---|---|---|
| What the site has to do | Present the business, take enquiries | Run part of the business: quotes, bookings, accounts |
| Your process | Standard: a form, a booking, a simple checkout | Specific: approval steps, pricing rules, customer types |
| Other systems | None, or a single add-on | Accounting, inventory, CRM, internal tools |
| Traffic and data | Modest and steady | Growing, seasonal peaks, large catalogues |
| What an outage costs | Inconvenience | Lost revenue |
What to take from this
A builder is not the wrong answer. For many businesses it is the right first step, and moving off it too early wastes money. The mistake is staying on it after the website has become part of how the business operates, and paying for that in workarounds, add-ons and lost speed.
So the decision is less about builder versus custom and more about what the website has to do. If it does real work for the business, build it to do that work. If it is a brochure that happens to be online, a builder will carry it for years.