What is the difference between a Next.js developer and a React developer?
React is a library for building UI components; Next.js is the meta-framework around it, with routing, server-side rendering, static site generation, image optimisation, edge functions and an opinionated project structure. Every good Next.js developer is also a React developer, but the reverse doesn't automatically hold. When you need SSR, SEO or a mixed rendering strategy, choose Next.js experience explicitly; for a purely client-side dashboard, vanilla React is enough.
Do you work with the App Router or the Pages Router?
The App Router has been stable since Next.js 13 and the recommended approach for new projects since 14, with server components, server actions and a clearer split between server and client code. We build new applications in the App Router by default. For existing Pages Router projects, we do a phased migration as long as the business case justifies it, or we happily maintain the Pages Router codebase without a forced migration. We don't force a rebuild where it isn't necessary.
SSR, SSG or ISR: how do you choose?
We decide the rendering strategy per route. SSG for pages whose content rarely changes, ISR for pages that need to be revalidated periodically or on demand (product pages, case studies, blog), SSR for pages that depend on the user or live data per request, and client-side rendering for interactive dashboards after login. It isn't an all-or-nothing choice; within one application we mix these patterns at route level to balance performance and data freshness.
Vercel or self-hosted: what do you recommend?
Vercel is the path of least resistance for a Next.js application and provides preview deploys, edge functions and image optimisation out of the box. For many clients that's the right choice. For organisations with strict data residency requirements, their own Kubernetes platforms, or a cost structure that matters at larger scale, we host Next.js via Docker on AWS, GCP, Azure or your own platform: a standalone build, image optimisation via a proxy or a third-party optimiser, and edge functions replaced by your own CDN layer. We discuss the scenario honestly up front; we're not religious about Vercel.
What is the minimum lead time to bring in a Next.js developer?
For a team augmentation role, we can often have someone start within a few weeks, depending on the requested stack mix and seniority level. For a project-based engagement with a scoping phase, it takes slightly longer because we first produce a scope document and sprint planning. We'll be honest in the introductory call about what is realistic for your timing.
Which contract type do you use: fixed or flexible?
Both are possible. For dedicated developers and team augmentation, we work with an hourly rate and a minimum weekly commitment, cancellable monthly. For project-based scope, we agree a fixed contract based on a scope document with deliverables and a sprint budget. No multi-year lock-ins and no mandatory minimum contract term of years.
Do you work with a Dutch team?
The Next.js team works from the Netherlands in the Dutch time zone. Communication can be in Dutch or English, whichever you prefer. No offshore handover, no 24-hour cycles, no language barriers in pull-request reviews or stand-ups. If a production incident occurs, someone is available immediately during working days, with no time-zone delay.
What happens if the developer leaves halfway through the project?
That is exactly why we work with code review by a fellow senior. If someone leaves or is off sick for a longer period, the second senior is already active in the codebase and can take over after a short handover. So you don't come to a standstill. For longer engagements, we run a more formal knowledge-transfer session in which the successor is brought up to speed, without your own team having to do it.
How is knowledge transferred at the end?
A standard part of every engagement: a runbook with operational instructions, an architecture document explaining the non-trivial choices (why a server component here, why a client component there, which rendering strategy per route), optionally Storybook stories for components, and walkthrough sessions with your own team or successor. Preferably in the final sprints of the engagement, not on the very last day of the collaboration.
How is the price determined?
For team augmentation and dedicated developers, we charge an hourly rate depending on seniority (mid-level, senior, lead). For project-based scope, we charge per sprint or a fixed total budget based on a scope document. We share rates openly during the introductory call: no hidden tiers, no penalty clauses and no surprises halfway through.
Do you also do full-stack work, or only front-end?
Both. Many of our Next.js developers work full-stack: server actions, API routes and data access via Prisma live in the same codebase as the UI. For heavier backend requirements — a separate Python API for ML, a Node.js microservice for pricing, a Go service for high throughput — we combine with a
full-stack developer or a dedicated backend developer.
Who owns the code?
You do. The code is written in your Git repository under your account. The IP rights to everything built on commission belong to you, set out in the contract. Any open-source libraries we use are clearly documented, including their licences, so your own team or an auditor can easily review them later.