> Hourly advisory on caching, the App Router server/client boundary, and edge middleware for a Next.js project.

Canonical: https://augustynglowacki.com/services/nextjs-consultancy/

# Next.js consultancy

You are about to pick a caching strategy, debug a hydration mismatch, or decide what a middleware function is actually allowed to do at the edge. Book the hours and I review that one decision with you.

Next.js is one of the two frameworks I build production sites in at Bejamas, alongside Astro - see [Agentic coding consultancy](/services/agentic-coding-consultancy/) for the general architecture and code review. This page is scoped narrower: the App Router's server/client boundary, caching, and edge runtime limits, hour by hour.

[Book time](#lead-form)

## Questions, answered

### What does this cover?

Fetch caching and revalidation configuration when a route serves stale data or invalidates more often than it should, the Server Component/Client Component boundary when a page ships more JavaScript than its content needs, and a middleware function's edge runtime constraints before it fails in a way local development never showed you. **A hydration mismatch almost always traces back to one of these three**, not to the symptom it shows up as in the console. It also covers a stalled Core Web Vitals score, traced to the actual render path rather than guessed at.

### What does this not cover?

**General architecture review, code review, or Core Web Vitals work that isn't Next.js-specific.** That's [Agentic coding consultancy](/services/agentic-coding-consultancy/). And if you need a Next.js site built from scratch, that's a fixed-price AI-editable website build, scoped separately.

## How a Next.js review runs

### Send me the repo and the question

The caching issue, the boundary you're not sure about, or the middleware function you're about to ship. One paragraph and read access to the project is enough to start.

### I read the app router before I quote

I go through the route segments, the caching config, and the client/server split, then give you a fixed hour estimate. No retainer running in the background.

### You get it in writing

What to change in the caching config, which components to move across the boundary, and what the middleware can safely do at the edge. Written down, so it survives the call.

## Book time

Custom quote

Contact form on this page: name, email, and what you need. [Book time](#lead-form).