How to price a B2B SaaS product before you have customers (the methodology).

B2B SaaS pricing: the framework, the common mistakes, and the evidence that separates a defensible answer from a confident one.

Most early-stage SaaS founders underprice their product. The reason is psychological more than analytical. Founders new to enterprise sales worry that customers will balk at a high number, so they pick a number low enough that they feel comfortable defending it. The result is a price that signals low value, attracts low-quality buyers, and creates margin problems that compound through every subsequent round. The fix is a deliberate pricing methodology that produces a defensible number before you have a single paying customer.

There are three primary methodologies for setting SaaS prices: cost-plus, competitor-based, and value-based. For most B2B SaaS products at early stage, value-based pricing is the right methodology, with competitor benchmarking as a sanity check. Cost-plus is mostly irrelevant for software where marginal cost is near zero.

Cost-plus pricing starts with the cost to deliver the product and adds a margin. This methodology is appropriate for hardware, services, or any business where marginal cost is significant. For software, marginal cost is usually a small fraction of price, and cost-plus produces a number far below what the market will bear.

Competitor-based pricing starts with what comparable products charge and positions relative to them. This methodology is appropriate as a sanity check and as a constraint (you usually cannot price 5x the closest competitor without specific justification), but it does not produce the right number on its own. Competitors may be underpriced or overpriced for their own reasons.

Value-based pricing starts with the economic value the product produces for the customer and captures a fraction of that value. This methodology produces the highest defensible price and is the right starting point for most SaaS products.

Value-based pricing requires you to quantify what the product is worth to the customer. The components are: what does the customer save in labor, what does the customer gain in revenue, what does the customer reduce in risk, and what does the customer avoid in cost. The sum of these components is the customer's total economic value.

For a compliance automation product targeting financial services SaaS companies: a SOC 2 audit cycle takes a compliance team 14 days at fully loaded cost of $1,500 per day per person, so $21,000 per cycle. The product reduces this to 4 days, saving $15,000 per audit cycle. The product also reduces external auditor fees by 30 percent due to better-organized evidence, saving an additional $8,000 per audit. With three audit cycles per year, the total annual economic value is approximately $69,000.

The pricing question is what fraction of $69,000 the product captures. Industry benchmarks suggest 10 to 30 percent capture rate for new categories, with established categories at 5 to 15 percent. A 15 percent capture rate produces a $10,350 annual contract value, which rounds to $10K or $12K depending on positioning.

Before you have paying customers, you can test willingness to pay through structured conversations. The framework: describe the product in outcome-oriented terms (specific deliverables, specific time savings, specific economic impact), then ask "what budget would you allocate to a tool that delivered this reliably?" The answers will be imprecise and optimistic, but the distribution of responses tells you the rough order of magnitude.

Run this test with five to ten target buyers. If the distribution clusters around $8,000 to $12,000 annual, your $10K price is in range. If the cluster is $2,000 to $4,000, your $10K price is too high for the segment and you need to either reduce price or target a different segment with higher willingness to pay. If the cluster is $20,000 to $30,000, you are underpriced.

Once you have the per-customer price, you need to choose a pricing model. The three primary models are per-seat (price scales with number of users), per-usage (price scales with consumption like API calls, transactions, or data volume), and flat-rate (one price per customer regardless of usage).

Per-seat works when the product is used by individual contributors and value scales with usage. Most workflow tools and productivity products use per-seat pricing. The drawback is that customers can game the model by sharing seats, which limits revenue growth from existing customers.

Per-usage works when the product produces measurable output that customers can attribute to the product. API products, data products, and infrastructure products often use per-usage. The drawback is that customer spend becomes unpredictable, which makes budget approval harder and lengthens sales cycles.

Flat-rate works when the value is consistent regardless of usage. Compliance products, security products, and some vertical SaaS products use flat-rate. The drawback is that flat-rate captures less value from heavy users, which is sometimes intentional (predictable customer spend) and sometimes a problem (you are leaving money on the table).

The standard SaaS pricing tier structure has three options: Starter, Professional, Enterprise. According to ProfitWell's 2024 pricing benchmark covering 2,400 SaaS companies, the median Starter tier is priced at 25 to 35 percent of the Professional tier, and the Enterprise tier is priced at 2.5 to 4x the Professional tier. The Professional tier should be the primary offer that 60 to 70 percent of customers buy.

The purpose of Starter is to provide a low-friction entry point for buyers who want to try the product before committing to the Professional tier. The purpose of Enterprise is to capture additional value from buyers with more complex needs (more seats, advanced features, premium support).

Three mistakes recur. First, anchoring on the wrong reference price. Founders coming from consumer SaaS or freemium products often anchor on $29 per month or $99 per month, which works for consumer products and is far below what B2B buyers expect to pay. Most B2B SaaS products should be priced above $200 per month for SMB and above $1,000 per month for mid-market.

Second, pricing for the smallest plausible customer rather than the target customer. Founders sometimes set price based on what the smallest customer in their pipeline can afford, which produces a price too low for the larger customers they actually want. The fix is to price for the target customer and let the smaller customers self-select out.

Third, leaving pricing flat too long. Most successful SaaS companies raise prices every 12 to 18 months as the product improves and the customer base matures. Founders who set a price at launch and never adjust it leave significant revenue on the table over time.

Build the value-based price by quantifying customer economic value and capturing 10 to 30 percent of it. Sanity-check against competitor pricing as a constraint, not as a target. Test willingness to pay with five to ten target buyers using outcome-oriented descriptions. Choose a pricing model that aligns with how value scales for your customers. Use three tiers with the middle tier as the primary offer. Most early-stage founders underprice. The discipline of building the price from value rather than from comfort produces a number that is defensible, that signals appropriate value, and that supports the unit economics investors will require at later stages. For the unit-economics side of pricing, see startup unit economics explained and CAC payback period explained.