Website builder or web developer? Do the three-year maths.
The builder ads show the first month's price. This guide shows year three. It also tells you, plainly, the situations where the builder is the better choice for you — because a recommendation you can't check isn't worth reading.
The money, over three years
Builder pricing is honest about the month and quiet about the rest. Here's the shape of it for a typical small business site:
| DIY page builder | Hand-built by a developer | |
|---|---|---|
| Up front | $0–$30, plus a weekend or three of your evenings | One quoted price, approved before work starts |
| Every month | Subscription, often rising after year one; extra "apps" for booking, forms, reviews | Nothing required. Optional care plan if you want someone watching it |
| Every year | Domain (sometimes marked up), sometimes a "premium template" renewal | About $15 for your domain, at your registrar, in your name |
| Your time | 10–30 hours to build, then an hour here and there forever | About an hour on the phone to describe your business |
| Year-three total, cash | Commonly several hundred dollars before counting your hours | The build price plus ~$45 of domain renewals — on typical numbers, less than the builder's cash-only total |
| What you hold at the end | An account on someone's platform | Files, domain and hosting login — yours to keep or move |
Read that last row twice, because it surprises people: once the subscription and the apps have run for three years, the DIY route has usually spent more cash than a hand-built site cost to build — before anyone counts your evenings. The reason a local developer can sit under the subscription companies is unglamorous: free static hosting, domains at cost, no office and no app store, because the code is written by hand.
The exact numbers depend on the builder and on you, which is why there's a calculator on this site that uses your subscription price, your apps and your hourly value: the true-cost calculator. Drag the sliders and watch the three-year gap open or close. It doesn't ask for your email.
Ownership is the whole argument
Everything else on this page is arithmetic. This part is principle. On a builder you are renting: stop paying and the website stops existing, and the address your customers learned goes dark. Moving to another platform means rebuilding, because the "site" is really rows in their database wearing their template.
A hand-built site is a pile of files you can hold. Put them on any hosting in the world and the site stands back up. That's not a technical footnote — it's the difference between an asset and a subscription.
The one-question test: "If we stopped paying you tomorrow, what would I still own?" Ask it of every builder salespage and every developer, including me. My answer is: the domain, the hosting account, the files and the code — all in your name from day one.
When it breaks — because it will
Sites don't fail loudly; they rot. A form stops reaching the inbox, a certificate expires, a plugin update changes a layout. On a builder the path is a help centre and a ticket queue, and the honest answer to "can it do X?" is often "there's an app for that" — another monthly line. With a developer you call the person who wrote it. On my $29 care plan that call is same-day, and the plan exists precisely so the rot gets caught before a customer notices.
Speed, and the thing nobody mentions
Builder sites carry the platform's editor, tracker and app stack on every page load. A hand-coded brochure site is a few dozen kilobytes and loads on a beach car-park's 4G before the builder page has finished asking for permission. Speed is a ranking factor and, more importantly, it's the difference between a customer reading your prices and closing the tab.
When the builder genuinely wins
Here's the list I promised. A DIY builder is the right call when:
- You enjoy it. If laying out pages is your idea of a good evening, the time cost isn't a cost.
- You need it live this weekend for an event, a market stall, a sale — and it can be replaced later.
- You'll rearrange it weekly. A menu that changes daily is fine to edit yourself in a visual editor.
- The budget is genuinely zero and the alternative is no site at all. A builder site beats no site.
- You want the platform's extras — their payments, their email marketing, their appointment system — and you're content to live inside that ecosystem.
And a developer is the right call when the site is the front door of the business: when it has to load fast on a phone, rank for "near me", survive years without rot, do one custom thing no template does, and be yours at the end of it.
The hybrid path, honestly
Some businesses start on a builder and outgrow it. That's a normal story, not a failure. Moving off one means rebuilding the pages and keeping search rankings alive with redirects — doable, and worth budgeting for the day the subscription stops feeling cheap.
Five questions that settle it fast
- Who owns the domain? If the answer isn't "me, at my registrar", pause.
- What's the year-three total, including apps and my hours?
- What happens to the site if I stop paying?
- Who fixes it when the form breaks — and how fast?
- Can I leave with everything I paid for?
Ask me the same five. My answers are on the comparison page, next to the calculator, including the card that lists when a builder beats me.
Straight answers
Is a DIY builder cheaper than hiring a developer?
In cash, sometimes, for year one. Over three years a subscription with an app or two commonly reaches several hundred dollars before your own hours are counted. A hand-built site is one build price plus about $15 a year for the domain, so over three years it usually wins — and you own the result.
Do I own a site I built on a builder?
Usually not in any portable sense. You own an account and your content inside their platform; stop paying and the site goes dark, and moving means rebuilding. With a developer who hands over files, domain and hosting logins, the site is property you can take anywhere.
When is the builder the better choice?
When you enjoy building and have spare hours, when it must be live this weekend, when you'll rearrange it weekly, when the budget is truly zero, or when you want the platform's bundled extras. Those are all real situations.
What happens when it breaks?
Builder: help centre, forum, ticket queue — and often "that needs an app." Developer: the phone number of the person who wrote it. On my care plan the response is same-day, which is the entire point of the plan.
Can you move my existing builder site to something I own?
Yes — rebuild the pages by hand, keep the wording and photos, and protect your search position with redirects from the old addresses. It's quoted as its own job, flat, approved before I start.
Still weighing it up? Ask me the awkward questions
I'll tell you honestly which route fits your business — including when the answer is "keep your money and use the builder." That conversation is free.