Ex-Disney · Ex-Globant · Freelance since 2014
Hire a senior Next.js developer who ships production, not demos.
I build Next.js apps that handle real traffic — marketing sites that rank, dashboards that don't blow up on large datasets, and App Router architectures that survive the next React RFC. Strong TypeScript, proper SEO, honest performance budgets.
Start a projectApp Router, Server Components, server actions — picked right
Not every page needs to be a server component. Not every form needs a server action. I pick the rendering strategy per route based on SEO, interactivity and cache behavior — not ideology.
SEO that actually works on a React framework
Proper metadata API, canonical tags, hreflang, Open Graph, Twitter cards, schema.org JSON-LD, sitemap.xml, robots.txt. Not 'it's a Next.js site, of course it's SEO-friendly' — the full technical SEO checklist.
Dashboards that handle real data volume
Server pagination, streaming responses, incremental rendering, TanStack Table for 100K+ rows, proper caching and invalidation. If your data is going past MVP scale, the architecture needs to as well.
Deploy on Vercel, Netlify or your own infra
Vercel is the default, but I've shipped Next.js on Netlify, self-hosted on Docker, and AWS via open-next. I'll pick based on your cost, compliance and team — not platform allegiance.
The Next.js stack I ship with
- Next.jsApp Router, server and client components, route handlers
- TypeScriptStrict types for props, server actions, API routes
- ReactSuspense, transitions, the use() hook — where it actually helps
- Server ComponentsDefault for data-heavy, static-ish content
- Server ActionsProgressive-enhancement forms without API boilerplate
- Tailwind CSSUtility-first, design tokens, dark mode, responsive
- shadcn/uiComponents you own and can customize, not a black-box library
- VercelDeploy previews, edge runtime, ISR, image optimization
- PrismaType-safe ORM with migrations you can trust
- NextAuthAuth with Google, GitHub, email magic links, credentials
- StripeSubscriptions, usage billing, customer portal, webhooks
- PlaywrightEnd-to-end tests across real browsers, not just Chromium
When Next.js is the right framework
Next.js is my default when the project is mostly React and needs real SEO. Marketing sites, dashboards with public-facing marketing pages, multi-tenant SaaS apps, content-heavy portals — Next.js handles all of them with the right rendering strategy per route. Its Server Components model lets you move data-fetching to the server without giving up React's programming model, which used to require picking between SSR frameworks and SPA frameworks with awkward tradeoffs.
App Router is mature now, but it's not a drop-in replacement for Pages Router on every project. Legacy codebases with complex custom _app/_document setups, specific patterns like getServerSideProps that depend on request/response access, or teams that already know Pages Router well — migration needs to be weighed, not assumed. I've done both migrations and 'stay on Pages Router for now' calls, depending on ROI.
Where Next.js is the wrong call: pure SPAs where SEO doesn't matter (use Vite + React, fewer moving parts), server-heavy APIs where the frontend is minor (use NestJS and a thin React frontend), or apps that need strong offline-first behavior (native or PWA-focused stacks fit better). Also: don't pick Next.js just because Vercel hosts it well — that's a nice consequence, not a reason.
I've built Next.js platforms for tourism operators (Argenway — marketing site plus admin dashboard), healthcare centers (Maeth — public site plus appointment booking), real estate (Don Piso Sitges/Mijas — SEO-heavy property listings for Spain), and B2B SEO-driven sites (DirecTV Argentina — conversion funnels per plan). Same framework, wildly different rendering strategies per page — that's the flexibility you get with Next.js done right.
FAQs
App Router for new projects. Pages Router for existing codebases unless there's a real reason to migrate. I don't do forced rewrites — if your app works and ships features, migration is an investment that needs to justify itself.
Both. A lot of my recent work is taking over existing Next.js projects — audits, performance fixes, adding App Router incrementally, migrating auth, moving off Vercel or to Vercel. I'll read the code before quoting.
I have a design eye but I'm not a designer. For landing pages and dashboards, I can build from rough wireframes or take an existing design system and implement it cleanly. For anything where brand and UX are the core product, hire a designer — I'll work with them.
Default recommendation is Vercel because the tooling integration is tight. But I've shipped Next.js to Netlify, self-hosted Docker on DigitalOcean, AWS via open-next, and Cloudflare Pages. Pick based on your cost, compliance, and team — not on hype.
Yes. Full Stripe integration: checkout, subscriptions, customer portal, webhooks with signature verification, proration, usage billing, tax automation with Stripe Tax. I've shipped this on SaaS products and content platforms.
Yes, extensively. I usually start with shadcn/ui as the component base because you own the code and can customize it. Tailwind for styling, Framer Motion or CSS transitions for animation. For enterprise clients, I've worked with bespoke component libraries and Mantine.
Need a Next.js engineer who ships fast and doesn't break prod?
MVPs, dashboards, SEO-heavy marketing sites, legacy migrations. 24-hour reply time.
Start the conversation