Next.js vs WordPress vs Website Builders: Choosing a Platform in NZ

Most platform advice online is written by someone who sells one of the options. This is an attempt at the honest version: what each platform is genuinely good at, where each one hurts, and how to work out which fits your business. We build custom Next.js sites, so treat the recommendation with appropriate suspicion and check it against the reasoning.

• There is no best platform - there is a best fit for your budget, your update habits, and how much the website actually earns.
• Website builders are genuinely the right answer for a simple presence on a small budget.
• WordPress is flexible and capable, and its real cost is ongoing maintenance most owners do not plan for.
• Custom builds make sense when the website is a revenue channel rather than a brochure.
• Whatever you choose, make sure you own the domain, the content, and the hosting access.

Builders get dismissed too readily by developers. If you need a handful of pages that describe your business, look tidy, and cost very little to run, a builder does that competently and you can maintain it yourself. For a sole trader who needs to exist online and answer the phone, this is often the right commercial decision.

The constraints are real, though, and they matter more as the site matters more. You are working inside the platform's templates and its performance envelope. Fine-grained technical SEO control is limited. And you cannot take the site with you: if you leave, you rebuild rather than migrate. That last point is the one worth thinking about before you have five years of content invested.

WordPress runs a very large share of the web for good reasons. There is a plugin for nearly everything, the editing experience is familiar, developers are easy to find, and you genuinely own the installation.

The cost people underestimate is not the build, it is the upkeep. A WordPress site is a live application made of many independently maintained parts, and it needs updating on a schedule. When that lapses, two things follow: the site slows down as plugins accumulate, and the security exposure grows. Compromises overwhelmingly come in through outdated plugins and themes rather than WordPress itself - which is a maintenance problem, not an argument against the platform.

WordPress is a sound choice if you will keep it updated, or you pay someone to. It is a poor choice if it will be installed and then forgotten for three years, which is the far more common outcome.

A headless CMS manages your content and delivers it over an API, leaving the front end to be built separately. The advantages are real: the public site can be statically generated and therefore very fast, there is no public admin login or database to attack, and the same content can feed a website, an app, and anything else you add later.

The trade-off is that nothing comes assembled. A builder gives you a working site on day one; a headless setup gives you the pieces. It earns its place when content volume is significant or when you need the same content in more than one place - and it is over-engineering for a five-page site.

A custom build is justified when the site is a revenue channel rather than a business card. Booking flows, quote calculators, customer portals, integrations with your CRM or invoicing, location pages built from structured data, genuinely fast pages under real mobile conditions.

The mechanism behind the speed advantage is worth understanding, because it is the substantive difference. Pages can be rendered ahead of time and served as static files from a CDN close to the visitor, rather than assembled by a server on each request. There is no database query in the visitor's path, and the public surface exposes no admin login. That is why these builds tend to score well on Core Web Vitals and present a much smaller security target.

The honest downside: higher upfront cost, and you need a developer for structural changes. If your budget is tight and your needs are simple, this is the wrong tool and any developer telling you otherwise is selling.

Skip the feature comparison and answer three questions about your own situation.

1. What does the website need to do? If the honest answer is "explain what we do and let people phone us", a builder or a tidy WordPress site is sufficient. If it needs to book, quote, calculate, or integrate, you are into custom territory.
2. Who maintains it, realistically? Not who should - who will. If nobody will log in for two years, choose the option that degrades gracefully when ignored.
3. What is a customer worth? A business where one new client is worth $500 has a different sensible budget from one where a client is worth $50,000. Match the investment to what the channel actually returns.

Whatever you choose, insist on three things: the domain is registered in your name, you have your own hosting and admin access, and you can export your content. Plenty of businesses discover during a falling-out with an agency that they own none of these. That is a far more expensive mistake than picking the second-best platform.