All hubs

Business Model

Building a SaaS business

SaaS is famously hard for first-time solo founders — long sales cycles, low first-purchase price, retention is everything. It's also famously rewarding when it works. This is the realistic version, not the Silicon Valley fairy tale.

By Priya Ranganathan · Last updated May 19, 2026

Who this is for

Solo founders or small teams building subscription software.

What you'll learn

  • Whether your idea is SaaS or something else
  • Startup costs and unit economics that work
  • First customer path for SaaS specifically
  • Pricing and packaging that compounds
Calculate your LTV:CAC

Is your idea SaaS?

Not every software business is SaaS. Test:

  • Recurring need? Customers need this monthly, not once. (One-off purchases don't compound.)
  • Net retention? Existing customers can spend more over time (more seats, more usage, higher tier).
  • Defensible by integration? The product gets stickier the more workflows it touches.

If you can't say yes to all three, you may have a great software product but it's not a SaaS — it's a tool or a one-off. Pricing and distribution work differently.

Startup costs and unit economics

Realistic SaaS founder budget for first 12 months (solo):

  • Hosting + DB: $0-200/mo (free tiers cover the first 100 users).
  • Auth/email: $0-50/mo.
  • AI APIs (if using): $50-500/mo depending on workload.
  • Tools: $100-300/mo.
  • Marketing: ~$0 if you're doing founder-led acquisition.
  • Legal/admin: $500-2,000 one-off.

Realistic milestones:

  • Month 1-3: 5-10 paying customers, $200-500 MRR.
  • Month 6: $1k MRR.
  • Month 12: $5-15k MRR.

If you blow past these comfortably, you have signal. If you're behind, the constraint is usually the offer, not the effort.

First customer path

SaaS first-customer reality: you'll cold-outreach the first 10 personally. Public marketing doesn't work yet at this scale.

The path that's worked for most solo SaaS founders:

  1. Hand-pick 50 names in your ICP.
  2. Cold DM/email with a specific observation about their business.
  3. Get on a 20-minute discovery call.
  4. Show the working product.
  5. Close at a sharp discount (early-customer pricing).

The first 10 are research. The first 100 are growth. Don't try to scale the channel that got you to 10 — pattern-match what worked across customers, then build a repeatable channel from that pattern.

Pricing and packaging

Three pricing instincts most SaaS founders learn the hard way:

  1. Don't price by feature; price by value. "Per user" is fine when the value scales with users. "Per workflow" is fine when value scales with usage. Pick what aligns with the outcome.
  2. Three tiers, not five. Starter / Pro / Business. Five tiers paralyses buyers.
  3. Annual prepay with a 15-20% discount. Improves cash flow and dramatically reduces churn.

Common mistakes: pricing too low (then having to raise prices and lose customers later), having no Pro tier (no upgrade path), and not testing annual pricing.

Retention is the whole game

New SaaS founders fixate on acquisition; experienced ones fixate on retention. The reason is mathematical: a 5% monthly churn rate caps your maximum MRR at 20× your monthly new MRR (1/0.05). At 2% monthly churn, the same monthly acquisition lifts the ceiling to 50×. Cutting churn is by far the highest-leverage growth lever you have.

Where churn actually comes from (in rough order of frequency):

  • Failed activation — the customer never reached the moment the product was supposed to help. Fix: a meaningful onboarding sequence that doesn't end with a checklist, it ends with the customer having achieved one outcome.
  • Wrong fit — the customer was acquired but was never going to retain. Fix: tighten your ICP filter pre-sale, not post-sale.
  • Champion left the buying company — common in B2B; the person who bought you left and the new person doesn't know what you do. Fix: build product touch with multiple users at each account.
  • Slow product — the next-best alternative caught up. Fix: ship.
  • Payment failures — 30-40% of involuntary churn is just expired cards. Fix: a smart dunning sequence (Stripe Smart Retries, ChartMogul, or a hand-rolled one) recovers most of these.

Track gross retention (excluding expansion) cohort-by-cohort, not blended. A blended NRR of 105% can hide an old cohort that's bleeding 4% a month — the new-customer growth is masking the leak.

Step-by-step action plan

Do these, in order

  1. 1Validate the recurring-need test against 10 ICP conversations
  2. 2Build the smallest possible useful product
  3. 3Hand-sell the first 10 customers
  4. 4Set up the LTV:CAC and Runway calculators with real numbers

Frequently asked questions

How long until SaaS is profitable?
Realistic: 18-36 months from start to $10k+ MRR with healthy gross margin. Faster paths exist (productised services attached to the SaaS); slower paths exist too (deep enterprise SaaS).
Should I raise for SaaS?
Optional. Many solo SaaS founders bootstrap to $50-100k MRR before considering outside money. The question to ask: would the capital meaningfully accelerate a specific lever (e.g. paid acquisition once unit economics work), or is it for runway you should be earning from customers?
PLG (product-led growth) vs sales-led — how do I pick?
Pick by ACV and complexity. Under $50/mo ACV and a setup time under 10 minutes — almost always PLG (a sales team would cost more than the LTV). Above $1,500/mo ACV or onboarding requiring integration work — almost always sales-led. The middle ($50-$1,500) usually starts PLG-led and adds sales as deals get bigger. Don't try to do both at once at pre-seed; pick the dominant motion.
When does a founder hire their first engineer?
When the constraint on shipping is genuinely a headcount problem, not a focus problem. Most solo SaaS founders hire too early — they're slow because they're context-switching across sales, support, and engineering, not because there isn't enough engineering capacity. Fix the focus problem first (drop one workload onto a contractor, simplify your scope), then hire the engineer when you're still bottlenecked.

Related resources

Related tools

Related templates

Related courses

Related hubs