Why We Build Business Sites in Next.js (When HubSpot Isn't the Fit)

By Nikola, founder at ZEROX. We build HubSpot CMS themes and custom React/Next.js sites side by side, so "which one should we use" is a question we answer most weeks. Last updated July 2026.

When a company asks us for a custom Next.js business website, they've usually already decided custom is better. Roughly half the time it isn't, and we say so on the scoping call. The other half have a real reason a CMS will fight them, and for them a hand-built Next.js site is the right tool. This post is the reasoning we walk them through: where a custom React front end genuinely beats a CMS like HubSpot or WordPress, where it loses, and how to tell which side of the line you're on.

We aren't neutral in the abstract, we sell both. We're neutral in the way that matters: we'd rather build the right thing once than the wrong thing twice.

Where a Next.js business website wins

Next.js is a React framework that renders pages on the server (SSR), pre-builds them at deploy time (SSG), or refreshes them on a schedule (ISR). That rendering model is why it's a serious choice for a marketing site, not just an app framework. In practice it buys you:

• Performance you control end to end. No theme, no plugin stack, no page-builder markup padding the payload. You ship the HTML, CSS, and JavaScript you actually wrote, which makes Core Web Vitals something you engineer rather than hope for.
• Total design freedom. Any layout, any animation, any interaction. Nothing has to survive a template system or a drag-and-drop editor's assumptions. If the design exists in Figma, it can exist on the page exactly.
• App-like interactivity. Configurators, calculators, gated tools, live pricing, customer-facing dashboards, the parts of a site that are really software, where a CMS starts to strain.
• SEO through real server rendering. Search engines get fully formed HTML on the first request, plus clean metadata, structured data, and fast loads, the crawlability of a static site with the flexibility of an app.
• Headless content. Pull copy from a headless CMS (Sanity, Contentful, or even HubSpot's own content APIs) so editors keep a friendly interface while the front end stays fully custom.

The honest trade-off: nobody edits it like HubSpot

Here's the part the sales-driven articles skip. On HubSpot, a marketer opens a page, drags a module, edits text inline, publishes, and cannot break the layout. That safety and independence is the entire point of a CMS, and a plain Next.js site does not have it. Content changes are code changes. A new landing page, a copy tweak, a swapped image, by default those go through a developer and a deploy.

For an engineering-led company shipping a few considered pages a quarter, that's fine, sometimes preferable. For a marketing team that launches campaign pages weekly and wants to A/B test a headline on Tuesday afternoon without filing a ticket, it's friction that compounds. If that's your team, HubSpot's drag-and-drop isn't a limitation to work around, it's the feature you're buying, and we'll tell you to buy it. Our HubSpot CMS vs WordPress comparison works through that same editor-independence question in more depth.

Headless: how you get most of both

The trade-off above isn't all-or-nothing. The common middle path is a headless build: a custom Next.js front end for speed and design, wired to a content system marketers actually log into.

• Editors manage copy, blog posts, and images in a headless CMS with a real editing UI.
• The Next.js front end reads that content at build time or on demand and renders it fast.
• Marketing gets meaningful independence for content; engineering keeps full control of presentation.

It's more moving parts than a pure CMS or a static site, and costs more to set up. But for a company that wants a custom front end without turning every wording change into a deploy, it's usually the honest answer. It also sits next to real product work, if your site is edging toward an application, our web app development practice is the same stack, so the marketing site and the product don't drift into two codebases.

When to choose which

Choose a custom Next.js build if:

• Design and brand differentiation are competitive advantages, not nice-to-haves.
• The site includes app-like features, tools, configurators, portals, calculators.
• Your team is engineering-led and comfortable owning the site in code.
• Performance is a first-class requirement, not an afterthought.

Choose HubSpot or another CMS if:

• Marketing needs to own and edit the site day to day without developers.
• You already run HubSpot CRM and want native forms, attribution, and lead data.
• The site is mostly standard marketing pages plus a blog.
• You'd rather not maintain hosting, builds, and dependencies at all.

Most B2B marketing sites, honestly, are better served by a CMS. The Next.js case gets strong when the site is unusually design-forward, unusually interactive, or quietly turning into a product.

FAQ

Is Next.js good for SEO?

Yes. Server-side rendering and static generation hand search engines complete HTML on the first request, and you control metadata, structured data, and page speed directly. Rendering isn't usually why a site ranks or doesn't, but Next.js removes the technical excuses.

Can marketers edit a Next.js website?

Not out of the box, content changes are code changes. Pair it with a headless CMS and editors get a friendly interface for copy and blog posts while the front end stays custom.

Is a custom Next.js site more expensive than HubSpot?

Upfront, usually yes, because you're building rather than configuring. Over time it depends on how much custom work you'd have fought a CMS to deliver anyway. We give a fixed quote after a scoping call so the number isn't a surprise.

Do we own the code when you build it?

Yes. Every custom build we ship is yours, no lock-in, no proprietary platform holding your site hostage.

Should every business use Next.js?

No. If your team is marketing-led and the site is standard pages plus a blog, a CMS will serve you better and cheaper. Next.js earns its place when design, interactivity, or performance are genuinely core to the business.

Want a straight answer on custom vs CMS?

Tell us what the site needs to do and who edits it, and we'll tell you honestly whether a custom Next.js build, HubSpot, or a headless mix is the right fit, even when that means talking you out of the more expensive option. Start a conversation on our contact page, or read more about how we build under web app development.