SaaS
Created by @namkyu · Updated Sep 1, 2026
Software as a Service (SaaS) is software delivered over the internet and commonly monetized through recurring subscriptions, usage-based charges, or per-user pricing.
A SaaS business can range from a one-person niche product generating a few hundred dollars per month to a large B2B software company with millions of dollars in annual recurring revenue.
The technical cost of launching software can be low, but the difficult part is usually finding customers, retaining them, and building a product valuable enough that they continue paying.
Item | Details |
|---|---|
Business model | Recurring software revenue |
Common pricing | Subscription, per-seat, usage-based, tiered |
Typical customers | Consumers, professionals, businesses, enterprises |
Smallest practical team | One founder |
Independent SaaS reality | 28% of companies in MicroConf's 2024 survey were below $1,000 MRR |
Paying customer count | 65% of surveyed independent SaaS companies had only 1–10 paying customers |
2026 private B2B SaaS median growth | 22% annually |
Bootstrapped B2B SaaS median growth | 20% annually |
Stripe U.S. card processing | 2.9% + $0.30 per successful domestic card transaction |
Supabase Pro | From $25/month |
Cloudflare Workers paid plan | From $5/month |
Vercel Pro | $20/month |
Main challenge | Distribution and retention |
Coding required | Usually, unless built with no-code tools |
Difficulty | Intermediate to advanced |
SaaS has attractive recurring-revenue economics, but revenue outcomes are highly uneven.
MicroConf's State of Independent SaaS data reported that:
28% of independent SaaS companies were below $1,000 MRR
65% had only 1–10 paying customers
More than half had fewer than 50 paying customers
The under-$1,000 MRR group was the largest single revenue group in the survey.
These numbers describe independent and bootstrapped SaaS companies participating in MicroConf's survey, not the entire SaaS industry.
They are useful because SaaS success stories can make $10,000 or $100,000 MRR appear more common than it actually is.
Launching functioning software does not mean customers will pay for it.
Larger established SaaS companies operate under very different economics.
SaaS Capital's 2026 survey included more than 1,000 private B2B SaaS companies.
It reported:
Metric | 2026 median |
|---|---|
Overall annual revenue growth | 22% |
Bootstrapped company growth | 20% |
Equity-backed company growth | 25% |
Only 7.3% of surveyed companies reported flat or negative growth.
These are established private B2B SaaS businesses and should not be treated as expected results for a newly launched product.
MRR and ARR represent recurring revenue, not owner income.
A SaaS business may need to pay for:
Infrastructure
Payment processing
APIs
Development
Customer support
Sales
Marketing
Administration
Contractors or employees
SaaS Capital's 2026 private B2B survey found:
Bootstrapped companies spent a median 96% of ARR
Equity-backed companies spent a median 101% of ARR
83% of bootstrapped respondents were profitable or within two percentage points of breakeven
52% of equity-backed respondents were profitable or near breakeven
This reflects established B2B SaaS companies and should not be interpreted as the cost structure of a solo micro-SaaS.
Customers pay a recurring fee for access.
For example:
Plan | Example |
|---|---|
Starter | $19/month |
Pro | $49/month |
Business | $149/month |
The prices above are illustrative rather than market benchmarks.
Annual subscriptions can improve cash flow and reduce the frequency of monthly cancellation decisions.
The customer pays for each user.
For example:
$20/user/month × 10 users = $200/month
This model can expand naturally as the customer's team grows.
The customer pays according to consumption.
Examples include:
API requests
AI tokens
Documents processed
Messages
Storage
Compute time
Transactions
Usage-based pricing can align revenue with customer activity, but the operator must understand variable infrastructure cost.
If a customer pays $20 while consuming $18 of external API services, the pricing model is weak even if the product has recurring revenue.
Different plans provide different:
Usage limits
Features
Support
Team size
Integrations
Customers can upgrade as their requirements increase.
Some SaaS companies also charge for:
Setup
Implementation
Premium support
Training
Consulting
Additional storage
Custom integrations
These services can increase revenue but should be distinguished from recurring software ARR when analyzing the business.
The strongest starting point is usually a repeated problem experienced by a clearly identifiable customer.
Better starting questions include:
What task is repeatedly painful?
What currently requires spreadsheets or manual work?
What existing software do users complain about?
What workflow is expensive or slow?
What niche has needs that larger software ignores?
Avoid starting with:
"I want to build a SaaS. What should it do?"
Technology is easier to build than demand.
Businesses purchase the software.
Possible advantages:
Higher prices
Higher customer value
Fewer customers needed for meaningful revenue
Possible challenges:
Sales calls
Procurement
Security reviews
Integrations
Customer support
For example:
100 customers × $200/month = $20,000 MRR
Individuals purchase directly.
Possible advantages:
Self-service signup
Large potential audience
Faster purchase process
Possible challenges:
Lower pricing
Higher churn
More customers needed
Expensive acquisition
For example:
2,000 customers × $10/month = $20,000 MRR
Both produce the same MRR but require very different businesses.
One of the largest SaaS risks is spending months building a product nobody needs.
Before building a full product, potential validation methods include:
Customer interviews
Landing page
Manual service
Prototype
Waitlist
Pre-sale where appropriate
Small MVP
The goal is to test whether the problem matters enough for people to spend money or actively try the product.
Positive comments are weaker validation than actual usage or payment.
The old version of this page listed items such as an existing computer, free code editor, and free GitHub account as startup costs.
Those are useful development tools, but they do not represent meaningful new cash requirements for most founders.
For a simple commercial SaaS, the more useful cost categories are:
Requirement | Current example | Typical starting cost |
|---|---|---|
Custom domain | Domain registrar | Usually about $10–$30/year depending on TLD |
Production hosting | Cloudflare Workers | Free possible; paid from $5/month |
Production hosting | Vercel Pro | $20/month |
Production database/backend | Supabase Pro | From $25/month |
Payment processing | Stripe | 2.9% + $0.30 per U.S. domestic card transaction |
Transactional email | Usage-based provider | Varies |
Monitoring / logging | Free or paid service | Varies |
External APIs / AI | Usage-based | Varies |
A simple SaaS can therefore launch with tens of dollars per month in direct infrastructure costs.
However, the true startup investment can be much larger when accounting for development time.
A founder who builds the software personally may spend almost no cash on engineering.
That does not make development free.
For example:
300 hours spent building an MVP
is a major investment even if no salary is paid.
This distinction matters when comparing SaaS with businesses that require more cash but less development time.
A technically complicated product can consume months before the founder learns whether customers want it.
Small SaaS products can operate inexpensively.
Current examples include:
Free plan available
Paid plan minimum: $5/month
Paid usage can increase with compute and other resources
Free tier currently includes:
PostgreSQL database
500 MB database size
50,000 monthly active users
1 GB file storage
The current Pro plan starts at:
$25/month
and is designed for production applications that need greater capacity and operational features.
Vercel currently provides:
Hobby: $0/month for personal projects
Pro: $20/month
The Pro plan includes one deploying seat and $20 in monthly usage credit.
A commercial SaaS should use a plan whose terms match commercial usage.
Infrastructure usually becomes more important as the product grows.
SaaS Capital's 2026 private B2B benchmark reported median spending equal to:
Department | Median share of ARR |
|---|---|
Hosting | 5% |
DevOps | 4% |
Customer support / success | 9% |
Sales | 15% |
Marketing | 8% |
R&D | 22% |
General & administrative | 15% |
These are established private B2B companies.
A solo product may have a completely different cost structure.
The useful lesson is that mature SaaS businesses spend far more than their hosting bill.
Stripe's current standard U.S. pricing charges:
2.9% + $0.30
for a successful domestic card transaction.
For example:
$10 subscription:
2.9% = $0.29 Fixed fee = $0.30
Total = $0.59
The processing cost is therefore approximately:
5.9%
of a $10 transaction.
For a $100 payment:
Fee = $3.20
or approximately:
3.2%
This shows why fixed transaction fees have a larger effect on very low-priced subscriptions.
Define the customer narrowly enough to understand their workflow.
For example:
Too broad:
"Small businesses"
Better:
"Small marketing agencies managing recurring client reports"
The narrower description makes customer research easier.
Talk to potential customers.
Understand:
How often the problem happens
How they solve it today
What the current process costs
Why existing tools are insufficient
Whether they would pay to improve it
Build the smallest version that completes the core paid task.
Avoid spending the first several months on:
Complex dashboards
Dozens of integrations
Advanced admin systems
Cosmetic features
before validating the core product.
A typical web SaaS may require:
Frontend
Backend
Database
Authentication
Billing
Email
Hosting
Basic analytics
Managed services can replace much of the infrastructure that once needed to be built manually.
The product needs to handle:
Payment
Subscription creation
Renewal
Failed payment
Upgrade
Downgrade
Cancellation
Test billing before inviting paying customers.
Possible acquisition channels include:
Direct outreach
Existing audience
SEO
Communities
Partnerships
App marketplaces
Content marketing
Paid advertising
Product-led growth
MicroConf's independent SaaS survey identified SEO and word of mouth among the highest-impact channels for surveyed founders.
The acquisition method should match pricing.
A $10/month product usually cannot support hours of manual sales work per customer.
Measure:
Signup
Activation
Usage
Conversion
Cancellation
Talk to users who:
Pay
Cancel
Never activate
Use the product heavily
Early customer behavior is often more useful than adding more features.
Recurring revenue only works when customers continue paying.
Improve:
Onboarding
Product reliability
Core value
Support
Integrations
Workflow fit
Only increase marketing spend after the basic economics make sense.
If customers cancel quickly, purchasing more traffic simply creates more churn.
Monthly Recurring Revenue is normalized monthly subscription revenue.
Example:
100 customers × $50/month =
$5,000 MRR
Annual Recurring Revenue is recurring revenue expressed annually.
A simplified calculation is:
$5,000 MRR × 12 =
$60,000 ARR
MRR and ARR should exclude one-time consulting or implementation revenue when the goal is to measure recurring software revenue.
Customer churn measures customers lost over a period.
Example:
Start month: 100 customers Customers cancel: 5
Customer churn:
5 ÷ 100 = 5%
Churn compounds.
If a SaaS continually loses customers, new customer acquisition must first replace lost revenue before the business can grow.
NRR measures recurring revenue retained from existing customers after:
Cancellations
Downgrades
Upgrades
Expansion
NRR can exceed 100% when expansion revenue is larger than revenue lost from cancellations and downgrades.
SaaS Capital's 2026 research found a strong relationship between NRR and company growth.
Moving from the 90–100% NRR range into the 100–110% range was associated with approximately 5 percentage points more growth in its private B2B dataset.
NRR is especially relevant for B2B SaaS with account expansion.
CAC measures how much it costs to acquire a customer.
Example:
Sales and marketing spend: $2,000 New customers: 20
CAC:
$2,000 ÷ 20 = $100
CAC should reflect the acquisition costs relevant to the business.
A SaaS can grow revenue while destroying cash if it spends more acquiring customers than those customers are worth.
Customer Lifetime Value estimates the economic value of a customer relationship.
The exact formula varies.
A simplified approach considers:
Revenue per customer
Gross margin
Retention
The metric should not be treated as precise when a product has little historical churn data.
A new SaaS with 20 customers cannot reliably assume those customers will remain for five years simply because few have canceled yet.
CAC payback asks:
How long does it take to recover the cost of acquiring a customer?
For example:
CAC: $300 Monthly gross profit from customer: $50
Payback:
$300 ÷ $50 = 6 months
Long payback periods increase the amount of working capital required for growth.
Assume:
200 customers × $30/month
MRR:
$6,000
Possible monthly costs:
Cost | Example |
|---|---|
Payment processing | $234 |
Hosting / database / infrastructure | $250 |
External APIs | $300 |
Email / monitoring / software | $150 |
Customer acquisition | $1,500 |
Contractor support | $500 |
Total example operating cost | $2,934 |
Example remaining amount:
$6,000 − $2,934 =
$3,066/month
before:
Founder salary
Taxes
Legal/accounting
Additional development
Refunds
This example is illustrative.
SaaS economics vary enormously depending on pricing, customer acquisition, API usage, and team size.
Pricing should reflect customer value and business economics rather than only competitor prices.
Common approaches include:
Flat subscription
Tiered subscription
Per-seat
Usage-based
Hybrid pricing
A common mistake is underpricing a B2B product because the founder personally would not pay a larger amount.
If the software saves a company 20 hours of employee time every month, its economic value may be very different from a consumer app.
Free tiers can help:
Product adoption
Word of mouth
User testing
But they also create:
Infrastructure usage
Support load
Non-paying users
A free plan should serve a clear acquisition strategy.
"Competitors have one" is not enough reason by itself.
A free trial allows users to experience paid functionality for a limited period.
Common structures include:
7 days
14 days
30 days
The ideal length depends on how quickly users can reach the product's core value.
A product whose value appears within five minutes may not need a 30-day evaluation period.
Annual subscriptions can improve:
Cash flow
Retention
Revenue predictability
A business may offer a discount in exchange for annual commitment.
For example:
Monthly: $20 × 12 = $240/year
Annual plan: $200/year
The business receives cash earlier but earns less than twelve full monthly payments.
SaaS businesses still require human work.
Support may include:
Account questions
Billing
Bugs
Feature questions
Data issues
Integrations
Support demand usually rises with customer count and product complexity.
A product with poor usability can create support costs that erase the savings of a low-maintenance software model.
Customers may trust the SaaS with:
Business data
Personal information
Payments
Documents
Internal processes
Production systems should consider:
Backups
Authentication
Authorization
Encryption
Monitoring
Dependency updates
Incident response
B2B and regulated customers may require additional security documentation or compliance.
There is no universal SaaS license.
Requirements depend on:
Company location
Customer location
Data handled
Industry
Potential obligations include:
Business registration
Terms of service
Privacy policy
Sales tax / VAT / GST
Data protection
Consumer protection
International SaaS can create tax obligations in jurisdictions where the founder has no physical presence.
Payment or merchant-of-record platforms may help with parts of this process, but responsibilities vary.
A profitable SaaS can itself become an asset that is sold.
Acquire.com's February 2026 acquisition report analyzed completed transactions from 2025.
It found:
Median confirmed SaaS profit multiple: 3.9×
Businesses below $100,000 net income averaged approximately 3.7×
Businesses with $100,000–$1 million net income averaged approximately 3.9×
Most deals clustered around roughly 3–5× net income
Average time on market was approximately 81 days
Acquire.com also reported that most profitable SaaS businesses published on its marketplace had profit margins of at least 50%, with average margins around 71% in 2025.
This dataset is strongly selected toward businesses being offered for sale and should not be treated as a valuation formula for every SaaS company.
Buyer interest can also depend on:
Growth
Retention
Customer concentration
Founder involvement
Product age
Profit
Documentation
Transferability
Modern hosting, AI coding tools, no-code platforms, payment APIs, and managed databases have reduced the technical barrier to launching software.
That also means more competitors can launch quickly.
The ability to build is not the same as the ability to acquire customers.
MicroConf's independent SaaS data shows that the largest revenue group was below $1,000 MRR.
Do not budget personal finances assuming a new SaaS will rapidly replace a salary.
A subscription business must continually replace canceled recurring revenue.
Weak retention can make strong new-customer acquisition look better than the underlying business actually is.
Costs can rise with:
AI usage
External APIs
Compute
Storage
Bandwidth
Database usage
Email
Track unit economics before offering unlimited usage.
A SaaS may depend on:
Cloud provider
Database
Payment processor
Authentication provider
AI provider
Email service
Third-party APIs
A pricing or policy change can affect the product immediately.
A technically excellent product can fail because customers are too expensive to acquire.
Distribution should be considered before the product is finished.
A solo SaaS may appear to have a 90% cash margin because the founder does not pay themselves.
That does not mean the business has no labor cost.
Consider whether the income adequately compensates the time required to:
Develop
Support
Sell
Maintain
the product.
SaaS stands for Software as a Service.
Customers access the software over the internet and usually pay through recurring subscriptions or usage charges.
Common models include:
Monthly subscriptions
Annual subscriptions
Per-seat pricing
Usage-based billing
Tiered plans
Some companies also charge for implementation, support, or consulting.
There is no universal amount.
A founder who can build the software personally can launch a simple SaaS using infrastructure costing tens of dollars per month.
Development time is often the much larger investment.
A prototype can often be built almost entirely on free tools and free infrastructure tiers.
A serious commercial launch usually introduces at least some costs for areas such as:
Domain
Production infrastructure
Email
APIs
Monitoring
Free infrastructure also has usage and plan restrictions.
Income varies enormously.
MicroConf's independent SaaS survey found that 28% of companies were below $1,000 MRR, making this the largest revenue group in its dataset.
Large success stories should not be treated as typical results.
Yes.
A narrow product with manageable support and infrastructure can be operated by one founder.
As customer and product complexity grows, support, engineering, sales, and administration requirements can eventually require a team.
MRR means Monthly Recurring Revenue.
It measures normalized recurring subscription revenue generated each month.
ARR means Annual Recurring Revenue.
For a stable monthly subscription base, it is often approximated as:
MRR × 12
Churn measures customers or recurring revenue lost through cancellation or downgrade.
Lower churn generally makes recurring revenue more durable.
Net Revenue Retention measures how much recurring revenue remains from existing customers after cancellations, downgrades, and expansion.
NRR can exceed 100% when upgrades and expansion exceed lost revenue.
Only if it supports a clear growth strategy.
Free users still create infrastructure and support costs.
A free trial may be more appropriate for some products.
No.
Many SaaS businesses are bootstrapped.
SaaS Capital's 2026 dataset showed bootstrapped private B2B companies growing at a median 20% annually compared with 25% for equity-backed companies.
The appropriate financing model depends on growth goals and capital requirements.
Generally no.
Even a stable SaaS requires ongoing work such as:
Development
Infrastructure maintenance
Customer support
Billing
Marketing
Security
Product improvements
Automation can reduce operating work but does not eliminate it.
There is no reliable universal timeframe.
Some founders can sell before building the full product, while other products may operate for years without reaching meaningful revenue.
Customer problem, pricing, distribution, and founder experience matter more than a generic timeline.
Yes.
Acquire.com's 2025 transaction data reported a median confirmed SaaS sale multiple of approximately 3.9× annual profit for its marketplace transactions.
Individual valuations can differ substantially.
MicroConf — $0–10K ARR Founders — State of Independent SaaS benchmarks including the share of companies below $1,000 MRR and paying-customer counts.
SaaS Capital — 2026 Private B2B SaaS Company Growth Rate Benchmarks — 2026 survey of more than 1,000 private B2B SaaS companies covering median growth, bootstrapped versus equity-backed growth, and NRR relationships.
SaaS Capital — 2026 Spending Benchmarks for Private B2B SaaS Companies — Current private B2B SaaS spending benchmarks for hosting, DevOps, sales, marketing, R&D, customer success, G&A, and profitability.
SaaS Capital — Research — Current SaaS Capital research library covering private B2B SaaS growth, retention, spending, and valuation benchmarks.
Acquire.com — Biannual Acquisition Multiples Report, January 2026 — 2025 transaction data covering SaaS profit multiples, profitability, buyer interest, and time on market.
Acquire.com — Acquisition Multiples Report: 2025 Findings — Current transaction examples covering typical 3–5x net-income multiples and profit-based SaaS acquisition pricing.
Stripe — Pricing — Current U.S. standard payment-processing rate of 2.9% + $0.30 for successful domestic card transactions.
Supabase — Pricing — Current Free and Pro pricing, database capacity, monthly active users, storage, and production infrastructure limits.
Cloudflare Workers — Pricing — Current Workers Free plan and paid plan starting at a $5 monthly minimum.
Vercel — Pricing — Current Hobby, Pro, and Enterprise pricing, including the $20/month Pro platform fee and monthly usage credit.
Vercel — Pro Plan — Official 2026 documentation covering the $20 Pro platform fee, included deploying seat, and $20 monthly usage credit.
Linked pages
No published pages are linked from this document.