Next.js builds that actually use the platform.
App Router, server components, ISR, edge rendering, server actions — picked by fit, not by hype. Next.js is our daily driver: the stack we ship every client site and product on.
Release
v4.2 · shipped Tuesday
Today · 8 bookings
Tuesday, May 6
Web · v4.2
Today
8 bookings
10:00
Clara M.
10:30
Maya K.
11:15
Jay R.
iOS + Android · v4.2
App Router, server components, server actions — used the way Vercel intends.
Rendering strategy chosen per route (SSG, ISR, SSR, edge) instead of one default.
Caching, revalidation, and tag-based invalidation built into the data layer.
What we build into every Next.js engagement.
Architecture, build, deploy, and the operational layer that keeps it cheap to run.
App Router architecture
Route groups, parallel routes, intercepted routes, and loading/error boundaries used the way the docs intend.
Scope of work
v1.0 · signed off
Users
- · Clinic staff · 40 seats
- · Patients · web + mobile
- · Billing · read-only
Integrations
Milestones
- · Discovery — Aug 12
- · Beta — Sep 30
- · Launch — Nov 1
Out of scope
EHR sync · deferred to Phase 2
Rendering-mode map
A per-route decision: static, ISR, SSR, edge SSR, or client. Documented in the repo. Reviewable.
Full stack
one team · one codebaseMarketing · web app · portal
GET /api/bookings · 142ms
Schema · migrations · backups
Data layer with revalidation
Server fetches with cache tags. Server actions that invalidate tags on write. No stale data, no full-route revalidates.
components/Header.tsx
tsx1
2
3
4
5
6
7
<header>
<nav aria-label="Main">
<button aria-label="Close menu">
Close
</button>
</nav>
</header>
Edge runtime where it pays
Cookie-based personalization, geo routing, AB-test flags — moved to the edge so origins stay cold.
API console
production[
{ "id": 4218, "time": "10:00", "name": "Clara M." },
{ "id": 4219, "time": "10:30", "name": "Maya K." }
]p50
18ms
p99
240ms
Uptime
99.99%
Five phases. Next.js-specific decisions baked in.
The phase names match every other engagement. The internals shift to surface Next.js-specific decisions early.
Discovery
Audit the existing stack, the conversion targets, the data sources, and the constraints (CMS, auth, third-party services).
Strategy
Per-route rendering map, caching strategy, data-layer design, Vercel deploy target plan. Signed off before scaffolding.
Build
Pages, components, data layer, server actions, edge personalization. Real Lighthouse scores from week two.
Ship
Vercel production deploy, monitoring, runbook, and the cost-engineering pass that keeps the bill in line with the architecture.
Building on Next.js — or migrating to it?
Tell us the routes, the data sources, the constraints. We’ll map the rendering strategy, scope the build, and tell you honestly whether Next.js is the right call for what you’re trying to ship.