I got tired of rebuilding the same SaaS setup in Next.js

A🖤🇨🇻 — Thu, 22 Jan 2026 16:53:07 +0000

I got tired of rebuilding the same SaaS setup in Next.js
Every time I started a new SaaS side project with Next.js, I noticed the same pattern.
Before I even got to the actual idea, I was rebuilding:
Landing pages
Auth flow UI
A dashboard layout
Basic state handling
Routing and structure
Over and over again.
None of that was the product — it was just the foundation.
So instead of repeating myself again, I decided to package my current setup into a starter template.
What this starter includes
This is not a finished SaaS.
It’s a boilerplate meant to save setup time.
Here’s what’s already wired:
Home, Features, and Pricing pages
Signup & Login UI (demo auth)
Protected dashboard
Simple Projects CRUD (create/delete)
App Router structure
Tailwind CSS styling
The idea is simple:
you plug in your own product logic, backend, and real authentication later.
Why I made it
I realized I was spending too much time rebuilding the same scaffolding instead of validating ideas.
Having a ready structure helps me:
Start faster
Stay consistent
Focus on the actual problem I’m trying to solve
It’s especially useful for MVPs and experiments.
About authentication
Right now, the template uses local storage–based demo authentication.
That’s intentional:
It shows auth flow and route protection
It keeps the starter lightweight
It’s easy to replace with Clerk, Supabase, or Auth.js
This is meant for prototyping, not production as-is.
Sharing in case it helps
I packaged this setup as a reusable starter in case it helps other people building MVPs with Next.js.
If you’re interested, it’s here:
👉 https://shorturl.at/ExYVf
No pressure — just sharing a tool I built for myself.
Happy to hear how others approach their own SaaS starters, or what you usually set up first when starting a new project.

Forem: A🖤🇨🇻

I got tired of rebuilding the same SaaS setup in Next.js