How One Team Shipped a Production SaaS in a Weekend
The constraint was the point
A small team building a B2B analytics dashboard for e-commerce operators gave themselves 72 hours. Not because they had to — because constraints are the sharpest design tool available to an engineering team.
The requirements were non-negotiable: multi-tenant auth, usage-based billing, real-time data, edge-deployed globally.
Without a starting UI layer, the honest estimate was three weeks minimum. With one, they shipped in a weekend.
What the template handled
Before writing a single line of product code, the following were already working:
- Auth UI: sign-in, magic links, and session screens ready to wire up to their own OAuth2/session provider.
- Billing UI: a pricing page and Customer Portal shell ready to connect to Stripe subscriptions with a 14-day trial and metered usage.
- Dashboard shell: layout, navigation, and data tables ready to point at their own Postgres instance.
- Deploys: a static build that pushes to the edge in seconds, with preview branches for every PR.
That’s the 80% most SaaS products spend weeks on UI alone. They started at the 20% — the actual product logic.
The velocity compound effect
What surprised the team wasn’t the initial speed. It was how velocity compounds.
When you’re not context-switching between “how do I lay out this settings page” and “what does my actual product need to do,” you ship faster every day. By hour 48, they were iterating on the core analytics query engine — not debugging layout CSS.
Numbers
| Metric | Value |
|---|---|
| Time to first deploy | ~4 hours |
| Auth screens wired up | ~20 minutes |
| Billing screens wired up | ~40 minutes |
| Lines of UI code written from scratch | 0 |
| Total product lines of code | ~3,200 |
The honest tradeoffs
A template like this is opinionated. If your stack needs to diverge significantly — a very different design language, non-Stripe billing, bespoke infra — you’ll fight it. It’s built for the 90% use case, not the edge case.
But for standing up a standard SaaS UI fast? It’s hard to beat.
Takeaway
The best UI layer is the one you don’t have to think about. A solid starting point gets out of the way so the team can build what their users actually need.
They shipped. It worked. They’d do it again.