Freelance Next.js Developer in the Netherlands

Who it's for: B2B SaaS, marketing agencies and SME platforms

I work with clients where Next.js is the right choice and is taken seriously. Think B2B SaaS teams building a new app or migrating a legacy React app, marketing and web agencies needing external Next.js capacity for client projects, scale-ups moving their marketing site to Vercel or Cloudflare, and SMEs ready for a fast, SEO-resilient website after years on WordPress. Not my audience: projects where Next.js was picked because "it's trendy" for a static brochure site that would be fine on Astro or plain HTML - there's no specialist value-add there.

The stack I work with daily

Not ad-hoc Stack Overflow fixes but real production experience with the modern Next.js toolchain. These are the tools I touch every working day:

• Next.js 14 / 15 / 16 (App Router) - Server Components, streaming, parallel routes, intercepting routes, dynamic vs static rendering, route handlers, middleware and the full caching model (fetch cache, full route cache, Data Cache).
• React 18 / 19 - Server Components, Suspense, the use() hook, Actions, useFormState, useOptimistic. Familiar with the migration paths between versions.
• TypeScript (strict) - End-to-end type safety with Drizzle ORM or Prisma, type-safe API routes, generated types from databases and OpenAPI specs.
• Tailwind CSS v4 + design tokens - Modern responsive design without the CSS-in-JS overhead. Dark mode, custom themes, container queries.
• next-intl + hreflang - Multi-language sites with locale-prefix routing, correct hreflang and x-default tags. Five languages on Salonnare, two languages on vaniersel.dev.
• Stripe, Resend, Cloudflare - Stripe Checkout + Subscriptions + Connect, transactional email via Resend (per-tenant DKIM), Cloudflare as CDN + image resizing + DNS API.
• Deployment - Vercel, Cloudflare Pages, self-hosted Docker - Three deploy models, three different trade-offs. Salonnare runs self-hosted on Hetzner with Docker Compose; this site runs behind Cloudflare. I help pick what fits your scale.

Specialisations where generalists get stuck

Next.js is easy to start with but unforgiving in the details. These are the areas where many teams get stuck and where specialisation makes the difference:

Recent Next.js production work

Not anonymous: these are live projects you can click on, measure performance on, and assess code quality of.

• Salonnare - Multi-tenant SaaS platform for beauty salons - bookings, POS, inventory, CRM, loyalty and marketing in one Next.js + PostgreSQL + Stripe stack. Five languages, 50+ tenants, multi-location support. Live in beta since April 2026.
• vaniersel.dev - This site - Next.js 16, App Router, two locales (NL/EN), MDX blog, programmatic local landing pages for SEO, Cloudflare edge cache. Lighthouse 95-100 by default on mobile.
• Dyola's Beauty Boutique - Responsive salon site delivered in one week, replacing an outdated site from a previous supplier. Next.js + Sanity headless CMS for self-managed content.

How it works

1. Intro call (free, 30 min): Video call wherever you are. I ask concrete questions about your stack, goals, deadlines and team setup. By the end you know whether I'm the right fit and have a first estimate of scope and approach.
2. Fixed price or day rate: For well-scoped projects a fixed price within 2-3 working days of the intake. For open-ended work (audit, advisory, retainer) a day rate with a budget cap. No surprise invoices after the fact.
3. Build with staging + daily visibility: You get a staging URL, a GitHub repo (under your organisation if preferred) and short daily-summary updates. Tests run in CI; deploys go via Vercel or Cloudflare Pages, or self-hosted if you prefer.
4. Deploy, monitoring and handover: Launch including domain, SSL, monitoring (Sentry, Web Vitals to GA4) and documentation. Small changes free for the first month. Optional retainer afterwards for continued support.

Rates and availability

Landing pages from €250 fixed. Full Next.js projects (5-15 pages or MVP applications) typically €1,500 - €15,000 depending on scope. For hourly work, retainer or staff augmentation: request a quote. Availability: typically 2-3 working days per week available for new projects, with a 1-2 week lead time before the first sprint.

Frequently asked questions

Do you work remote or on site?

Remote by default - that works fine for clients across the Netherlands, Belgium and the EU. For kick-offs, architecture sessions or stakeholder alignment I'm happy to come on site in Noord-Brabant and the Randstad. Beyond that, on-site work is billed with travel expenses.

Which Next.js versions do you work with?

Production experience with Next.js 13 (Pages and App Router), 14, 15 and 16. Migrations between versions including breaking changes (caching model, async cookies, async params) are a standard part of my work. For new projects I default to the latest stable - no canary builds in production.

How much does a Next.js project cost?

Strongly depends on scope. A marketing site of 5-10 pages with CMS integration is typically €1,500 - €5,000. A SaaS MVP €15,000 - €40,000. An audit of an existing codebase with recommendations €500 - €2,000. You always get a fixed price up front after a short intake. Pair-programming or office hours can be billed hourly.

Do you provide maintenance after launch?

Yes, optional. The first month after launch small changes are free. After that maintenance can be a retainer (fixed monthly hours, lower rate), per ticket, or per hour. Hosting via a professional web host is typically €150 per year - no mandatory monthly contracts like many agencies impose.

Which hosting do you recommend for a Next.js site?

Three options depending on your profile: Vercel for simplicity (auto-deploy, perfect Next.js integration, easy to scale), Cloudflare Pages for budget-conscious clients with high traffic (generous free tier, fast edge), or self-hosted via Docker on Hetzner or a DigitalOcean droplet for maximum control and GDPR comfort. I help pick what fits your scale and compliance needs.

Do you work TypeScript-only or also plain JavaScript?

TypeScript strict mode is my default - end-to-end types from the database (Drizzle or Prisma) into the React components. For existing JavaScript projects I can work with JSDoc typing or a gradual TypeScript migration. Plain JavaScript without typing I don't recommend for new projects.

Can you train or mentor my team during a migration?

Yes. Beyond building I also do code reviews, architecture sessions and workshops on App Router, Server Components, caching and performance. For teams that want to build internal Next.js knowledge I can mentor part-time via a retainer (1-2 days a week) or run a focused 1-3 day workshop.