What is a SaaS startup? Definition, examples, and how to start

A SaaS startup is a company that delivers software over the internet (no installs) and charges a recurring fee (monthly or annual). The provider hosts, maintains, and updates the app, while customers access it via a browser or API. That model is called Software as a Service (SaaS) in the official cloud service taxonomy. NIST’s definition of SaaS and NIST SP 800‑145 are the canonical references. (csrc.nist.gov)

Key takeaways

• SaaS = hosted software, subscription revenue, and (usually) a multi‑tenant architecture where many customers share the same app instance. Microsoft’s SaaS architecture guide and AWS’s SaaS whitepaper explain why this keeps costs low and speeds up shipping. (learn.microsoft.com)
• The business model rests on predictable recurring revenue (MRR/ARR), retention (churn, NRR), and efficient acquisition (CAC, payback). See concise definitions and formulas in the ChartMogul metrics library. (chartmogul.com)
• You can validate and ship a credible SaaS in weeks using an inexpensive landing page (Carrd), managed hosting (Vercel/Render), and modern billing (Stripe or Paddle). Pricing and capabilities are documented by each vendor. Carrd plan prices, Vercel pricing overview, Render pricing, Stripe pricing, and Paddle pricing. (carrd.com)

What “SaaS startup” means (and what it doesn’t)

A SaaS startup is a new software company that:

• Delivers its product over the internet as a service (not installed on the customer’s hardware).
• Charges recurring subscription fees (monthly or yearly), often tiered by seats, usage, or features.
• Operates and updates one shared application for all customers (multi‑tenant), with data and entitlements isolated per customer.

These are straight from the cloud model formalized by NIST and widely implemented by major platforms. NIST SP 800‑145 defines SaaS distinct from PaaS and IaaS; multitenancy is explained in depth by Microsoft and AWS. (nist.gov)

Common examples you’ve used: CRM, collaboration suites, analytics dashboards, help desks, billing systems. The defining traits are delivery (hosted + browser/API) and subscription—not a specific market.

How a SaaS startup works (architecture, delivery, ops)

At a high level:

• Multi‑tenant app: One codebase serves many tenants; you isolate each tenant’s data and entitlements, and you monitor noisy‑neighbor risks. See AWS’s discussion of why multitenancy is a business model choice as much as it’s technical. (docs.aws.amazon.com)
• Continuous delivery: You ship updates to all customers at once, with feature flags and safe migrations. Microsoft’s reference architecture diagrams capture the usual split of shared services (auth, billing, telemetry) plus tenant isolation patterns. (learn.microsoft.com)
• Cloud responsibilities: The provider runs the app, databases, and security controls; customers just use the product. That division is codified in NIST’s service model definitions. (nist.gov)

Why this matters for founders: a single, hosted codebase makes support, upgrades, and pricing experimentation faster than shipping binaries or on‑prem installers.

SaaS vs on‑prem, PaaS, and IaaS (quick comparison)

Aspect	SaaS	On‑prem software license	PaaS	IaaS
What you buy	Finished app as a service	Perpetual/term license to run software yourself	Managed platform to build/run your app	Virtualized compute, storage, networking
Who operates it	Vendor	Customer IT	Shared (vendor platform + your app)	You
Updates	Continuous, by vendor	Manual, by customer	Platform by vendor; your code by you	You
Pricing	Recurring subscription, often tiered/usage‑based	Upfront + maintenance	Usage‑based	Usage‑based
Reference	NIST SP 800‑145	—	NIST SP 800‑145	NIST SP 800‑145

(nist.gov)

How SaaS startups make money (pricing models that actually ship)

There are four common patterns. Each is supported by mainstream billing platforms and documented with exact behaviors.

• Flat subscription (one plan price). Simple for self‑serve tools.
• Per‑seat (user‑based). Linear with users; the price scales with the quantity field. Stripe docs on per‑seat and pricing models explain how to set quantity and tiers. (docs.stripe.com)
• Tiered feature bundles (Starter/Pro/Enterprise). Show more value per tier; gate features or limits. Stripe’s tiered pricing guide outlines tier shapes and tradeoffs. (stripe.com)
• Usage‑based (metered) or hybrid (base + overage). Great for APIs and data products; you record usage events and let billing generate invoices; Stripe’s pay‑per‑use explainer covers ops realities. (stripe.com)

Merchant‑of‑record (MoR) providers like Paddle bundle payments, taxes, and buyer support into one all‑in price: Paddle’s posted “pay‑as‑you‑go” rate is currently 5% + $0.50 per Checkout transaction, with no monthly fee. That’s explicit on their pricing page. See Paddle pricing. (paddle.com)

If you run your own payments stack, Stripe’s U.S. card processing is 2.9% + 30¢ per successful transaction; Stripe Billing is 0.7% of billing volume on pay‑as‑you‑go, with optional subscriptions for higher‑volume needs. See Stripe’s live pricing page. (stripe.com)

