IncomeWiki

Revision 1

SaaS

@namkyu · Aug 26, 2026, 3:59 PM

Added a practical overview of SaaS startup economics, revenue, costs, workflow, tools, retention, and acquisition benchmarks.
+18,970−0
1Software as a Service (SaaS) is software delivered over the internet and commonly monetized through recurring subscriptions or usage-based charges. SaaS ranges from solo-operated niche products to large B2B platforms, so startup cost, pricing, revenue, and operating requirements vary substantially by product and customer type.
2
3# Quick Facts
4
5
6| Item | Practical benchmark |
7| ----------------------- | -------------------------------------------------------------------------------------------------------- |
8| Common revenue model | Monthly or annual subscription |
9| Other revenue models | Usage-based pricing, per-seat pricing, tiered plans, add-ons |
10| Smallest practical team | One founder can build and operate a small SaaS |
11| Early-stage revenue | 28% of independent SaaS companies in MicroConf's 2024 survey were below US$1,000 MRR |
12| Payment processing | [Stripe](/wiki/stripe): 2.9% + US$0.30 per successful domestic card transaction in standard U.S. pricing |
13| Hosting | Can begin on free or low-cost infrastructure |
14| Database/backend | Free tiers are available; [Supabase](/wiki/supabase) Pro starts at US$25/mo |
15| Major ongoing risks | Customer churn, infrastructure costs, customer acquisition, platform/vendor dependency |
16
17
18SaaS should not be treated as a single uniform market. A solo product charging US$10 per month and an enterprise SaaS company selling US$100,000 contracts have very different economics.
19
20# Earnings
21
22SaaS revenue outcomes are extremely unequal, particularly among independent products.
23
24In MicroConf's 2024 State of Independent SaaS data, **28% of independent SaaS companies generated less than US$1,000 in monthly recurring revenue (MRR)**, making this the largest revenue group in its survey. The same dataset reports that 65% had only 1–10 paying customers and more than half had fewer than 50.\[\* These figures describe independent and bootstrapped SaaS companies participating in MicroConf's survey, not the entire SaaS industry.\]
25
26This means that reaching meaningful recurring revenue should not be assumed simply because a SaaS product has launched.
27
28At the other end of the market, SaaS Capital's 2026 survey included more than 1,000 private B2B SaaS companies. Across the survey, companies reported a median annual growth rate of 22%; bootstrapped companies reported 20% and equity-backed companies 25%.\[\* These are established private B2B SaaS companies and should not be interpreted as expected results for a new SaaS product.\]
29
30For bootstrapped B2B SaaS companies already generating US$3M–20M ARR, SaaS Capital reported median annual revenue growth of 15% and 90th-percentile growth of 42.3% in 2026.
31
32## Revenue is not profit
33
34Recurring revenue can produce attractive economics once a product has an established customer base, but revenue must pay for infrastructure, development, customer support, payment processing, marketing, administration, and employees or contractors.
35
36SaaS Capital's 2026 private B2B SaaS survey found that bootstrapped respondents had median total spending equal to **96% of ARR**. 83% were profitable or within two percentage points of breakeven. Equity-backed companies had median spending equal to 101% of ARR, with 52% profitable or near breakeven.\[\* These figures describe private B2B SaaS companies in SaaS Capital's survey and are not representative of every SaaS business.\]
37
38Smaller profitable SaaS businesses can have very different economics. Among profitable SaaS businesses listed on [Acquire.com](/wiki/acquire-com), most reported profit margins of at least 50%, while the average margin among published businesses was 71% in 2025.\[\* Acquire.com data is marketplace data and is strongly selected toward SaaS businesses whose owners are considering a sale.\]
39
40# Minimum Entry Setup
41
42A software developer who already owns a computer can build and launch a simple SaaS without purchasing servers or expensive development software.
43
44
45| Requirement | Minimum option | Cost | Priority | Notes |
46| -------------------- | ------------------------------------------------------------------------ | ---------------------------------------------: | --------------------------------- | ----------------------------------------- |
47| Development computer | Existing computer | $0 additional | Essential | Suitable existing hardware can be used |
48| Code editor | [Visual Studio Code](/wiki/visual-studio-code) or similar | Free | Essential | Paid IDE is optional |
49| Source control | [GitHub](/wiki/github) | Free tier | Essential | Stores and manages application code |
50| Application hosting | [Cloudflare Workers](/wiki/cloudflare-workers) or another free-tier host | Free tier | Essential | Limits depend on provider |
51| Database/backend | [Supabase](/wiki/supabase) | Free tier | Essential for many products | Free tier includes a PostgreSQL database |
52| Payment processing | [Stripe](/wiki/stripe) | No setup or monthly fee for standard payments | Essential when charging customers | Transaction fees apply |
53| Analytics | Hosting analytics or free analytics service | Free options | Recommended | Useful for measuring activation and usage |
54
55
56A custom domain is normally added before serious commercial launch, but the domain price depends on the registrar and top-level domain.
57
58The practical minimum is therefore primarily **development time rather than large upfront capital** when the founder can build the software and use free infrastructure tiers.
59
60A production service may need paid hosting, database capacity, email delivery, monitoring, backups, support software, and other services as usage increases.
61
62# Practical Workflow
63
64## Identify a problem and customer
65
66A SaaS product normally begins with a repeatable problem that software can solve for multiple customers.
67
68The target customer matters operationally. Selling a low-priced self-service tool may require a simple checkout and automated onboarding, while B2B products with large contracts can require sales calls, demonstrations, procurement, security reviews, contracts, and manual onboarding.
69
70## Build the application
71
72A typical web SaaS requires:
73
74- frontend and application logic;
75- database;
76- user accounts and authentication;
77- hosting;
78- domain and DNS;
79- HTTPS;
80- billing;
81- transactional email;
82- analytics;
83- backups and monitoring.
84
85These components do not have to be built from scratch. Services such as [Supabase](/wiki/supabase), [Stripe](/wiki/stripe), [Cloudflare](/wiki/cloudflare), and managed hosting platforms can replace substantial amounts of custom infrastructure.
86
87## Deploy a usable version
88
89The initial product needs enough functionality for a customer to complete the activity they are paying for.
90
91A production deployment should also have a method to identify failures, recover important data, and contact users when necessary.
92
93## Add billing
94
95Subscription products need a way to create plans, collect payments, renew subscriptions, handle failed payments, change plans, and cancel subscriptions.
96
97[Stripe Billing](/wiki/stripe-billing) can provide subscription management on top of Stripe payments. Merchant-of-record services are another option and may take responsibility for additional payment and tax functions in exchange for higher fees.
98
99## Acquire the first customers
100
101Customer acquisition differs substantially between SaaS types.
102
103Independent SaaS companies in MicroConf's survey identified SEO and word of mouth among their highest-impact marketing channels. Other products may rely on outbound sales, marketplaces, paid advertising, communities, partnerships, integrations, or existing audiences.
104
105The acquisition method should match the product's price. A low-priced product cannot normally support the same manual sales process as a high-value B2B contract.
106
107## Operate and retain customers
108
109After launch, operating work can include:
110
111- fixing production errors;
112- answering support requests;
113- monitoring infrastructure;
114- handling failed payments and refunds;
115- improving onboarding;
116- shipping product updates;
117- maintaining integrations;
118- monitoring cancellations;
119- backing up data;
120- managing security issues.
121
122Unlike a one-time software sale, subscription revenue must continually replace revenue lost when customers cancel.
123
124# How It Makes Money
125
126## Subscriptions
127
128Customers pay a recurring monthly or annual fee.
129
130Example structure:
131
132
133| Plan | Example customer |
134| ---------- | -------------------------------------------- |
135| Individual | One user |
136| Team | Multiple users |
137| Business | Larger teams or additional features |
138| Enterprise | Large organizations with custom requirements |
139
140
141Actual prices are determined by the individual product rather than by SaaS as a category.
142
143## Per-seat pricing
144
145The customer pays according to the number of users or seats. Revenue can increase as a customer adds employees.
146
147## Usage-based pricing
148
149Charges are based on consumption such as API requests, storage, compute time, messages, processed documents, or another measurable unit.
150
151Usage-based products can generate more revenue as customers use the product more heavily, but the SaaS operator's infrastructure or third-party API expenses may also increase.
152
153## Tiered pricing
154
155Different plans provide different limits or features. Customers can move to more expensive tiers as their requirements increase.
156
157## Additional revenue
158
159Some SaaS companies also sell:
160
161- onboarding;
162- implementation;
163- consulting;
164- premium support;
165- additional storage or usage;
166- integrations;
167- training.
168
169These are not necessarily recurring software revenue and should be distinguished from subscription ARR.
170
171# Costs
172
173## Payment processing
174
175For standard U.S. pricing, [Stripe](/wiki/stripe) charges **2.9% + US$0.30** for a successful domestic card transaction. Stripe lists an additional 1.5% for international cards and 1% when currency conversion is required.
176
177The fixed transaction component makes payment processing proportionally more expensive for very small subscription charges.
178
179## Hosting and infrastructure
180
181Infrastructure can initially cost little or nothing when usage fits within free tiers.
182
183[Cloudflare Workers](/wiki/cloudflare-workers) provides a free plan, while its paid Workers plan has a minimum charge of **US$5/mo**.
184
185[Supabase](/wiki/supabase) provides a free tier with a 500 MB database. Its Pro plan starts at **US$25/mo** and includes 8 GB of database disk space and US$10/mo of compute credits.
186
187[Vercel](/wiki/vercel) offers a free Hobby plan intended for personal, non-commercial projects. Its Pro plan, intended for professional and business use, costs **US$20/mo** for the included deploying seat and includes US$20 in monthly usage credit.
188
189Infrastructure spending can increase with database size, bandwidth, file storage, compute, API usage, logs, backups, and traffic.
190
191At much larger scale, infrastructure becomes a material operating expense. SaaS Capital's 2026 survey of private B2B SaaS companies found median hosting spending equal to **5% of ARR** and DevOps spending equal to another **4% of ARR**.
192
193## Labor
194
195For a founder-built product, development may require no direct cash payment but can represent the largest startup investment in time.
196
197Larger SaaS businesses add engineering, sales, marketing, customer success, support, and administrative labor. In SaaS Capital's 2026 private B2B dataset, median spending included 22% of ARR on R&D, 15% on sales, 8% on marketing, 9% on customer support/customer success, and 15% on general and administrative costs.
198
199These are benchmarks for established private B2B SaaS companies, not a recommended budget for a new product.
200
201# Software, Services & Tools
202
203
204| Tool | Price | Level | Main use |
205| ---------------------------------------------- | ----------------------------: | ------------ | --------------------------------------------- |
206| [GitHub](/wiki/github) | Free tier | Beginner | Source control and collaboration |
207| [Cloudflare Workers](/wiki/cloudflare-workers) | Free tier; paid from US$5/mo | Intermediate | Application hosting and serverless compute |
208| [Supabase](/wiki/supabase) | Free; Pro US$25/mo | Beginner | Database, authentication and backend services |
209| [Vercel](/wiki/vercel) | Hobby Free; Pro US$20/mo | Beginner | Web application deployment |
210| [Stripe](/wiki/stripe) | Transaction-based | Intermediate | Payments |
211
212
213The exact stack depends on the application. A SaaS may instead use [Amazon Web Services](/wiki/amazon-web-services), [Google Cloud](/wiki/google-cloud), [Microsoft Azure](/wiki/microsoft-azure), self-managed servers, or other infrastructure.
214
215# Requirements
216
217There is no universal license or certification required simply to create SaaS.
218
219The actual requirements depend on where the company and customers are located and what data or industry the software handles.
220
221A commercial product commonly needs:
222
223- a legal entity or other appropriate business structure where required;
224- a bank account and payment account capable of receiving customer payments;
225- terms of service;
226- privacy disclosures;
227- appropriate tax handling;
228- security appropriate to the data being stored.
229
230Products handling healthcare, financial, children's, or other regulated data can face additional requirements.
231
232Selling internationally can also create tax and privacy obligations that do not exist for a purely local product.
233
234# Retention
235
236Customer retention has unusually large effects on a subscription business because canceled recurring revenue must be replaced before new sales produce net growth.
237
238SaaS Capital's 2025 private B2B SaaS data illustrates how retention differs by contract size. Companies with annual contract values of US$25,000–50,000 reported median net revenue retention (NRR) of **102%**; the bottom quartile was 97% and the top quartile 111%.\[\* NRR includes expansion from existing customers, such as upgrades and price increases, so it can exceed 100%.\]
239
240Retention characteristics can be very different for inexpensive self-service SaaS and high-contract-value B2B SaaS. These figures should therefore not be applied to every SaaS product.
241
242# Selling a SaaS Business
243
244A profitable SaaS can itself become a sellable asset.
245
246Acquire.com's 2026 report on confirmed marketplace transactions found that SaaS businesses sold at a **median 3.9× profit multiple in both 2024 and 2025**. Its marketplace primarily covers businesses with enterprise values below US$10M.
247
248Among more than 136 deals examined in its 2025 transaction data, businesses below US$100,000 in net income averaged a 3.7× multiple and those with US$100,000–1M in net income averaged 3.9×.
249
250These are observed acquisition-marketplace transactions rather than guaranteed valuations. Growth, retention, profit, owner involvement, customer concentration, and other factors can materially change what a buyer will pay.
251
252# Risks / Things to Know
253
254- **Many products remain small.** In MicroConf's independent SaaS dataset, 28% were below US$1,000 MRR. Building functioning software does not establish that customers will pay for it.
255- **Churn compounds.** Subscription customers who cancel remove future recurring revenue. Products with weak retention must continually acquire new customers simply to replace lost revenue.
256- **Infrastructure costs can scale with usage.** Database, compute, bandwidth, storage, email, AI/API usage, and monitoring costs can rise as customers use the product. Usage-based SaaS is particularly exposed when customer charges do not adequately cover variable infrastructure costs.
257- **Customer acquisition can become a major expense.** SaaS Capital's established private B2B respondents spent a median 15% of ARR on sales and another 8% on marketing in 2026.
258- **Third-party dependencies create operational risk.** Payment processors, hosting providers, app marketplaces, APIs, email providers, and authentication services can change prices, limits, policies, or availability.
259
260# Sources
261
262- [SaaS Capital — 2026 Private B2B SaaS Company Growth Rate Benchmarks](https://www.saas-capital.com/research/private-saas-company-growth-rate-benchmarks/)
263- [SaaS Capital — 2026 Spending Benchmarks for Private B2B SaaS Companies](https://www.saas-capital.com/blog-posts/spending-benchmarks-for-private-b2b-saas-companies/)
264- [SaaS Capital — 2026 Benchmarking Metrics for Bootstrapped SaaS Companies](https://www.saas-capital.com/blog-posts/benchmarking-metrics-for-bootstrapped-saas-companies/)
265- [SaaS Capital — 2025 Private SaaS Retention Benchmarks](https://www.saas-capital.com/blog-posts/what-is-a-good-retention-rate-for-a-private-saas-company/)
266- [MicroConf — State of Independent SaaS](https://microconf.com/state-of-indie-saas)
267- [MicroConf — Independent SaaS: US$0–10K ARR](https://microconf.squarespace.com/founders/0-10k-arr)
268- [Acquire.com — 2026 Acquisition Multiples Report](https://blog.acquire.com/acquire-com-biannual-acquisition-multiples-report-jan-2026/)
269- [Stripe — Pricing & Fees](https://stripe.com/pricing)
270- [Stripe Billing — Pricing](https://stripe.com/billing/pricing)
271- [Supabase — Pricing](https://supabase.com/pricing)
272- [Vercel — Pricing](https://vercel.com/pricing)
273- [Cloudflare Workers — Pricing](https://developers.cloudflare.com/workers/platform/pricing/)