Next.js is a React framework maintained by Vercel for building web applications that combine server-rendered HTML, static site generation, and client-side React in a single codebase. It was first released in 2016 and has become the default professional choice for marketing sites, dashboards, and content-heavy applications. Next.js 16, the current major version as of 2026, uses the App Router — a file-system-based routing model where every folder inside /app is a URL, and every page.tsx is the page that URL renders. Pages are server components by default, which means the HTML ships ready-rendered, images and fonts are optimised at build time, and JavaScript bundles stay small because nothing client-side ships unless it has to. For small businesses, Next.js is overkill if you need a three-page brochure site and exactly right if you want performance, ownership, and the option to grow beyond a brochure later.
What a real Next.js build looks like
This site is Next.js 16 with React 19, TypeScript strict, and Tailwind CSS 4, deployed on Vercel's edge network. Total initial JavaScript on the homepage is under 90 KB gzipped. Every page is statically generated at build time. The whole codebase lives in a GitHub repository the client owns, and any Next.js developer on earth can pick it up and continue. If the client outgrows me, they do not outgrow the framework.
Why framework choice is a hiring decision
Framework choice is usually the least interesting decision on a site, but it becomes the most expensive decision two years later when you try to hire. React and Next.js are the most-recruited combination in front-end — picking a more exotic framework, or a no-code builder, means a narrower developer pool and a higher migration cost. Picking Next.js is the least-regret technical decision most small businesses can make.
Related terms
Bespoke, live in seven days.
£1,000 flat. Paid upfront. Full refund if I miss day seven. Code, hosting, and domain all in your name.