Next.js starter kits for early-stage startups
Pre-revenue, pre-seed, and every week spent on plumbing is a week not spent with users.
What this is
Before you have customers, the only thing that matters is how quickly you can put something in front of people and charge them for it. Everything else is a cost.
The SaaS Boilerplate is $59 one-time and covers the part of that which is pure plumbing: accounts, teams, roles, and two payment processors that actually record what they were paid.
What you get on day one
- Multi-tenancy that exists. Organizations, memberships with owner / admin / member, invitations that expire and are bound to the invited email address, and seat limits read from the plan at invite time rather than enforced by hiding a button.
- Billing that records itself. Stripe and Polar webhooks, both signature-verified, both writing to one subscriptions table, keyed so a replayed event updates instead of duplicating.
- An admin area behind a platform-role check, so you can see every user and subscription without opening a database client.
- Tests. 13 Playwright specs that pass on a fresh clone, including that every protected route redirects a signed-out visitor.
What to ignore until you have customers
Resist these. They feel like progress:
- A design system. Use the one in the box.
- SSO and SAML. Nobody has asked yet. When an enterprise buyer asks, that conversation funds the work.
- Usage-based billing. Start with flat plans. You do not know your value metric yet.
- Multi-region anything.
Why Polar matters for some founders
Stripe does not support businesses in every country. Polar is a merchant of record reaching 130+ countries, which means it handles the sales-tax and payout side for you. If you are incorporating somewhere Stripe does not cover, this is the difference between taking payments and not.
Both are wired. Use whichever you can actually get paid through, or both.
The honest limitation
This is a snapshot of source code you own outright. It does not update itself, there is no support contract, and when you raise money and hire a team you will refactor most of it.
What survives is the part that is easy to get wrong and hard to notice: webhook idempotency, server-side role checks on every mutation, and sessions that actually persist. Those are worth $59 whatever happens to the rest.
Where to go next
- Build a SaaS for $100/month — what it costs to run once it is live
- Build an MVP for under $50 — the cheaper path
- MakerKit vs CheapStack — if you are funded and want a support contract
Questions
Does it support multiple organizations and roles?
Yes. The SaaS Boilerplate ships organizations, memberships with three roles, invitations with expiry and email binding, and per-plan seat limits enforced server-side at invite time.
Can we take payments on day one?
Yes. Stripe and Polar are both wired, both verify webhook signatures, and both write to one subscriptions table. Polar reaches 130+ countries, which matters if your founders or customers are outside Stripe's supported list.
Will we outgrow it?
You will, and that is fine. It is source code you own, not a dependency. The parts worth keeping — the idempotent webhook handling and the role checks — are the parts teams usually get wrong when they write them from scratch under time pressure.