Hiring someone to build in Next.js? What to check before you sign

How to choose a Next.js development company or developer: what to check in their work, hosting choices, questions to ask, red flags and public rate data.

Summarize with
Line drawing of a bank card, a shield with a tick and a padlock with a green keyhole, standing on one line

A good Next.js development company, or developer, proves three things before you sign: their Next.js sites pass Core Web Vitals on real phones, they can explain how they use the App Router, Server Components and caching on your project, and they will hand over a codebase, hosting and CMS that sit in your company's name. Ask to see live work and measure it yourself, ask where they would host it and why, ask how they patched the December 2025 React Server Components vulnerability, and get one written scope with a fixed price. A list of company names can't tell you any of that; the questions below can.

I'm a design engineer: I design products and build them in TypeScript, React and Next.js. I'm not a company, and I compete with companies for the same projects, so I'll say plainly where a company is the better choice. The build side of my work is on my development page.

What a Next.js development company should deliver

"Next.js development" can mean a marketing site with a CMS, a SaaS dashboard, an online shop or a rebuild. Before you compare anyone, write down which you need and what's in scope:

  • Design. Does the company design the screens, or build from your Figma file? If design sits elsewhere, ask who decides when a screen and the code disagree.
  • The build. Pages, components, forms, sign-in, payments, search, the admin side.
  • Content. Which CMS, who sets it up, and whether your team can edit every word without a developer.
  • Hosting and operations. Where it runs, who pays the bill, who watches errors and who applies security updates after launch.
  • Handover. The repository, documentation, environment variables and a walkthrough.

A quote that skips any of these grows later.

What to check in their Next.js work

Core Web Vitals on real sites

Google's Web Vitals guidance sets the "good" bar at a Largest Contentful Paint of 2.5 seconds or less, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. Run two or three of their live sites through PageSpeed Insights on mobile, and ask about any that fail. My post on improving INP in Next.js shows what fixing the slowest of the three involves.

App Router and Server Components

The Next.js docs say layouts and pages are Server Components by default, and Client Components are for state, event handlers, effects and browser APIs. Ask where the line sits on a page like yours. A good answer: content renders on the server, and only interactive parts (a menu, a filter, a form) ship JavaScript. A worrying one marks whole pages as client code because it was quicker.

Caching

Caching changed in recent versions. The Next.js caching docs now describe Cache Components, turned on with cacheComponents: true, with a separate guide for the previous model. Ask which model they use, what gets cached on your project, and how an edit in the CMS reaches the live page. "We'll turn caching off to be safe" means slower pages and bigger bills.

Security updates

On 3 December 2025, Next.js published CVE-2025-66478, a CVSS 10.0 flaw in the React Server Components protocol that could allow remote code execution in unpatched App Router apps on Next.js 15 and 16. The advisory said there was no workaround besides upgrading, and recommended rotating secrets for apps that were online and unpatched by 4 December. Ask any candidate what they did that week. Also check the Next.js support policy: on 10 November 2026 it lists 16.x as Active LTS and 15.x in Maintenance LTS, with security releases for 15 through 31 January 2027. A new build should start on a supported version.

Accessibility and SEO

WCAG 2.2 is the current W3C standard for accessible web content; ask which level they test to and how. For search, check that the text is in the HTML the server sends and each page has its own title and description. On a rebuild, ask how they'll keep or redirect every URL.

Where it's hosted: Vercel, Cloudflare or your own server

The Next.js deployment docs list four routes: a Node.js server and a Docker container support all features, a static export has limited support, and adapters vary by platform.

OptionWhat the official docs sayWorth asking
VercelA verified adapter in the Next.js docs. Vercel's pricing page says the Hobby plan is for personal, non-commercial use, and lists Pro at $20 a monthWhat happens to the bill when traffic grows?
Cloudflare WorkersNot yet a verified adapter; Cloudflare offers its own integration. Its Next.js guide now recommends vinext by default and keeps OpenNext for existing apps that can't move yet. OpenNext's docs say Node Middleware isn't supported yetWhich adapter, and which Next.js features won't work?
Your own Node.js server or DockerAll features supportedWho patches the server and watches it at night?
Static exportLimited: no features that need a serverIs the site truly static, and will it stay that way?

The table is dated 10 November 2026; prices and adapter support change often. No option suits every project, so ask whoever recommends one to explain the trade-off for yours.

Questions to ask a Next.js development company

  1. Which live Next.js sites did you build, and can I run them through PageSpeed Insights now?
  2. Who exactly writes the code, and will they be on calls with me?
  3. Where would you host this, and what would it cost each month at our expected traffic?
  4. Which CMS do you suggest, and can my team edit every page without you?
  5. Who owns the repository, hosting, domain and API keys, from day one?
  6. What do you hand over at the end, and what does support look like after launch?

Add the technical checks above: Server Components, caching, security updates and accessibility.

If you're moving from a Figma design, also ask how they keep the build matching it. My post on Figma to Next.js covers how I do that, with tokens and components named the same in both.

