Wix, Squarespace, Webflow and WordPress themes made it possible for anyone to put a website online. That's a good thing. We don't build on them, but not because they're bad. They're built for a different job.
This is the honest version of the comparison: what a builder is good at, where it starts to cost you, and how to tell which one your business actually needs.
What a website builder is good at
Builders exist to get something online quickly without writing code, and they're genuinely good at it.
- Speed to a first version. Pick a template, swap the text, publish.
- Low cost to start. A monthly subscription instead of a project fee.
- Editing without a developer. Everything happens in a visual editor.
If you're testing an idea, need a single page this weekend, or your website is essentially a digital business card, a builder can be the right call.
Where builders start to cost you
The trade-offs don't show up on day one. They show up in the second year.
Your site looks like other sites. A template is a starting point shared by thousands of businesses. You can change the colours and swap the photos, but the structure — the part people actually recognise — stays the same. The harder you push against it, the harder it pushes back.
It loads things you don't use. A builder has to support every feature for every customer, so each page carries code for features you never touched. Your visitors download it anyway and your pages get slower. Speed changes how long people stay, and it's one of the signals search engines look at.
You rent it. On a hosted builder, your website only exists inside that platform. Stop paying and it goes offline. Some platforms let you export parts of a site; none let you pick the whole thing up and run it somewhere else unchanged. There's more on this in what it means to own your website.
Plugins pile up. WordPress is different — you can host it yourself — but a theme plus a dozen plugins becomes a stack of other people's code that all needs updating, and any one of them can break the site.
What "custom-coded" actually means
A custom-coded site is designed for your brand first, then written for exactly that design. There's no template underneath and no features waiting in the background.
In practice:
- It looks like you. The layout, type and motion come from your brand, not from a theme gallery.
- It's fast. Each page loads only what it needs, because nothing else exists.
- It lives where you want. The code sits in a repository you own and deploys to Vercel, Netlify, Cloudflare or your own server.
- It grows with you. Need a store or a CMS later? It's added to the same codebase instead of bolted on as a plugin.
The old trade-off was time
The reason people chose a builder was never quality. Everyone knows a custom site is better. The problem was that custom used to mean three months and an agency invoice to match.
You shouldn't have to choose between fast and good.
That's the trade-off we set out to remove. A custom-coded site that's designed, built and launched in seven days changes the maths.
How to decide
Choose a website builder if:
- you're testing an idea and might not need the site in six months
- a template genuinely fits your brand as it is
- you want to rearrange the layout yourself every week
Choose a custom-coded website if:
- your website is how customers judge you before they get in touch
- you want it to look like your brand, not a theme
- speed and search visibility matter to your business
- you want to own it outright, with no platform in the middle
What we build with
React and Next.js. TypeScript. Our own CMS when you need to edit things yourself, headless commerce when you need a store, and GSAP and WebGL for motion. Deployed on Vercel, Netlify, Cloudflare or your own server. Never Webflow, Wix or a WordPress theme.
If a custom site sounds right, the three packages are on one page, prices included.