A brochure site — who you are, what you do, how to reach you — is exactly what Squarespace or Wix was built for, and a builder does that well. This post is for the businesses past that: where the builder has quietly become the expensive option, and it's worth knowing whether you're in that group.
The test is whether your website has to do anything. If it mostly has to say things, a builder can still be fine. Past that, here's where the cost actually shows up.
Where builders start to cost you
The monthly never stops, and it isn't only the platform. The plan is the visible part. Then there's the ecommerce tier, the transaction fee, the booking app, the form app, the SEO app, the popup app. Each one is a few dollars and each is billed separately, which is exactly why nobody adds them up. It's the same shape as the IT costs that never show up on an invoice.
You're renting the whole thing. Your content, your layout, your URLs. There's no meaningful export — you can usually get your text and images out, but not the site. Moving platforms means rebuilding, which is why people stay on plans they've long outgrown.
Speed. Builder pages ship a lot of JavaScript to do things a page doesn't need done. That shows up in Core Web Vitals, and it matters most on a phone on a mediocre connection, which is exactly where local searches actually happen.
The design ceiling. Templates are fine right up until you want the thing the template doesn't do. Then you're fighting the editor, and the fix is usually a plugin that half works.
What "custom" actually means here
Worth clearing up, because it sounds more expensive than it usually is. Custom does not mean a bespoke content management system built from nothing.
For most small businesses it means a static site — the pages are built once and served as plain files. No database, no plugins to keep updated, very little to attack. It loads fast because there's almost nothing to load, and hosting runs from free to a few dollars a month.
The trade is that changing content means editing a file rather than clicking around in an editor. For a site whose pages change a few times a year, that's a fine trade. For one that changes weekly, it isn't — and that's a genuine reason to stay on a builder.
The comparison
| Site builder | Custom build | |
|---|---|---|
| Up front | Low or nothing | Higher, once |
| Ongoing | Monthly, forever | Hosting only |
| Editing | Anyone, in a browser | Editing files |
| Speed | Heavy by default | Fast by default |
| Design | Template's limits | Whatever you want |
| Ownership | Rented | Yours |
| Best when | The site says things | The site does things |
The question that actually decides it
Add up everything you pay for the site each month — plan, apps, transaction fees, the domain, anything else attached to it — and multiply by thirty-six.
That's your three-year number, and it's the one to weigh a build against. Most people have never worked it out, and it's routinely larger than they expect.
If it's small, stay where you are. If it's large, or if it grows every time you need the site to do one more thing, the arithmetic has already moved.
Signs it's worth pricing out a move
- You're paying for three or four add-on apps to make one page work
- The site is slow on a phone and you've quietly stopped checking
- You asked for a change and were told the template can't do it
- You're on an ecommerce plan taking a cut of every sale
- Nobody has been able to edit it since the person who set it up left
The same math as any other tool
It's the same shape as buying software instead of building it — most of the time the off-the-shelf option is right. If a builder does what you need, keep it. If you're working around it every month and paying for the privilege, the signs above are the tell.
If you've priced it out and a custom site is the better math, get in touch and we'll start with what the site actually needs to do.
More on what I build and how a project runs.