Next.js developer · New Zealand
Next.js, built and shipped by a senior engineer.
For founders, agencies needing a subcontractor, and teams who already know they want React and Next.js. I’m a senior engineer with a decade in financial-services software — available for a project, an ongoing contract, or white-label subcontract work, and the code is yours to own.
In short
What a Next.js developer actually does
A Next.js developer builds web applications on Next.js — React’s production framework — using the App Router, React Server Components and TypeScript. In practice that’s a marketing site that scores in the green on Core Web Vitals, a SaaS product with authentication and billing, a customer dashboard, a headless storefront, or a migration off WordPress or an ageing Create React App. Next.js decides per route whether a page is static (SSG), regenerated on a schedule (ISR) or rendered on each request (SSR), which is why it’s the default choice when a site needs both speed and dynamic data. Hiring one in New Zealand means a senior engineer who writes the code, deploys it to Vercel, and hands you a repository you own.
What we build
What I build with Next.js
Most engagements are one of these, or a combination. If it runs on React and Next.js and someone’s business depends on it, it’s in scope.
Next.js apps on the App Router
Applications built on the current App Router — React Server Components that fetch data on the server and never ship to the client, Server Actions for mutations without a hand-written API layer, and streaming with Suspense so the page paints before every query resolves.
Fast marketing sites & landing pages
Statically generated or incrementally regenerated pages that score in the green on Core Web Vitals — real LCP, CLS and INP budgets, image optimisation and edge delivery — not a page-builder theme with a nice Lighthouse screenshot and a slow first load.
SaaS products & dashboards
The full product: authentication, role-based access, Stripe billing, multi-tenant data, an admin back-end and a dashboard that reads live from Postgres — typed end to end so the front end and the database can’t quietly drift apart.
Headless commerce & CMS
A Next.js front end on a headless back end — Sanity or a headless CMS for content, Shopify or Stripe for checkout — so editors and merchandisers work in a proper tool while the storefront stays fast and fully under your control.
Migrations off WordPress & legacy React
Moving a slow WordPress site, an ageing Create React App, or a Pages Router codebase onto the modern App Router — incrementally, route by route, without a big-bang rewrite that takes the site down or loses your search rankings.
Contract & white-label subcontract
Senior Next.js capacity for agencies and teams already at full stretch — dropping into an existing repository, or building a client project white-label under your brand, with the same code standards and no junior hand-off.
In depth
How to think about hiring a Next.js developer
What the App Router changed, and why it matters
The App Router — Next.js’s current model — moved the default from “ship a big JavaScript bundle and fetch data in the browser” to “render on the server, send HTML, and only hydrate what’s actually interactive”. React Server Components run on the server and never ship to the client, so a data-heavy page can query the database directly and send almost no JavaScript. Server Actions let you write mutations as plain functions instead of hand-rolling an API route for every form. Streaming and Suspense let the shell paint immediately while slower data fills in. The result is faster pages and less client code — but it’s a genuinely different mental model from the old Pages Router or a Create React App, which is exactly where an experienced hand saves you weeks of relearning.
SSR, SSG, ISR — which rendering strategy your site needs
Next.js’s real strength is that it decides rendering per route rather than for the whole app. A marketing page whose content rarely changes is statically generated (SSG) at build time and served from the edge — the fastest thing on the web. A page whose content changes on a schedule uses incremental static regeneration (ISR), rebuilding in the background so visitors never wait on it. A page that depends on who’s logged in, or on live data, is server-rendered (SSR) on each request. Most real sites are a mix, and picking the wrong strategy per route is where performance and hosting cost quietly go wrong. Choosing it correctly is most of what senior Next.js work actually is.
When you don’t need Next.js (or a Next.js developer)
Not every site needs this, and I’ll say so before you spend money. If you want a small brochure site your team edits themselves and that never really grows, a hosted website builder or a WordPress theme is cheaper and I’m the wrong call. If you’re building a purely client-side app with no SEO and no server needs — an internal tool behind a login — plain React on Vite is simpler than Next.js and I’ll happily point you there. Next.js earns its keep when you need server rendering for SEO or speed, a real back end, dynamic data, and a codebase that scales past a handful of pages. If your problem is smaller than that, the honest answer is a smaller tool.
Migrating off WordPress or legacy React without a rewrite
Most Next.js work isn’t greenfield — it’s a WordPress site that has grown slow and fragile, a Create React App that React itself has now deprecated, or a Pages Router codebase you want on the modern App Router. None of those need a big-bang rewrite. A migration runs route by route: stand the new Next.js app up alongside the old site, move the highest-traffic pages first, keep URLs and redirects intact so you don’t lose search rankings, and cut over once the new version is proven. You get the performance and the maintainability without the month-long outage or the “we rebuilt everything and half of it regressed” story.
Who you actually work with
Not an account manager fronting an offshore team — Isaac Vicliph, a senior software engineer with a decade shipping software in financial services, writing the Next.js and React himself. You get one accountable person from the first call to deployment, direct contact throughout, and code held to a standard someone will still be able to read in three years. It’s a deliberately small operation: fewer projects, no junior hand-off, and the person who understands your codebase is the person who wrote it. NZ-based, priced in NZD, GST-registered.
Project, contract or subcontract — and how it’s priced
There are three ways to work with me. A fixed-scope project — I scope it, quote a fixed price, build it and hand it over. An ongoing contract — senior Next.js capacity by the day or week, embedded in your team and your repository. Or white-label subcontract for agencies who’ve won the work and need someone senior to actually build it. Pricing depends on which of those it is and on the scope, so rather than publish a number that’s wrong for your project, I scope first and quote firm. Tell me what you’re building and how you’d like to work, and you’ll get a straight plan and a straight price back.
Reviewed July 2026 · written by Isaac Vicliph, Tally Digital
Questions
Frequently asked
What does a Next.js developer do?
Builds web applications with Next.js, React’s production framework — using the App Router, React Server Components and TypeScript. That covers fast marketing sites, SaaS products, dashboards, headless storefronts and migrations off WordPress or legacy React, usually deployed to Vercel. In practice it’s a senior engineer who handles rendering strategy, performance, the back end and deployment, and hands you a repository you own.
How much does it cost to hire a Next.js developer in NZ?
It depends on scope and on how you want to work — a fixed-scope project, an ongoing day-rate contract, and white-label subcontract work are priced differently, and a landing page is a very different job from a full SaaS build. I don’t publish a blanket figure because it would be misleading. Tell me what you’re building and I’ll scope it and quote a firm price before any work starts.
Can you hire a Next.js developer on a contract or subcontract basis?
Yes — that’s a large part of the work. I take fixed-scope projects, ongoing contracts where I embed in your team and repository by the day or week, and white-label subcontract work for agencies who’ve won a project and need a senior engineer to build it under their brand. Same code standards across all three.
Next.js or plain React — which do I need?
Plain React (usually on Vite) is the simpler choice for a purely client-side app with no SEO needs — an internal tool behind a login, for example. Next.js adds server rendering, routing, per-route SSG/SSR/ISR and a back-end layer, which is what you want the moment a site needs to rank in search, load fast for first-time visitors, or talk to a database. If you’re not sure, describe the app and I’ll tell you honestly which one fits.
Should I move my WordPress site to Next.js?
Only if WordPress is actually holding you back — a slow site, a fragile pile of plugins, or a front end you can’t customise the way you need. If WordPress is doing the job, keep it. When a move makes sense it’s done incrementally: highest-traffic pages first, URLs and redirects preserved so you keep your search rankings, and a cut-over once the new version is proven — not a big-bang rewrite.
Do you deploy to Vercel, and do I own everything?
Yes. Next.js apps typically deploy to Vercel, built by the same team, which handles edge delivery, ISR and preview deployments cleanly — though it can run anywhere that hosts Node. Either way you own it outright: the repository, the Vercel or hosting account, the domain and any database. It’s a mainstream stack with no proprietary lock-in, so any competent developer can pick it up.
Do you work with clients across New Zealand?
Yes. I’m a New Zealand-based engineer working with founders, companies and agencies across the country — remotely, which is how most software work happens anyway. The process is the same wherever you are: a clear scope, direct contact with the engineer writing the code, and a repository you own at the end.
Are you a developer or an agency?
A senior software engineer, working solo — not an agency and not a monthly marketing retainer. You talk to the person who designs, writes and deploys the Next.js code, every time. For agencies, that’s the whole point: senior capacity you can subcontract without adding headcount.
Tell me what you’re building with Next.js.
A new app, a rescue of a slow WordPress site, an App Router migration, or senior capacity your agency can subcontract — tell me what you’re building and how you’d like to work, and I’ll come back with a clear plan and a fixed price.