SaaS Pricing Strategy

Pricing conversations usually start in the wrong place. Someone opens a competitor’s pricing page, screenshots three tiers, and argues about whether 49 dollars should be 59. That argument is the last of four decisions, and the least valuable one.

The order that matters: value metric, packaging, price point, discount policy. Get the first two right and the number almost sets itself. Get the metric wrong and no amount of copywriting rescues it.

The four decisions, in the order they should be made

Decision one is the value metric. What unit are you charging for, and does it grow as the customer succeeds? Decision two is packaging: which features live in which tier, and what forces an upgrade. Decision three is the price point, which is arithmetic once you know willingness to pay. Decision four is discount policy, which is the difference between the price you publish and the price you collect.

Notice the asymmetry. The decision that’s hardest to reverse is the one most teams make fastest, usually in the first six months of the company’s life, by copying whatever the nearest competitor does. The decision that’s easiest to reverse gets the most meeting time.

Picking the value metric: the decision tree

Start with three inputs: your ACV band, your gross margin structure, and your sales motion. Those three narrow the model set to one or two candidates.

If your costs scale with usage, as in infrastructure, messaging or AI inference, usage based pricing is close to mandatory. Snowflake charges compute credits because storage and compute are its cost of goods. Twilio charges per message for the same reason. Fixed pricing on a variable cost base is how companies discover negative gross margin on their largest accounts.

If value scales with the number of people doing work, seats win. Figma charges for editors rather than viewers, which is precise: a viewer costs Figma nothing and spreads the file, an editor is the person getting the value. That distinction, editor versus viewer, is worth more than any pricing page redesign Figma has ever shipped.

If value scales with work completed rather than people, use an outcome unit. Zapier’s task pricing is the clean example. A solo operator running 50,000 tasks a month pays more than a 200 person company running 2,000, which is correct, because the value tracks automation volume, not headcount.

Model	Best for	Expansion behaviour	Forecastability for buyer	Main failure mode
Per seat	Collaboration, CRM, design	Steady, tied to hiring	High	Seat sharing and stagnant headcount cap growth
Usage or credits	Infrastructure, data, messaging, AI	Strong and automatic	Low, buyers hate surprise bills	Bill shock and procurement friction
Tiered feature	Early stage, simple products	Weak, upgrade only	Very high	Everyone lands in the middle tier forever
Hybrid seat plus usage	Mid market to enterprise	Strong	Medium	Complexity in quoting and billing
Per transaction or outcome	Payments, recruiting, support deflection	Very strong	Medium	Attribution arguments about which outcome you caused

The extended version of this comparison, including revenue share and platform fee models, is in SaaS pricing models compared. If you are leaning toward consumption, the migration mechanics and the bill shock controls are covered in usage based pricing for SaaS.

Packaging: what actually forces the upgrade

Packaging fails in a specific and diagnosable way. Everyone lands in the middle tier and stays there for three years.

That happens when the gate between tiers is a feature nobody needs rather than a limit everyone eventually hits. Good gates are quantitative: seats, contacts, records, environments, API rate. Bad gates are qualitative: advanced reporting, priority support, custom branding. Qualitative gates give the buyer a reason to say no once. Quantitative gates give them a reason to say yes eighteen months later without a conversation.

HubSpot’s unbundling of seat types is the most instructive recent example in B2B. Rather than one price per user, seats are split by what the person does, so a company with 12 people who need full access and 40 who need visibility pays for exactly that. It raised the ceiling on large accounts and lowered the entry cost at the same time, which is the rare packaging change that helps both ends of the market.

A few rules that hold up:

• Three paid tiers plus an enterprise contact option. Four tiers confuses, two leaves money on the table.
• Put one gate per tier boundary that the customer will predictably cross.
• Never gate security and SSO behind the top tier if you sell to companies with a security review. It reads as a tax and shows up in every comparison article about you.
• Name tiers for the buyer, not for the size. “Team” and “Business” beat “Silver” and “Gold”.

