How much should you charge for your B2B SaaS? Early-stage pricing without data

Short answer. Charge the highest price a narrow buyer can defend from a painful workflow, then sell it manually until the objections repeat. For early B2B SaaS, I would set a price tied to a business outcome. I would add a floor that protects support time, with a package simple enough for a founder to explain in a cold email.

In short:

• Pick the buyer before the price; a horizontal price guesses at value and teaches you little.
• Use value as the anchor, but set a floor from support load and onboarding time.
• Quote manually before publishing a grid; early calls are where price becomes evidence.
• Raise price when deals close cleanly and buyers stop pushing back.

What price should you start with when you have no data?

Start narrow. A founder with no closed-won pattern should choose the smallest buyer segment where the product removes a budgeted headache, because that buyer can argue for price without needing category education. Your starting price is a hypothesis about pain and the budget owner who owns that pain. The seed-stage version sits inside How to price your B2B product at seed stage.

I would avoid the safe little number that makes every prospect nod and every contract unprofitable. Pick a floor. If the contract cannot fund customer work while leaving room for product fixes, the price trains you to chase noisy accounts all quarter and starves the accounts that could expand.

Which buyer sets the number?

The buyer sets the number. Price follows the person who feels the wound and controls a budget line because that person can survive internal review with a clean business case today. A user with delight and no budget gives you feedback dressed as demand. Before price, tighten the buyer map through How to figure out your first ICP before you waste a year selling to everyone.

A US buyer may carry a different willingness to pay than the India buyer who helped you shape the product. Be careful. The same workflow can sit under another executive and a harder procurement habit once it moves across markets, so a copied price can hide a broken segment choice until pipeline slows. I would treat geography as a pricing variable when the sales call changes from founder trust to vendor risk.

Should you price by seat, usage, outcome, or package?

Choose the metric that matches the customer's proof moment. Simple wins. If the buyer gets value when a team adopts the product, seat pricing will feel natural, while a workflow that scales with calls, records, tokens, or transactions can justify usage pricing.

Public price menus can teach you the shape of a model without giving you the number for your product. AWS shows consumption pricing at https://aws.amazon.com/pricing/, and OpenAI's API page shows metered model pricing at https://openai.com/api/pricing/. Treat those pages as grammar, because your buyer's pain still sets the noun.

• Seat metric: value rises with named users
• Usage metric: value rises with volume
• Flat package: value needs handholding
• Outcome anchor: value maps to saved budget

How do you test price without burning trust?

Test price in a live sales conversation, with the buyer's spreadsheet open and the problem stated in their words. Stay human. A founder can say the price is early and the package will tighten as implementation help becomes clearer through the actual work inside the account this month.

I prefer a manual quote before a pricing page because every objection carries context. Write it down. If prospects pause at the same line item, you have a packaging problem; if they pause at the total, you have a value proof problem in the deal. That distinction matters.

When should the price go up?

Raise price when clean deals close without founder discount theatre. Watch the calendar. If buyers sign after normal security questions and still pull colleagues into the product after the kickoff, the old number has become a drag on learning. Low prices can make serious accounts doubt the product.

Do not wait for perfect retention math. Early pricing moves through sales evidence before dashboards catch up, and the useful evidence is buyer language that repeats across calls. If proof suggests a sales-led motion, the frame in PLG or sales-led? The right GTM motion follows proof can stop you from copying a public pricing grid too early.

What should go on the pricing page?

Publish less than you want. A pricing page for an early product should answer who the package is for and what work is included, with enough fit language to prevent junk calls. Keep the grid quiet until the sales script can defend each boundary. Your early page is a filter.

The copy matters more than the table styling. I would connect price to the buyer's job through plain homepage language, especially if your current site still sounds like investor copy; From pitch deck to homepage: Messaging that converts, not investor copy is the cleaner frame. Atlassian's Jira pricing page shows how public packaging can name plans and scope at https://www.atlassian.com/software/jira/pricing/.

Common questions

How do I decide what price to charge for my B2B SaaS?

Choose a narrow buyer and anchor the number to a painful workflow. Then set a floor that pays for onboarding and support. If the buyer cannot repeat the business case in their own words, the price is floating. I would rather start high with a clear package than low with vague usage promises.

Should I show pricing on my website before I have customers?

Show package shape before exact numbers if sales calls still change the offer. A page can say who it serves and what work is included, with enough fit language to keep junk calls away. Exact public numbers make sense when the founder can defend every boundary without editing the offer in the call.

Is per-seat pricing better than usage pricing?

Per-seat pricing works when adoption by named users creates value. Usage pricing works when volume creates value and the customer can predict the meter. The wrong metric creates procurement friction. The right metric makes the invoice feel like the buyer's own spreadsheet.

How do I know my price is too low?

It is too low when buyers accept without debate and support cost swallows the contract. Another signal is expansion without executive attention, because the product may be useful while the account size stays unserious. Raise the next quote before changing old contracts unless the old contract already allows a scheduled increase.

Should India pricing carry into the US market?

Treat India pricing as a clue, then rebuild the number from US procurement and vendor risk. The buyer may value the same workflow through a different budget owner. If the sales call moves from personal trust to security review, the package and price should move with it.