Guide
Boilerplate vs. Building From Scratch: The Real Time Cost
Wiring auth, Stripe, emails, SEO, and deployment from scratch takes 50–90 hours before you write a line of product code. We break down the hours feature by feature.
Every founder who can code faces this fork: start from an empty repo and build exactly what you want, or start from a boilerplate and customize. The argument is usually conducted with vibes — "real engineers build their own" versus "just ship" — so let's do it with numbers instead.
What "from scratch" actually means
Before your product exists, a production SaaS needs the same seven layers no matter what you're building: authentication, payments, database, transactional email, SEO, analytics, and deployment. None of these are hard individually. All of them have edge cases that eat days:
- Auth isn't a login form — it's OAuth redirect flows, email verification, password reset, session refresh, and protecting every route.
- Stripe isn't a checkout button — it's webhook handlers that survive retries and out-of-order events, subscription state sync, and the customer portal.
- SEO isn't a title tag — it's Open Graph images, canonical URLs, sitemaps, robots rules, and structured data that validates.
The hours, feature by feature
These are our estimates for a competent developer who has done each task before, including testing. First-timers should expect the high end or worse — the numbers below are the midpoints of each range:
Estimates assume prior experience with each tool and include testing edge cases (webhook retries, OAuth failures, email deliverability). Total midpoint: ~83 hours; realistic range 55–110 hours.
Translating hours to money
| Your time is worth… | From scratch (~80 h) | Boilerplate (~4 h setup + price) |
|---|---|---|
| $0/hour (nights & weekends) | 3–4 weeks of evenings | One evening + $0–$349 |
| $50/hour | $4,000 | $200–$550 |
| $100/hour (typical contractor) | $8,000 | $400–$750 |
| $150/hour (senior rate) | $12,000 | $600–$950 |
Total cost of infrastructure phase: from scratch vs. boilerplate, at different valuations of your time.
Even at hobbyist rates the comparison isn't close, and the gap widens with every extra hour of debugging a webhook at midnight. The honest version of the from-scratch argument is never about money — it's about control and learning, which are real but should be priced consciously.
The cost that actually kills projects
The 80 hours aren't just expensive — they're front-loaded at the exact moment your motivation and idea are most fragile. Most side projects die in the infrastructure phase, before a single user has seen the product. Two to four weeks of building things users never notice is where momentum goes to die. The boilerplate's real value isn't the $4,000 of saved labor; it's that your first week produces something a user can react to.
When from scratch is the right call
- The infrastructure is the product — you're building an auth service, a billing tool, an email platform.
- Your architecture is genuinely unusual — realtime collaboration, local-first sync, or compliance constraints that fight every kit's assumptions.
- Learning is the explicit goal — wiring Stripe once teaches you things no tutorial does. Do it deliberately, on a project without a deadline.
The verdict
If you're building a product to put in front of users, start from a boilerplate and spend your 80 hours on the thing only you can build. The budget question is secondary — options run from free (Vercel's starter) through $20 (Web Boilerplate, refunded — ours) to $199+ (ShipFast) and $299+ (MakerKit). We've compared them all in the best Next.js boilerplates in 2026; if budget is the constraint, start with the cheapest options ranked.
Frequently asked questions
How long does it take to build a SaaS from scratch?
The infrastructure alone — auth, payments, database, email, SEO, analytics, deployment — takes a competent developer roughly 50–90 hours before any product code. Add your actual product on top. With a boilerplate, that infrastructure phase collapses to a few hours of configuration.
Is it cheaper to build from scratch or buy a boilerplate?
Buying almost always wins on cost. Even valuing your time at just $50/hour, 50–90 hours of infrastructure work is $2,500–$4,500 of effort, versus $0–$349 for a boilerplate. From scratch only wins when the infrastructure is your product or your architecture is genuinely unusual.
Will I understand my codebase less if I start from a boilerplate?
Initially yes — you inherit decisions you didn't make. In practice this fades within the first week of customizing, and good kits are documented for exactly this. The trade is the same as using a framework: you give up some familiarity for an enormous head start.
Does building from scratch make sense with AI coding tools?
AI tools shrink from-scratch time meaningfully (perhaps 30–50% on well-documented tasks like Stripe integration), but they shrink boilerplate-customization time too — and they're more reliable working within an established codebase's conventions than generating architecture from nothing. AI narrows the gap; it doesn't close it.
Keep reading
- Best Next.js Boilerplates in 2026: An Honest ComparisonShipFast, MakerKit, supastarter, Vercel's free SaaS starter, and Web Boilerplate compared on price, stack, and features — with a clear recommendation for each type of founder.
- ShipFast Alternatives in 2026: Cheaper and Free Options ComparedShipFast costs $199–$349. Here are the best alternatives at every price point — from free open-source starters to a $20 bundle — compared feature by feature.
- What Is a Web Boilerplate? A Practical Guide for FoundersA web boilerplate is a pre-built codebase with auth, payments, and deployment already wired up. Here's exactly what's inside one, when to use one, and when not to.