Red flags

  • No live sites to measure, only screenshots or a mock-up gallery.
  • Every page marked as client code, or no clear answer on caching.
  • Hosting in their account with no plan to move it to yours.
  • A price before a scope. Without questions about content, integrations and traffic, it's a guess.
  • "We'll handle SEO later" on a rebuild of a site that already ranks.
  • Nobody can name your developer. Meet the people who'll build it.

Engagement models and public rate data

Three models are common: a fixed price for a written scope, time and materials billed by the hour, and a dedicated team billed by the month. Fixed price puts the scope risk on the builder; hourly puts it on you.

For rates, the most traceable public figures I found are in Clutch's software development pricing guide, updated 21 September 2026 and read on 10 November 2026. It covers all software projects reviewed on Clutch, not Next.js alone:

MeasureClutch figure
Average hourly rate$25 to $49
Most common project size$10,000 to $49,999
Average project cost$132,480.29
Average monthly cost$10,209.39
Average hourly rate, United States$50 to $99
Average hourly rate, Canada and Australia$100 to $149
Average hourly rate, India, Philippines, Ukraine, Mexico$25 to $49

A few large projects pull the average far above the common band. Use these as a reference, not a price list.

A company, or a design engineer who designs and builds

A Next.js development company is the better fit when you need many people at once: several developers in parallel, a dedicated QA team, cover across time zones, or a large build with a hard date. It also has more people to replace anyone who leaves.

One design engineer fits when design and build should stay close: a marketing site, a SaaS front end or a product where the screens matter as much as the code. There's no handoff between a design team and a build team, so details survive into production. The limit is capacity: one person can only run so many projects, and you should ask how cover works.

My design engineering page explains that way of working.

How I'd approach your Next.js project

  1. A free 30 minute intro call about what the site or app must do, who edits it and where it should be hosted.
  2. A written scope and one fixed quote for the whole project. No retainer, nothing billed by the hour.
  3. Design in Figma, in weekly sprints, with a written update in Slack every 48 hours and a review call each week. A design system with tokens and components named the same in Figma and in code.
  4. The build in Next.js and TypeScript, with pages rendered on the server and client code only where something moves. I use AI coding tools where they save time, and I review every change.
  5. Launch and handover to accounts in your company's name.

As an example of the design side, I designed the Fintus marketing website, a banking and saving platform: home, features, about, blog, article and FAQ pages on desktop, tablet and mobile, ending in a design handover to developers. A Next.js build should start from a file like that: every page, every breakpoint, one style guide.

Frequently asked questions

How do I choose a Next.js development company?

Measure their live sites against Core Web Vitals, ask about Server Components, caching, hosting and security updates, and confirm you'll own every account. Then compare written scopes, not hourly rates.

How much does a Next.js development company charge?

Clutch's software development pricing guide, updated 21 September 2026, lists an average hourly rate of $25 to $49 and a most common project size of $10,000 to $49,999, across all software projects. Your price depends on scope, integrations and content.

Do I need to host a Next.js site on Vercel?

No. The Next.js docs list a Node.js server, Docker, static export and platform adapters. Vercel is a verified adapter; Cloudflare, Netlify and others offer their own integrations with varying feature support.

Is Next.js good for SEO?

It can be, because pages can render on the server and send full HTML. A builder can still undo that by rendering text in the browser, so check the HTML of their live sites.

Should I hire a Next.js developer or a company?

A company suits large builds needing many people at once; a design engineer suits projects where design and code should stay together. Both should pass the same checks.

Can you design and build my Next.js site?

Yes. I design in Figma and build in Next.js and TypeScript, with a design system named the same in both, and hand everything over in your company's name.

Sources and method

I read every source on 10 November 2026. The pages ranking for "nextjs development company" are mostly company service pages or ranked lists with no stated method, so I give questions, not names. Prices and platform support change often; check them before you decide.

  • Google, web.dev, Web Vitals, date read 10 November 2026: web.dev
  • Next.js docs, Server and Client Components, date read 10 November 2026: nextjs.org
  • Next.js docs, Caching, date read 10 November 2026: nextjs.org
  • Next.js, Security Advisory CVE-2025-66478 (3 December 2025), date read 10 November 2026: nextjs.org
  • Next.js, support policy, date read 10 November 2026: nextjs.org
  • Next.js docs, Deploying, date read 10 November 2026: nextjs.org
  • Vercel, pricing, date read 10 November 2026: vercel.com
  • Cloudflare, Next.js on Workers guide, date read 10 November 2026: developers.cloudflare.com
  • OpenNext, Cloudflare adapter docs, date read 10 November 2026: opennext.js.org
  • W3C, Web Content Accessibility Guidelines 2.2, date read 10 November 2026: w3.org
  • Clutch, software development pricing guide (updated 21 September 2026), date read 10 November 2026: clutch.co

If you're choosing who builds your Next.js site or app and want it designed and built by one person, book a free 30 minute intro call. After it, you get a written scope and one fixed quote, with every account in your company's name.

Tags: Next.js development company, Next.js, Hiring a developer, Development, Design engineering

Keep reading

Let’s look at your product.

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call