Which Next.js version do you use — App Router or Pages Router?+
Next.js 15 with the App Router for every new project. It gives us React Server Components, streaming, and better data-fetching patterns out of the box. I still maintain Pages Router codebases when clients hire me for existing apps, but I recommend migrating incrementally when it makes sense.
Can you migrate my existing site to Next.js?+
Yes. Common migrations I handle: WordPress or Webflow marketing sites to Next.js for speed and SEO, Create React App SPAs to Next.js for better rendering and Core Web Vitals, and older Next.js Pages Router apps to the App Router. Migrations start at $2,500 depending on the source stack and content volume.
Do you handle SEO and Core Web Vitals in Next.js builds?+
Every Next.js build I ship includes: proper metadata and OpenGraph tags, dynamic OG image generation, JSON-LD schema (Article, Service, FAQPage, BreadcrumbList as appropriate), a real sitemap.ts, RSS feed if it's a content site, and Core Web Vitals passing in green. This site is a working example — audit it yourself.
Do you build the backend too, or just frontend?+
Full-stack. My typical stack is Next.js frontend + Supabase or PostgreSQL for data, with Next.js API routes for lightweight backends and FastAPI on Railway when the logic gets heavy (AI, data pipelines, complex business rules). I ship one accountable, deployed product — not a frontend that needs a separate backend hire.
How do you handle authentication in Next.js apps?+
Supabase Auth for most projects — it gives me JWT tokens I can wire directly into PostgreSQL row-level security policies, so multi-tenancy is enforced at the database layer, not just in application code. NextAuth for simpler identity needs. Both are production-grade patterns I've run in real client work like Conslinq.
Do you work with US-based startups and founders?+
Yes — US clients are my main focus. I work in flexible hours with strong overlap for the US business day (typically 10am–6pm ET is easy for me), all communication in English, and async-first over Slack and email. Most US clients say the collaboration feels no different than a local hire.
What if I already have a design in Figma?+
Perfect — that speeds things up. I convert Figma designs to Next.js + Tailwind implementations, matching your design tokens (colors, spacing, typography) and adding the interaction states, responsiveness, and accessibility your designer probably didn't spec.
How do you price Next.js projects?+
Fixed-scope pricing for well-defined builds: MVPs and landing pages from $2,500 (2–4 weeks), full-stack SaaS from $5,000 (4–8 weeks). Hourly at $120/hr for ongoing work or unclear scope. After a free 30-minute scoping call I send a written estimate within 24 hours — no surprises later.
What happens after the project ships?+
Two options. Either full handoff — clear README, environment docs, and a walkthrough call so your team can take it from there — or an ongoing retainer for maintenance, feature work, and on-call support. Retainers start at $500/month for light maintenance and scale up to fractional-CTO engagements.