Overview
Most businesses that need a new website end up weighing two routes. One is a hosted website builder such as Wix, Squarespace, Webflow or Shopify, where you pick a template, edit pages visually and pay a monthly fee. The other is a custom site built with a framework like Next.js, designed around your content and deployed to your own hosting.
Neither option is better in every case. Each one suits a different stage, budget and level of ambition. This guide sets out the questions that usually settle the decision, so you can choose based on what your site needs to do rather than on what is fashionable.
Start with what the website has to do
List the jobs your website must handle in the next twelve to eighteen months. A brochure site that explains your services and collects enquiries is a very different project from a site that needs customer logins, calculators, product configurators, multi-language content or live data from your CRM.
If most of your list is pages, forms and a blog, a builder can cover it well. If your list includes logic that is specific to your business, or connections to systems you already use, a custom build starts to make more sense.
- Content only: pages, a blog, a contact form and basic SEO.
- Light integration: newsletter sign-up, booking widget, simple payments.
- Custom behaviour: user accounts, dashboards, pricing logic, API integrations, or content pulled from another system.
When a website builder is the sensible choice
Builders are hard to beat for speed and convenience. You can launch in days, your team can edit pages without a developer, and hosting, security patches and SSL certificates are handled for you. For an early-stage business testing a message, or a small firm that mainly needs a credible online presence, that is often exactly right.
The trade-offs show up later. You work within the platform's templates and plugin ecosystem, so unusual layouts or features can become awkward. Performance depends on how much the platform loads on each page. Monthly costs rise as you add apps and seats. Moving away later usually means rebuilding rather than exporting.
- You need to launch quickly with a modest budget.
- Your content changes often and non-technical staff will edit it.
- Your requirements fit comfortably within the platform's features.
When a custom Next.js site earns its cost
Next.js is a React framework that can render pages on the server, generate them ahead of time, or mix both. In practice this gives you fast pages, clean URLs and metadata that search engines can read easily, and complete control over design and behaviour.
A custom build makes sense when the website is closely tied to how your business operates. Examples include pulling services, jobs or articles from a CRM, showing pricing that depends on user input, giving customers a portal, or building a site that will later grow into a web application. Because you own the code, you can move hosts, change providers and extend the site without asking a platform for permission.
The cost is a larger upfront investment and a need for ongoing technical care. Someone must keep dependencies updated, monitor uptime and handle changes the content editor cannot.
- Your site needs integrations or logic a builder cannot provide cleanly.
- Performance and technical SEO are central to how you win customers.
- You want to own the codebase and avoid platform lock-in.
Do not forget content editing
A common worry about custom sites is that the team will lose the ability to edit pages. That does not have to happen. A custom Next.js site can pull its content from a headless CMS or from an admin panel in a system you already use, so editors keep a familiar form while developers control the presentation.
Decide early who will edit what. Blog posts, job openings and team updates should be editable without a developer. Page layouts and components usually change less often and can stay in code. Agreeing this split before design starts avoids frustration after launch.
Compare the total cost, not just the launch price
Builder subscriptions look cheap at first, but add up the plan, any paid apps, extra editor seats and transaction fees over three years. For a custom site, include design and build, hosting, a maintenance arrangement and a budget for small changes.
Also consider the cost of switching. If you expect your needs to grow significantly, starting on a builder and rebuilding in two years may cost more overall than building custom once. If you are still validating your offer, the cheaper, faster route is usually wiser, and you can rebuild once you know what works.
A simple way to decide
Write down your must-have features, who will edit the site, which systems it must connect to, and your three-year budget. Then test those requirements against one or two builders. If everything fits without workarounds, a builder is likely the pragmatic choice. If you find yourself relying on several plugins and compromises to make it work, that is a strong signal that a custom build will serve you better.
Whichever route you take, protect the basics: keep a copy of your content, own your domain name, set up analytics from day one, and plan redirects if URLs change. If you would like a second opinion on your requirements, you can write to hello@yoorie.com.
LinkedIn