Website builder vs custom website - or should the nephew build it?

Every studio has heard it. Usually in the first five minutes of a call, said kindly, as a gentle warning that the budget is about to come up.

“Actually, my nephew can build the website.”

And he can! Probably. The nephew is real, the nephew is talented, and the nephew once ran a Minecraft server that forty people lived on for an entire summer. We have nothing but respect for the nephew. Half of us were the nephew.

But “can build it” and “will look after it for the next five years” are two different jobs. So here’s an honest comparison of your four options - the nephew, the drag-and-drop website builder, the template theme and a custom-built site - and the questions that actually decide between them.

Option 1: The nephew

For: Cheap. Enthusiastic. Knows what CSS is. Will add lovingly crafted touches nobody asked for, such as a loading screen where your logo spins.

Against: Has exams. Then a girlfriend. Then a job in another city. Then a different phone number.

The website itself usually turns out fine. The trouble arrives eighteen months later, when the contact form stops working and nobody knows where the site is hosted, what the password is, or why the domain renewal emails go to his old school address. The nephew isn’t ignoring you. He’s in the middle of exam season and honestly doesn’t remember either.

Verdict: A legitimate option if you treat it like a real project - written down, with accounts in your name and a plan for the day he moves on. More on that below.

Option 2: The drag-and-drop website builder

For: Quick to start. Pretty templates. Hosting, SSL and updates are handled for you. You can change your own opening hours at midnight without calling anyone.

Against: The price on the landing page is the price of the plan you won’t stay on. Then come the custom domain, the email add-on, the booking widget, the “remove our branding” upgrade, the second language, the shop, and a plugin for the thing the other plugin was supposed to do. Each one is a small monthly line. Together they’re a monthly bill with a personality.

And you’re renting, not owning. If you ever leave, the design usually stays behind. Your words and pictures come with you; the rest you rebuild.

Verdict: The right choice more often than agencies like to admit. See below.

Option 3: The template theme

The middle path: a bought theme on a popular CMS, hosted wherever you like.

For: Looks professional on day one. Lots of features. Cheap to buy.

Against: It looks professional because it looks like a few thousand other sites. Every feature you don’t use still loads on every page, which is why the demo was fast and your version isn’t. The theme needs updates, the CMS needs updates, the 14 plugins need updates, and at least one of them was last updated around the time the nephew started primary school. Skip the updates for a year and your site becomes a hobby for somebody else’s botnet.

Verdict: Fine if someone actually maintains it. Dangerous if “someone” turns out to mean nobody.

Option 4: The custom site (and the agency that never answers)

We’d be lying if we said the satire stops here. The custom route has its own villain: the agency that was lovely during the sales process and then turned into a ticketing system with a nine-day response time. You paid for a bespoke website. You got bespoke silence.

For: Built for your content, your languages and your customers. Fast, because it only loads what it needs. Grows with you instead of around you.

Against: Costs more up front. Takes longer than an afternoon. Only as good as the people who build it - and whether they still pick up the phone afterwards.

Verdict: Pays off when the website is a working part of the business rather than a digital business card.

The criteria that actually matter

Forget the labels for a minute. These are the questions that decide whether your website still works for you in three years.

Who owns the domain and the accounts. This is the big one. Domain registrar, hosting, the builder subscription, analytics, your Google Business Profile, email - every one of them should be in your name, with your email address and your payment method, and other people added as users. Not the nephew’s account. Not the agency’s account. Yours. If a working relationship ends badly, this is the difference between an awkward email and losing your domain.

Hosting. Where does the site live, who pays for it, and who gets the alert when it goes down? “Somewhere cheap the nephew found” is an answer, but it should be written down somewhere.

Speed. A slow site loses visitors before they read a word, and search engines notice too. Test it on a phone, on mobile data, not on the office Wi-Fi. If you can make a coffee while it loads, so can your customers - at a competitor’s.

SEO basics. Proper page titles and descriptions, real headings, readable URLs, images with alt text, a sitemap, and a Google Business Profile if you have a physical location. None of this is magic, and most builders handle it fine once you fill in the fields. Most sites skip it because nobody knew the fields existed.

Multilingual. If you sell in more than one language, check how each option handles it before you choose. Separate URLs per language, translated page titles, a language switcher that doesn’t dump visitors back on the homepage. On some builders this is an upgrade; with some themes it’s a plugin that needs its own plugin.

Maintenance and security updates. Every website needs someone who owns updates, backups and the contact form that quietly stopped sending in March. With a builder, that’s what the monthly fee buys. Everywhere else, decide who does it and how often - and write their name down.

When a builder is genuinely the right choice

Honestly? Often. If you need a few pages, a contact form, opening hours and a gallery, in one language, and you want to edit it yourself - use a builder. Pick one, pay for the yearly plan, connect your own domain, done. You don’t need a studio, and a good studio will tell you so.

The same goes if you’re testing an idea and don’t yet know whether it’ll exist next year. Spend the money on finding out, not on infrastructure.

When custom pays off

Custom starts making sense when the website stops being a brochure and starts being a tool:

• several languages, done properly, for markets that matter to you
• bookings, quotes, customer accounts, or anything that talks to your other systems
• speed and search visibility that translate directly into revenue
• builder bills that, added up over a couple of years, have quietly overtaken what a one-off build would cost
• a brand that doesn’t want to look like the template everybody else bought

At that point a custom website - or, when it’s really software with a homepage, a web application - usually pays for itself in things that never appear on an invoice: fewer workarounds, fewer plugins, fewer calls to the nephew.

A word in defence of nephews

The nephew isn’t the problem. The nephew is often the first person in the family who took the internet seriously. Unclear ownership is the problem, and it happens with builders, themes and agencies just as often.

So if the nephew builds it: wonderful. Buy the domain yourself. Open the hosting account yourself and add him to it. Ask him to write one page of notes on how everything fits together. Pay him properly - in money, not just Sunday lunch. And when he gets the job in the other city, you’ll still have a website.

If you’d like a second opinion on which option fits - including “honestly, the builder is fine” - just ask us. We answer. That’s sort of the point.