The core SaaS metrics (definitions + copy‑paste formulas)

Run your company on these. The formulas and definitions below are from ChartMogul’s public library and help docs.

• MRR (Monthly Recurring Revenue) and ARR (Annual Recurring Revenue): predictable subscription revenue normalized to month or year. ARR is often MRR × 12.
• Churn: the rate customers or recurring revenue are lost in a period. Track both logo churn and MRR churn.
• NRR (Net Revenue Retention): (Starting MRR + Expansion − Contraction − Churn) ÷ Starting MRR.
• CAC (Customer Acquisition Cost): fully‑loaded sales + marketing cost to acquire a customer.
• CAC payback (months): CAC ÷ (ARPA × gross margin %).
• LTV (Customer Lifetime Value): ARPA × gross margin % ÷ churn rate (logo or revenue, be consistent).

Definitions, formulas, and worked examples: ChartMogul SaaS metrics library, NRR method, and LTV rule‑of‑thumb. (chartmogul.com)

Operator tips:

• Don’t compute LTV on revenue alone—use gross margin in the numerator or you’ll flatter LTV and the LTV:CAC ratio. ChartMogul’s guidance makes this explicit. (chartmogul.com)
• When in doubt, adopt the public definitions your investors and finance tools already use (ChartMogul/Baremetrics/ProfitWell). It removes debate from board meetings. (help.chartmogul.com)

Set up your public “home base” (yes, this is part of building)

Create a page that says who you are, what you’ve built, and how to reach you. A founders.page takes 5–10 minutes and helps you:

• List every product you’ve shipped (ship the SaaS you’re validating first; keep past tools as social proof).
• Add milestones (MVP live, first 10 users, first $1k MRR) and your GitHub activity so prospects see momentum.
• Link your docs, pricing, and a “Book a call” link for sales conversations.
• Use the single link in your email signature, social bios, and pricing page footer.

For this topic, include: your product page, a short pricing grid, your changelog, and a Loom demo. Then add a “Try free” and “Talk to us” button. It shortens discovery for users and investors. Create your free founders.page.

The fastest credible way to prove a SaaS idea (30‑day plan)

1. Market and problem definition (days 1–3)

• Write one sentence: “We help [ICP] do [job] by [mechanism].” Keep it on your homepage.
• Draft a 10‑question interview guide. Aim for 10 calls; measure “problem must‑have” intensity.

2. Landing page + list (days 2–5)

• Use Carrd Pro Standard ($19/year) to ship a one‑page site with headline, demo GIF, 3 value bullets, and an email capture form. Carrd’s official docs list plan prices and features. Carrd plans and prices. (carrd.com)

3. Billing, pricing, and checkout (days 3–7)

• If you want to own the merchant account: set up Stripe Payments and Stripe Billing. Start with one flat plan and one usage‑based add‑on; Stripe’s docs cover per‑seat, tiered, and metered models you can turn on later. Stripe pricing models overview. (docs.stripe.com)
• If you want sales‑tax/VAT handled for you: start with Paddle’s MoR model (5% + $0.50 pay‑as‑you‑go listed on their site) to accept global payments without filing taxes yourself. Paddle’s posted pricing. (paddle.com)

4. Build the smallest usable product (days 5–20)

• Host the app on Vercel (free Hobby for non‑commercial; Pro for businesses) or Render (predictable, usage‑based pricing). Keep it simple: one region, one Postgres, one queue. See each provider’s live pricing pages. Vercel pricing, Render pricing. (vercel.com)
• If you prefer serverless Postgres/auth/storage, Supabase has a Free and Pro plan with documented quotas and costs. Start free; upgrade when you need dedicated compute. Supabase billing and pricing and pricing page. (supabase.com)

5. First 10 users (days 14–30)

• Offer a self‑serve trial (PLG) unless your product is enterprise‑only. OpenView coined and documents product‑led growth well; skim their primer to decide if PLG fits your motion. OpenView’s PLG primer. (openviewpartners.com)
• Instrument the onboarding funnel: trial started → activated feature → week‑2 usage. Tie these events to upgrade prompts.
• Ship one retention loop: a weekly emailed report or an in‑app “aha” milestone.

Further reading on execution: our deep dives on SaaS implementation: phases, checklists, and examples and the SaaS business model.

Payments and billing: concrete setup patterns

Starter pattern (Stripe):

• Products and Prices: create three prices (Monthly, Annual, and a metered add‑on). Use Quantity for seats; Stripe’s Price object supports per‑unit vs. tiered and graduated tiers. Stripe Price object. (docs.stripe.com)
• Checkout: embed your pricing table for flat/tiered plans; note that Stripe’s embeddable pricing table doesn’t support metered pricing, so link to a self‑serve portal for usage plans. Stripe pricing table limits. (docs.stripe.com)

Starter pattern (Paddle):

• Use Paddle as merchant‑of‑record if you want out‑of‑the‑box tax, invoicing, fraud protection, and buyer support bundled into the 5% + $0.50 fee. Paddle for SaaS overview and pricing. (developer.paddle.com)

