How to price your first B2B SaaS product

The short version. Price your first B2B SaaS product from the buyer's expensive workflow, then fit the package to the way that buyer already budgets. Copying loses signal. I would rather see a founder charge a simple uncomfortable price than copy a competitor's grid and inherit their strategy by accident. Start with a narrow paid segment, choose a value metric, set a floor you can defend, and use sales calls to test willingness.

Before you start:

• Start with the painful workflow and the budget owner; competitors only mark the corridor.
• Pick a value metric before a price, because the paid unit shapes buyer risk.
• Write the floor before the demo, because live discomfort creates weak discounts.
• Use every quote as evidence about the segment and the proof around the paid unit.

Step 1: Anchor on an expensive workflow, then write what done looks like

Start with the workflow. Your first price should come from a messy job inside the buyer's week, where delay creates cost, audit risk, missed revenue, or founder anxiety that already has a budget shadow. If the pain sounds broad, the price will wobble. A narrow workflow gives you language for the sales deck and a reason to avoid feature-by-feature haggling.

I use discovery notes as the pricing lab, because buyers usually reveal budget logic when they describe what happens before your product and what breaks after the old process fails. Price follows pain. The earlier positioning playbook helps here because price follows the alternative you displace. Done looks like a named workflow beside a named buyer, plus a sentence that says why delay costs money.

• Workflow named in buyer words
• Current workaround named
• Budget owner identified
• Delay cost written plainly

Step 2: Ask which customer should anchor price, then write what done looks like?

Choose the customer who feels the problem most sharply, even if that segment looks smaller than the market slide you showed investors. Be selective. A vague average buyer turns the first price into mush, while a sharp early segment gives you a cleaner willingness-to-pay test and a cleaner outbound list.

Keep India budgets and US budgets in separate rows until the buyer is real enough to quote. If your first serious buyers sit in the US, the market-entry choice in India-first or US-first matters because procurement norms travel into pricing calls. Done looks like a primary segment with a reject segment beside it, plus an explicit reason the primary buyer feels more pain.

• Primary buyer named
• Reject segment named
• Budget context separated
• Pain intensity explained

Step 3: Pick the paid unit, then write what done looks like

Pick the unit first. Stripe Billing supports subscription billing and usage-based billing in the same product area at https://stripe.com/docs/billing, which is a useful reminder that SaaS price architecture is a billing choice as much as a positioning choice. Seats work when each user receives separate value. Usage works when volume tracks value, while outcome fees demand trust and measurement that first-time vendors rarely have yet.

An AI product has extra pressure here, because compute costs can punish a flat plan when heavy users behave very differently from light users. The separate AI pricing note covers that edge case, but the principle stays simple: the unit should rise when the buyer gets more value. Done looks like a value metric that finance can understand and product can measure.

• Value metric chosen
• Metering path known
• Heavy use protected
• Buyer risk visible
• Invoice story clean

Step 4: Set a confident price floor, then write what done looks like

Write the walkaway price before the next demo. Panic hides. A founder who invents price while the buyer watches will usually sell the buyer's discomfort back to themselves as a discount before the real objection appears. The first floor should feel slightly high and still defensible from the workflow cost you already heard.

Competitors can mark a corridor, yet they cannot give you courage. Investopedia defines value-based pricing as setting price mainly from perceived customer value at https://www.investopedia.com/terms/v/valuebasedpricing.asp, which matches how I want a founder to defend the first offer. Done looks like a written floor beside a default quote, plus a sentence explaining the value logic.

• Walkaway price written
• Default quote written
• Discount reason limited
• Value sentence rehearsed

Step 5: Package the offer for the sales motion, then write what done looks like

Match the package to the way the deal will close. Shape reduces friction. A founder-led motion can carry a higher explanation burden because the founder can translate risk and handle security anxiety while reframing the old workflow during the call. A self-serve page needs cleaner limits because the buyer has to understand the package without your voice in the room.

If sales is still founder-led, the discovery habit in Founder-led sales: the playbook for your first customers should shape the quote as much as the pricing page. When the product is already self-serve, When to layer sales onto a self-serve product helps separate buyer education from packaging confusion. Done looks like a quote format that matches the channel and removes an avoidable objection.

• Quote mirrors sales motion
• Plan limits are clear
• Security burden accounted
• Expansion path visible
• Objection removed before call

What goes wrong

Founders underprice for emotional reasons. This creates bad data. They want kindness from the buyer or proof for the investor update, so they turn price into apology before the product has had a fair test. Cheap can still be expensive when it attracts the wrong account.

Big quotes wobble. A giant quote with weak discovery turns the call into procurement cosplay, and the buyer can smell the gap between the promise and the founder's proof. Discounting also lies. Once every early deal carries a special exception, you lose the ability to learn whether the segment is wrong or the proof around the unit is weak.

• Apology discounts
• Fake enterprise theater
• Confusing paid unit
• Blended buyer segment
• Silent procurement risk

Step 6: Turn every quote into evidence, then write what done looks like

Treat the first paid quote as a test instrument. The response matters. A buyer's words after price reveal urgency, budget owner, procurement path, competitive alternative, and the story they need to repeat inside the buying committee before procurement begins. A clean loss with a clear reason can improve price faster than a messy yes with hidden concessions.

Log the exact words around price, because the phrasing tells you whether the buyer saw a budget line or a nice-to-have experiment. If nobody came after launch, the same evidence discipline in zero-users triage plan helps separate pricing failure from distribution failure. Done looks like a pricing log that pairs objections with accepted quotes and planned changes.

• Exact quote captured
• Objection language saved
• Win reason written
• Loss reason written
• Next change decided

Common questions

How should I price my B2B SaaS product?

Price it from the buyer's costly workflow and the value metric that grows with value. I would pick a specific segment and name the alternative they fund today, then set a floor you can defend in a sales call. Competitor pages can frame the corridor. Your first real signal comes from whether the buyer accepts the logic before they negotiate the amount.

Should I copy competitor pricing?

Copying competitor pricing gives weak signal. Their page reflects their costs, sales motion, brand trust, and history, while your first product has different proof. Use competitors to spot obvious market boundaries. The real price should come from the pain you displace and the paid unit your product can measure, with buyer budget logic kept visible.

Should my first SaaS price be public?

Public pricing works when the buyer can understand the package without a founder translating risk. If the deal needs security discussion or workflow diagnosis before legal can move, a guided quote usually teaches more early. A public starting point can still help inbound buyers self-select. The key is keeping the same value logic across the page and the sales call.

Should I charge per seat or usage?

Use seats when value maps to people. Use usage when value rises with volume and the buyer can predict the bill well enough to trust it. For AI products, usage often protects margin, while a flat plan can feel simpler to buy. The right unit is the unit the buyer believes and your system can meter.