"What should we build our website on?" usually comes up at the very start, before it's fully clear what the site needs to do. Some people recommend a website builder, others WordPress, others a modern stack on Next.js. Each is right for its own job and wrong for someone else's.
Let's look at the three main paths: a website builder, a CMS like WordPress, and custom development on the Next.js framework. We'll show how they differ in practice, who each one suits, and which questions to ask when choosing a platform so you don't have to rebuild everything a year from now.
Where to start when choosing a website platform
Arguing "WordPress or Next.js" is pointless until you know what kind of site you need. Answer a few questions first, and the choice largely makes itself.
- What the site is for. Testing an idea and collecting first leads, attracting customers from search, selling products online, or serving customers in an account area.
- How many pages it will have. A dozen service pages, or a catalog of thousands of products with filters.
- What it connects to. CRM, ERP or accounting system, inventory, payment providers, internal services.
- Who will run it. A marketer with no technical skills, a content manager, or your own development team.
- What the plans are for the next year or two. Will it stay a brochure site, or grow into a store, a customer portal, a service?
- How much search matters. For a site that lives on organic traffic, the technical foundation matters more than for an ad landing page.
With these answers, the conversation with a vendor becomes concrete: it's clear what to compare and what you're paying for.
Three paths: builder, CMS, and framework
There are plenty of platforms, but almost every option comes down to one of three approaches. Here's how they compare on what matters to a business.
| Website builder | WordPress | Next.js | |
|---|---|---|---|
| Launch | Fastest | Medium | Medium |
| Design | Within blocks and templates | Anything, but tied to themes and plugins | Anything |
| Integrations | Limited | Ready-made plugins | Anything, through development |
| Site speed | Depends on the platform | Needs tuning | A core strength |
| Content management | Visual editor | Built-in admin panel | Headless CMS or custom admin |
| Ownership | The site lives on the platform | Code and server are yours | Code and server are yours |
Below is a closer look at each approach: where it shines and where it starts getting in the way.
Website builders: fast, but with a ceiling
A website builder is a service where you assemble a site from ready-made blocks in a visual editor. No developer needed, launch takes days, and the cost is a subscription plus a designer's or marketer's time.
A builder works well when you need a landing page for an ad campaign, a simple brochure site, an event page, or a quick test of a new idea. If a month later it turns out the market doesn't want the product, you haven't spent a development budget.
The limits show up as you grow. Design is capped by what the blocks can do. Complex flows such as calculators, customer accounts, or ERP sync are either impossible or stitched together from third-party widgets. The site lives on someone else's platform, and you usually can't fully move it elsewhere: migrating means building it again.
WordPress: the classic CMS for corporate sites and stores
A CMS is a content management system: content is separated from code, and the site has an admin panel. WordPress is the most widely used CMS in the world, from blogs to corporate sites to online stores built on WooCommerce.
Strengths:
- thousands of ready-made plugins: catalog, cart, payments, shipping, search, forms;
- off-the-shelf connectors for popular CRMs, payment providers, and ERP systems;
- an admin panel many marketers already know;
- a huge pool of developers, so it's easier to hand the site over to another team.
What to keep in mind. The core is free, but premium themes and plugins usually come with annual licenses. Ready-made plugins speed up development, but a custom interface or business logic needs custom work, and the more of it there is, the harder updates become. A site stitched together from dozens of plugins by different authors is harder to update and secure. Fast load times on WordPress are achievable, but they take deliberate tuning.
WordPress is a sensible choice for a corporate site or online store where the catalog, integrations, and a familiar admin matter most.
What about other CMSs?
WordPress isn't the only CMS. Drupal is popular for large, complex content sites; Craft CMS is loved by design-led teams; hosted ecommerce platforms like Shopify cover a lot of online retail. Each has its own niche and community.
The logic of choosing is the same for every CMS: the more tasks ready-made modules cover, the faster the launch, but the more the site depends on what those modules can do and how well they're built. So when choosing a CMS, look beyond the license price at how much custom work you'll actually need and who will maintain the system after launch.
Next.js: modern development built around your business
Next.js is a framework built on React. It isn't a finished system with an admin panel but a tool for developers: the site is built for the task at hand, and pages can be generated ahead of time or on the server, so they open fast and are easy for search engines to index.
Strengths. Fast load times, complete freedom in design and interface, animation and interactivity without platform limits. The site is easy to connect to a web service, a customer portal, or a mobile app, because they're all built on the same stack. No license fees for the platform itself.
What to keep in mind. There's no admin panel out of the box: content is managed through a headless CMS or a dashboard built for the project. There are no ready-made store modules either, so the catalog, cart, and integrations are developed. For a simple site, Next.js can be overkill.
You don't pick Next.js because it's trendy. You pick it when the site needs speed, interface freedom, and a tight link to your business systems.
Website builder or custom development: which pays off
Comparing only launch cost is a mistake. The platform affects costs for as long as the site lives: subscriptions and licenses, the price of every change, speed (and therefore conversion and rankings), and ultimately the cost of migrating if the platform stops fitting.
A simple rule: choose the platform for the site you'll have in two years, not today's version. If there are no growth plans, a builder will honestly save you money. If the site needs to become your main source of leads, take orders, or work alongside your CRM and ERP, custom website development on a CMS or a framework pays for itself because you won't have to do it twice.
How we choose a stack
As a digital agency, we build websites end to end on Next.js, WordPress, or another stack, and we choose the platform after the first phase, discovery. First we get to know the business, the audience, and what the site has to do, look at which systems it will connect to and who will run it, and only then recommend a technology.
That's why one client gets a WordPress site synced with their ERP, while another gets a Next.js site that works alongside a customer portal and the company's internal services. Either way, the site comes with a content management panel, responsive layouts, and analytics. You can see examples in our website development projects, and read about Sphere's approach on the About page.
FAQ
What should a small business build its website on?
If you need a landing page or a simple brochure site with no integrations and want to launch fast, a website builder will do. If the site needs to grow, bring in search traffic, and connect to a CRM or ERP, it's better to choose a CMS or framework from the start so you don't have to migrate later.
WordPress or Next.js: which should I choose?
WordPress is convenient when you need a classic corporate site or store with a familiar admin panel and ready-made plugins, and your team already knows the platform. Next.js fits when speed, a custom interface, integration with a web service or app, and architectural freedom matter. The decision should follow the project's needs, not trends.
Can a site built on a website builder rank in search?
Yes: popular builders have basic SEO settings. The limits appear on larger sites, around URL control, speed, generating many pages, and fine-grained technical setup. For a site that relies on organic traffic, a CMS or framework gives you more control.
Is it hard to move off a website builder later?
Migrating almost always means a rebuild: design and content are moved over by hand, and redirects from the old URLs are set up to keep your rankings. So if you expect the site to grow, choose a platform with room to spare.
Can a marketer edit a Next.js site without a developer?
Yes, if the site is connected to a content management panel: a headless CMS or a custom admin. Then copy, news, products, and pages can be edited without a developer, just like in a classic CMS.




