Next.js Consulting
Next.js Consultant forEU and Swiss Teams.
Ten years building production React and Next.js. I help product teams choose the right rendering strategy, pass Core Web Vitals, migrate to the App Router and ship architecture that still makes sense at scale.
- 10 years in React & Next.js
- Core Web Vitals specialist
- EU & Swiss hours overlap
Where Next.js projects go wrong
Next.js makes the easy things easy and the architectural decisions easy to defer. The cost of those deferred decisions shows up later, as slow pages, brittle data flows and rewrites nobody budgeted for.
Failing Core Web Vitals
Heavy client bundles, blocking data fetches and layout shift quietly drag down LCP and INP. The result is a site that feels slow, ranks worse and converts less, often without the team knowing which decision caused it.
The wrong rendering strategy
Static, server, client and streaming each have a place. Reaching for the wrong one - over-fetching on the server, shipping logic to the client, fighting the cache - turns Next.js from an advantage into a source of bugs.
Architecture that will not scale
Folder structure, data access and component boundaries set early decide how fast you can move at 50 routes. Get them wrong and every new feature costs more than the last.
Who I work with
I work with product teams that have a real Next.js codebase and a real deadline, not greenfield experiments.
- A scale-up whose Next.js app has outgrown its original architecture
- A team stuck part-way through a Pages Router to App Router migration
- A SaaS product failing Core Web Vitals and losing ranking or conversions
- A founder who needs a senior second opinion before committing to a rebuild
- An agency that needs Next.js depth on a client project for a few months
- An enterprise team adding React Server Components and unsure where to draw the line
How I help
Architecture review
A structured review of routing, data fetching, caching, state and component boundaries, with a written set of recommendations your team can act on. You see exactly what to keep, what to change and why.
Core Web Vitals audit
LCP, INP and CLS measured against real field data, the bottlenecks traced to specific code, and a prioritised fix list ordered by impact. Optionally I implement the fixes and verify the gains.
App Router migration plan
An incremental path from the Pages Router to the App Router and React Server Components: route-by-route sequencing, risk notes and the rendering decision for each section, so you keep shipping throughout.
Hands-on implementation
When you want the work done, not just advised, I embed in the codebase and ship the changes alongside your engineers, leaving the team able to maintain the result.
How an engagement works
Call and scope
You tell me the symptom: slow pages, a stalled migration, an architecture decision. I scope the smallest useful engagement and send a quote and timeline.
Audit and diagnosis
I work through the codebase and field data, isolate the real causes, and separate quick wins from structural changes.
Recommendations
You get a prioritised, written set of recommendations with the reasoning, so the decision holds up even after the engagement ends.
Implementation (optional)
If you want the fixes shipped, I implement them with your team and verify the result against the metrics we agreed.
Case Study
A Next.js platform built to scale
Flowrence is a healthcare platform built on Next.js and TypeScript, with the kind of architecture and performance constraints these engagements exist for: a real product, a real team and decisions that had to hold up under load. It is the type of work I bring to Next.js consulting.See selected projects →
Frequently Asked Questions
What does a Next.js consultant actually do?
I help teams make the architecture and performance decisions that are expensive to get wrong: choosing between static, server and client rendering, structuring the App Router, modelling data fetching and caching, and setting a Core Web Vitals budget. The work ranges from a one-off architecture review to hands-on implementation alongside your engineers.
Can you help us migrate from the Pages Router to the App Router?
Yes. I plan App Router and React Server Components migrations as an incremental path rather than a rewrite, so you keep shipping while moving route by route. You get a migration plan with sequencing, risk notes and the rendering strategy for each section before any code changes.
Our Next.js site is slow. Can you fix Core Web Vitals?
That is one of the most common reasons teams reach out. I audit LCP, INP and CLS with real field data, find the bottlenecks (oversized client bundles, blocking data fetches, layout shift, unoptimised images) and deliver a prioritised fix list with the highest-impact items first. I can implement the fixes or hand the list to your team.
Do you work as an advisor or do you write code too?
Both. Some clients want a senior second opinion on architecture and a written review. Others want me embedded in the codebase shipping the changes. I am comfortable moving between advisory and hands-on as the engagement needs.
How do you work with EU and Swiss teams remotely?
I am based in Poland and work in overlapping Central European hours, so daily collaboration with Swiss and EU teams is straightforward. I invoice cleanly from an EU entity, which keeps cross-border contracts simple for clients in the EU and EEA.
How do we start?
Book a call and tell me where it hurts: performance, a stalled migration, an architecture decision or a delivery deadline. I will scope the smallest useful engagement, usually an architecture or performance audit, and you decide whether to continue into implementation from there.
Get a senior read on your Next.js app
Tell me where it hurts - performance, a migration or an architecture decision. I will reply with a scoped engagement and a timeline within 24 hours.
Book a Next.js Consultation