Go‑to‑market: product‑led vs sales‑led (picking one on purpose)

• Product‑led growth (PLG): users onboard themselves; the product does most of the selling and expansion. OpenView popularized the term and provides benchmarks/playbooks. PLG definition at OpenView. (openviewpartners.com)
• Sales‑led: a human‑led funnel (SDR → AE → pilot → contract). Better when deals are large, implementations are complex, or compliance is heavy. Salesforce’s guide contrasts PLG and sales‑led in practical terms. Salesforce on PLG vs sales‑led. (salesforce.com)

You can run both: self‑serve for SMB/teams and sales‑assist for mid‑market/enterprise once product signals intent.

Trust and compliance basics you can’t ignore

• SOC 2 (AICPA Trust Services Criteria) is the common attestation buyers ask for. If you’re early, start with the Security category and a sensible control set. The AICPA’s SOC overview and Trust Services Criteria pages are the primary sources. AICPA SOC suite and SOC 3 overview. (aicpa-cima.com)
• GDPR if you process EU personal data: follow data‑minimization, purpose limitation, and user rights principles, regardless of where you’re based. EU Commission’s GDPR principles page and the EU’s business guidance summarize scope. (commission.europa.eu)
• HIPAA if you handle U.S. protected health information: HHS publishes clear summaries of the Privacy Rule and requirements for covered entities and business associates. HHS HIPAA overview. (hhs.gov)

Use a reputable policy generator to publish Privacy Policy, Terms, and Cookie notices from day one. Tools like iubenda and Termly document what they generate and their pricing. iubenda pricing and Termly pricing. (iubenda.com)

Build and host your MVP (platform picks)

• Frontend + edge functions: Vercel is popular with Next.js and supports a free Hobby tier for non‑commercial use and a Pro plan for businesses, with included monthly credits and clear usage docs. Vercel pricing page and [plan limits/FAQ on that page] (look for the Pro plan credit and Hobby vs Pro notes). (vercel.com)
• Full‑stack hosting: Render provides predictable usage‑based pricing for web services and databases. See their current pricing grid for instance sizes. Render pricing. (render.com)
• Backend services: Supabase offers Free/Pro/Team/Enterprise with documented quotas for auth MAUs, storage, and compute. Start free; add Pro once you need dedicated resources or SLAs. Supabase billing docs and pricing. (supabase.com)

What makes a SaaS startup different from other software businesses

• The revenue engine is retention, not just acquisition. NRR above 100% means expansions are more than covering downgrades/churn; it’s a primary valuation driver. See ChartMogul’s NRR definition and formula. NRR explained. (help.chartmogul.com)
• Pricing is a growth lever you can tune continuously. Stripe’s docs cover per‑seat, tiered, and metered shapes you can experiment with safely. Stripe pricing models. (docs.stripe.com)
• Upgrades ship to everyone at once. That’s a feature of the SaaS delivery model, with multitenancy giving you economies of scale. Microsoft SaaS multitenant architecture. (learn.microsoft.com)

Common pitfalls (and fixes)

• Vague ICP → weak onboarding. Fix: pick one segment and design activation around the first outcome that proves value.
• Vanity metrics → bad decisions. Fix: track MRR/ARR, logo churn, NRR, CAC, payback, and LTV using the public formulas above; put them in a monthly review. ChartMogul metrics library. (chartmogul.com)
• Billing complexity too early. Fix: start with one or two plans; add usage later. Use the simplest model that fits, then extend with tiered or metered pricing once you see real usage. Stripe tiered and usage billing resources and metered billing docs. (stripe.com)
• Tax compliance ignored. Fix: either integrate Stripe Tax and file in each region, or use an MoR like Paddle that includes global VAT/sales‑tax handling as part of its fee. Stripe Tax pricing notes and Paddle MoR pricing. (stripe.com)

Where this connects to your founder brand

When you start getting press, replies, and warm intros, people Google you. Keep one canonical page updated with launches, screenshots, milestones, and a way to talk. That’s what a founders.page gives you, and it slots naturally into the “About” link on your site. You can also share it in founder directories (see our roundup) and co‑founder platforms when you recruit. See: Best Founder Directories of 2026: 9 Compared and Best platforms to find a co‑founder in 2026.

Resources to keep going

• Deep dives: SaaS business model: what it is and how it works and Bootstrapping SaaS to Millions: the 0–$3M ARR playbook.
• Official references: NIST SP 800‑145 for SaaS/PaaS/IaaS; AWS SaaS fundamentals for multitenancy; ChartMogul for metrics; Stripe and Paddle for up‑to‑date pricing and billing capabilities. (nist.gov)

—

If you’re skimming: a SaaS startup is hosted software sold on subscription; master recurring‑revenue metrics, pick a simple pricing model, ship a tiny product, and publish a clear founder “home base” so interested users can find and trust you.