SaaS

Recurring 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.

SaaS 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.^{[3][3]These figures describe private B2B SaaS companies in SaaS Capital's survey and are not representative of every SaaS business.}

Smaller profitable SaaS businesses can have very different economics. Among profitable SaaS businesses listed on Acquire.com, most reported profit margins of at least 50%, while the average margin among published businesses was 71% in 2025.^{[4][4]Acquire.com data is marketplace data and is strongly selected toward SaaS businesses whose owners are considering a sale.}

A SaaS product normally begins with a repeatable problem that software can solve for multiple customers.

The 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.

A typical web SaaS requires:

• frontend and application logic;

• database;

• user accounts and authentication;

• hosting;

• domain and DNS;

• HTTPS;

• billing;

• transactional email;

• analytics;

• backups and monitoring.

These components do not have to be built from scratch. Services such as Supabase, Stripe, Cloudflare, and managed hosting platforms can replace substantial amounts of custom infrastructure.

The initial product needs enough functionality for a customer to complete the activity they are paying for.

A production deployment should also have a method to identify failures, recover important data, and contact users when necessary.

Subscription products need a way to create plans, collect payments, renew subscriptions, handle failed payments, change plans, and cancel subscriptions.

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.

Customer acquisition differs substantially between SaaS types.

Independent 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.

The 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.

After launch, operating work can include:

• fixing production errors;

• answering support requests;

• monitoring infrastructure;

• handling failed payments and refunds;

• improving onboarding;

• shipping product updates;

• maintaining integrations;

• monitoring cancellations;

• backing up data;

• managing security issues.

Unlike a one-time software sale, subscription revenue must continually replace revenue lost when customers cancel.

Customers pay a recurring monthly or annual fee.

Example structure:

Actual prices are determined by the individual product rather than by SaaS as a category.

The customer pays according to the number of users or seats. Revenue can increase as a customer adds employees.

Charges are based on consumption such as API requests, storage, compute time, messages, processed documents, or another measurable unit.

Usage-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.

Different plans provide different limits or features. Customers can move to more expensive tiers as their requirements increase.

Some SaaS companies also sell:

• onboarding;

• implementation;

• consulting;

• premium support;

• additional storage or usage;

• integrations;

• training.

These are not necessarily recurring software revenue and should be distinguished from subscription ARR.

For standard U.S. pricing, 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.

The fixed transaction component makes payment processing proportionally more expensive for very small subscription charges.

Infrastructure can initially cost little or nothing when usage fits within free tiers.

Cloudflare Workers provides a free plan, while its paid Workers plan has a minimum charge of US$5/mo.

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.

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.

Infrastructure spending can increase with database size, bandwidth, file storage, compute, API usage, logs, backups, and traffic.

At 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.

For a founder-built product, development may require no direct cash payment but can represent the largest startup investment in time.

Larger 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.

These are benchmarks for established private B2B SaaS companies, not a recommended budget for a new product.