Brent Haskins / Applied AI
A Next.js MVP wins when you cut scope, not when you win framework debates
Posts arguing Next.js versus React miss what founders need: a URL that works. Brent Haskins uses Next.js for SaaS MVPs when SEO, server routes, and fast deploys matter—and spends the savings on scope control, not plugin shopping.
Framework debates are entertainment. Founders need a domain, a form, a notification, and a bill they can pay.
I ship Next.js on SaaS where HTML must rank, server code must hold API keys, and teams want one repo. Formably and broker-facing web products fit that shape.
What not to copy from enterprise templates
Boilerplates ship RBAC, billing, and admin themes you will not use for months. Each extra surface is a bug surface. Your MVP hypothesis is usually one loop:
Stranger arrives → understands offer → completes action → you get alerted
Everything else is backlog fiction.
Server boundaries in plain language
If a key must not appear in the browser bundle, it belongs in a route handler or server action with validation—not in a client component “temporarily.” AI generation, payment intents, and webhook signing all fail this test when rushed.
SEO without a marketing department
Program pages for brokers, landing pages for form software, and training catalogs need indexable routes, metadata, and sitemaps. Next.js App Router is a tool; the product decision is which pages earn search traffic and which stay behind auth.
Pair with real copy—see broker site as product.
Deploy rhythm beats perfect abstractions
Ship to production weekly. Feature flags for risky paths. Rollback via revert, not heroics. Users on shared hosting do not care if you used RSC—they care that submit works on mobile Safari.
iOS is not a Next.js problem
Floom, Auri, and Story World are Swift. Choosing Next.js for web does not obligate mobile. Pick stack per product.
Brent Haskins
Case studies: /projects/formably, /projects/rally. More on product engineering.
If you are planning an MVP, write the one loop on paper. If Next.js helps that loop, use it. If the loop is native-only, ignore this post and open Xcode.
FAQ
Questions people ask about this topic.
When is Next.js the right choice for a SaaS MVP?
Choose Next.js when you need marketing pages and authenticated app routes together, server handlers for secrets and webhooks, and predictable deploys. Skip framework tours if the MVP is mobile-only or a desktop utility. The decision is workload fit, not Twitter polls.
What should the first Next.js release include?
One core workflow end to end, auth if multi-user is day-one, email or webhook on the success event, basic analytics, and error monitoring. Defer admin dashboards, role matrices, and plugin ecosystems until users touch production. Brent’s Formably and RallyLeads work followed that line—ship the pipeline before the platform.
Sources