Next.js consultancy
An editor publishes but the page shows old copy. A menu loads slowly because it sends too much JavaScript. A route works locally and fails after deployment. I review the caching, rendering and runtime decisions behind these problems.
I have led Next.js redesigns, large catalogs moved to on-demand generation, and multilingual sites with live data. Send the planned build, slow route, migration or pull request. I send a list of changes in the order to make them.
100 USDexcl. VAT
- An architecture recommendation before you commit: rendering strategy per route, data fetching, caching, and how the CMS plugs in.
- A Core Web Vitals pass with each slow metric traced to its cause, fixes ordered by impact.
- A prioritized review of a pull request, a component boundary or a caching decision before it ships.
Symptoms
Problems I can trace
Published an hour ago, still showing the old copy
I check which routes are prerendered, revalidate on a webhook or fetch per request, then document the choice for each route.
The interaction feels slow, and the score says the page is fine
I trace slow interactions to their render path and identify components that can move work to the server.
It works locally and breaks once deployed
I trace runtime errors or hydration mismatches to the failing route and name the change needed in production.
FAQ
Scope
What does this cover?
Architecture before a build or a migration: which routes are static, which render on demand, how data is fetched and cached. Performance, each Core Web Vitals metric traced to its render path. Code review on pull requests, boundaries and caching. And the AGENTS.md that lets a new developer or an agent ship a first change.
Does this end at recommendations, or do you ship the changes?
It ends at a change list your team applies. If you want me to change the code - execute a migration, move a boundary - I write the changes up as a roadmap of tasks, each estimated in hours, and carry them out as you approve them, at 75 USD an hour excl. VAT.
How is the time scoped?
I read the code first, then reply with a fixed number of hours at 100 USD an hour excl. VAT, with a 300 USD minimum. A pull request or a single caching question is usually a few hours, an architecture review or a migration plan a day or two. Nothing starts before you agree the hours.
Something else on your mind? The chatbot answers questions about my work from this site. Ask in English, Polish or your own language.
Ask the agentRelated reviews
The CMS affects caching
The content your CMS lets editors publish affects what each route can cache. I also review Sanity, Storyblok and Astro projects.
In practice
How a Next.js review runs
Send the repo and the question
Read access and a sentence on what is at stake.
I read the code first
The route segments, data fetching and client/server split your question touches, then a fixed number of hours at 100 USD an hour excl. VAT, with a 300 USD minimum.
You get a change list
What to change and in what order, each item naming the route or component it touches.
Next.js consultancy
100 USDexcl. VAT
- An architecture recommendation before you commit: rendering, data, caching, CMS.
- A Core Web Vitals pass, each slow metric traced to its cause.
- A prioritized review of a pull request, a component boundary or a caching decision.
- A migration plan reviewed before the cutover.
- The docs and rules a new developer or a coding agent needs to ship a first change.
Get in touch
Send the question
Send the repository and a sentence on what is at stake - the route serving stale content, the interaction that drags, or the failure that only appears once deployed.
Working with an AI agent?