Setting the price point from willingness to pay

Competitor screenshots tell you what a different company decided about a different product for a different segment, at a moment you cannot see the context for. They are a sanity check, not an input.

The usable method is direct research, and it does not require a research agency. Thirty structured conversations with a mix of customers, churned accounts and lost deals will produce a defensible range. Ask two calibrated questions per segment: at what price does this become expensive but worth considering, and at what price does it become so expensive you would not buy. The gap between those two answers, aggregated, is your acceptable band. Then check the top of the band against your win rate data.

Whether to publish the resulting number is a separate question with a real tradeoff, laid out in public pricing versus contact sales. The short version: publish under roughly 25,000 dollars entry ACV, because self qualification is worth more than negotiating influence at that size.

Discount governance and net price realization

List price is a marketing decision. Net price is an operations decision, and it is the one that shows up in revenue.

Most teams do not know their net price realization. Pull it: total contracted ARR divided by what that same set of contracts would cost at list. If you land below 80 percent, discounting is structural rather than exceptional, and the fix is process rather than exhortation.

That last row is the one that matters. A quarter end discount does not just cost margin on that deal. It teaches an entire buying market that waiting until the last week of March is profitable. The approval workflow that prevents this, including the routing and the escalation thresholds, is in the discount approval workflow, and the broader policy design is in SaaS discounting strategy.

The 90 day repricing rollout

A price change is a cross functional project, not a pricing page edit. The sequencing below protects existing revenue, which is the thing pricing projects most often damage.

Days 1 to 30: decide and model. Finalise the value metric and packaging, model the revenue impact across your existing base account by account, and identify which customers would see an increase above 20 percent. Those accounts are your risk list. Build entitlement mapping in your billing system before anything is announced, because discovering that your billing platform cannot express the new packaging is a four week delay that always arrives at the worst moment. The tooling constraints here are covered in SaaS pricing and billing tools.

• Days 31 to 60: launch on new business only. New logos get the new price. Existing customers see nothing. Watch win rate, average deal size and sales cycle length weekly against the prior quarter. Two things to expect: a temporary dip in win rate as reps adjust, and at least one loud internal voice claiming the price killed a deal that was never going to close.

Days 61 to 90: migrate existing customers. Announce at least 60 days before the renewal date, in a message from a named human rather than a no-reply address. Offer a 12 month grandfathering window to accounts on the risk list, and only to them. Blanket grandfathering feels safe and creates a two tier customer base you will still be untangling in three years.

The full checklist, including the billing, entitlement, CS enablement and comms sequencing, is in the 90 day pricing and packaging refresh.

How to measure whether it worked

Four numbers, reviewed quarterly. ARPA tells you whether packaging changed what people buy. Net price realization tells you whether discipline held. Net revenue retention tells you whether the value metric expands. Win rate tells you whether you went too far.

The trap is reading any one of them alone. Win rate falling 6 percent after a 20 percent price increase is a clear win, and it will still be reported as a problem by whoever owns win rate. Agree in advance which combination counts as success, and write it down before the first number lands.

The position, stated plainly

Most B2B SaaS is underpriced relative to the value it delivers and over-discounted relative to its own published list. The combination is why pricing work has an unusually high return compared with most marketing projects, and why it keeps getting deferred: it requires agreement across sales, finance, product and marketing, and every one of them has a reason to delay.

Start with the value metric, because it sets the ceiling on everything else. Then make the change annual, dull and well communicated. Exciting pricing is usually a symptom of something else going wrong. If you need the segment specific version of this, B2B SaaS pricing strategy goes deeper on enterprise contracting, and value based versus cost plus pricing settles the philosophical argument that tends to stall these projects in week two.

What to do next

Calculate your net price realization this week. It takes an hour with a CRM export and a list price sheet, and it is the single number most likely to change what you do next quarter.

If it comes back under 85 percent, your project is discount governance, not repricing. If it comes back above 90 percent and your win rates are strong, you are underpriced, and the value metric conversation is where to start.