Production Next.js, built by the same person who designs it.

Next.js is the production framework for React. It is maintained by Vercel and is the default choice in the React documentation for new full-stack applications. The current programming model is the App Router with React Server Components, which colocates server-side data fetching with the components that render it and ships almost no unused JavaScript to the browser by default (Next.js docs, 2026).

When most agencies say Next.js development, they mean a one-page or multi-page marketing site that happens to be built on Next.js instead of WordPress. That is a small slice of what the framework is for. The work I do under this header is custom application development: server-rendered pages, typed data layers, custom authentication where it is needed, integrations with the third-party services a business actually uses, and a maintenance surface I will still understand a year from now.

The proof points are public. This site runs on Next.js 16. Pathlight, the website intelligence product I built, runs on the same framework. The two systems share a codebase, a deployment pipeline, and a Postgres database. That is the level I work at, and it is the level of system I am proposing when you hire me. For a worked example in a specific vertical, the auto service industry page covers the Star Auto Service rebuild in production detail.

Next.js is the right call when at least two of these are true. You want full ownership of your code, not a hosted-platform license you rent. Your buyers do real research before contacting you, which means the site needs to rank in Google and answer questions confidently. You have or expect to have integrations beyond a contact form, such as scheduling, internal dashboards, customer portals, or a custom CRM you do not want to glue together with third-party widgets. You expect the site to evolve over multiple years, not get rebuilt every twenty-four months.

Next.js is the wrong call when you genuinely need a brochure. Squarespace and Wix are real products and they are good at what they do. If your entire internet strategy is a one-page address, hours, and a phone number, paying for a custom application from a studio is straightforward overspending and I will tell you that directly. The honest framing here is that most local service businesses fall on the line between the two, and the right answer depends on what you plan to do with the site over the next five years, not what you want it to look like next month. The longer reference on what each tier should actually cost is What a Website Should Cost in 2026.

A second wrong-fit case is the marketing-blog-only site. If the entire purpose is a content stream and you do not need any custom server logic, a static-site generator like Astro or Hugo will ship faster, cost less to host, and require less ongoing care than a full Next.js application. I will say so when that is what fits.

Service businesses get four things from this stack that they struggle to get from page-builder platforms. Server-side rendering and Server Components mean the HTML the search engine sees is the HTML the customer sees, with no client-side JavaScript required to read your services and prices. That posture passes Core Web Vitals by default rather than as an afterthought, which Google has used as a ranking input since the page experience update became a rolling-out signal in mid-2021 (Google Search Central, 2021). When Vodafone Italy rebuilt one of their pages on Next.js and improved LCP by thirty-one percent, sales rose by eight percent and lead rate by fifteen percent in their measurement window (Google, 2022).

The second benefit is integration depth. The same codebase that renders your marketing pages can run your booking flow, your admin dashboard, your customer login, and the queue that sends your transactional email. You do not need to glue together five vendors and pay each of them a monthly fee that adds up to more than a principal architect's annual retainer. You also do not need a plugin marketplace, which is the failure mode that takes most WordPress sites down.

The third benefit is type safety end to end. With TypeScript and Drizzle or Prisma, the shape of your database matches the shape of your forms, which matches the shape of your API responses. A rename in one place propagates through the whole system at compile time, which is why a one-person studio can maintain a system over many years without it drifting into chaos.

The fourth benefit is the one that matters most for a small business: the framework is well-supported and is not going to be abandoned. According to the State of JS 2024 survey of more than fifteen thousand developers, Next.js retained the top spot for metaframework usage and the highest retention rate in its category (Devographics, 2024). The HTTP Archive Web Almanac's 2024 CMS and frameworks chapters track its adoption growth across the public web (HTTP Archive, 2024). The downside risk of building on Next.js, on Vercel infrastructure, with first-party React, is lower than the downside risk of betting on a niche stack.

Three honest tradeoffs. First, this is not the cheapest option, and the cheapest option is sometimes the right one. Templated builds on Squarespace start under one thousand dollars in setup. Custom Next.js work under my Starter tier starts at four thousand five hundred dollars and scales up from there based on scope, with the full tier breakdown published on the pricing page. If your ceiling is the templated option, choose it and spend the difference on advertising.

Second, this is not the fastest path to a public URL. A custom Next.js application takes weeks of design and engineering, where a template-based site can be online inside a weekend. The speed gap is real and the right answer is not always to wait. If your deadline is two weeks, hire a templater and revisit the custom build later when the timing is right. If the deadline pressure is coming from a site that is quietly losing leads right now, the performance audit page covers the audit-and-fix path that ships in two weeks instead of a full rebuild quarter.

Third, the dependency surface is real. A modern Next.js application pulls in React, the framework runtime, TypeScript, a build toolchain, and whatever client libraries you choose for data access, authentication, and email. Each of those has its own release cadence and its own breaking-change schedule. Maintenance is part of the engagement, not an afterthought. I budget for it, and I price retainers around it, because pretending it does not exist is what produces the four-year-old framework version on a live site that an attacker eventually finds.