SaaS Pricing Models: The GTM Decision Most Founders Get Wrong

Most founders treat pricing like an accounting question. You build the product, you survey three competitors, you pick a number that feels defensible, and you move on to the next fire. The number lives on the pricing page. Sales quotes it. Finance models off it. Done.

That framing is why so many SaaS startups stall.

Your pricing model: the structure of how you charge, not the dollar amount, decides who sells your product, how fast deals close, and whether product-led growth is even possible for you. Pick the wrong one, and you spend two years discovering you’ve boxed yourself out of self-serve, or that your sales team can’t quote anything in under three weeks because your “simple” tiered plan has nineteen line items.

This piece is not a list of every pricing model that exists. The internet has enough of those. This is a working framework for picking a pricing model based on your go-to-market motion, your stage, and the moves you’re going to want to make later. It covers the six pricing models you actually need to understand, with real examples you can pull apart, and the one distinction — pricing versus packaging — that competitors keep glossing over.

Why SaaS pricing is a GTM decision, not an ops one

Three things follow from your pricing model that founders rarely connect back to it.

1. Who sells for you. Per-seat pricing under $20/user/month sells itself — the buyer can swipe a card. Per-seat over $50 needs sales. Usage-based, with unpredictable bills, almost always needs a customer success motion to handle the “why was my bill different this month” conversation. Outcome-based pricing needs a sales rep who can defend the value claim. The pricing model picks the team you have to hire next.

2. How fast deals close. A clean three-tier list-price page with predictable annual numbers closes in days. A custom-quoted usage forecast with platform fees, overage rates, and committed-use discounts closes in months. If your sales cycle is 90 days and you wish it were 14, the answer is usually in the pricing model, not the sales team.

3. Whether PLG is even on the table. Self-serve onboarding requires a buyer who can predict their bill before they swipe. Per-seat works. Tiered with clear limits works. Pure usage-based with no calculator on the page does not — finance buyers will not approve it without a meeting. If you want a PLG motion and your pricing requires a quote, the pricing has to change before the GTM does.

Founders default to per-seat because it’s what they saw at the last company they worked at. That’s not a reason. The reason should be: this model lines up with how we want to sell, who we want to sell to, and what we want our growth to look like in 18 months.

The 6 SaaS pricing models, ranked by GTM fit

Here are the six models that cover roughly 95% of B2B SaaS in market, and the GTM motion each one actually supports.

1. Per-seat (per-user) pricing

You charge a fixed price for each user added to the account. Add a sales rep, pay for a sales rep.

Real example: Linear. $10/user/month on Basic, $16/user/month on Business, Enterprise on a custom annual contract. Free tier supports unlimited members but caps you at 250 issues across two teams, which is the upgrade trigger.

Why founders pick it: Predictable revenue per customer. Easy to forecast. Easy to explain. Every B2B SaaS sales rep on earth knows how to quote it.

The GTM consequence nobody mentions: Per-seat actively kills product-led growth inside companies. The moment your product becomes useful to a team, the IT manager turns off self-serve invites and routes new seats through procurement. You’ve trained your champion to limit who uses the product, because every new user costs them money. Slack solved this with the freemium gate. Most startups don’t think about it until it’s too late.

Use when: Your buyer is a manager with a defined team and per-seat budget. The product is intrinsically per-user (CRM, support tool, code editor). You want sales-led GTM and you’re OK with a heavier rep org.

Avoid when: Your product creates value at the workspace level, not the user level (analytics dashboards, billing systems, status pages). Charging per-seat for those forces customers to share logins, which they will.

2. Tiered pricing

Three to four named plans with progressively more features and higher prices. The buyer picks the tier that has the feature they need.

Real example: Slack. Free → Pro ($7.25/user/month annual) → Business+ ($15/user/month) → Enterprise+ (custom). Each tier unlocks specific features — message history, SSO, compliance — that map to specific buyer pain points at specific stages of company size.

Why founders pick it: It’s the safe default. It works for self-serve and sales-led at the same time. Buyers self-segment into the right tier by what they ask for in the trial.

The GTM consequence: Tier design is more important than tier price. If your most-requested feature is on the highest tier, your sales team will spend every call defending the gap. If it’s on the lowest tier, you’ll never sell up. Most tier design fails because product, sales, and finance each get a vote and nobody owns the outcome.

Use when: You serve more than one customer segment with one product, and the segments value different features. This is most B2B SaaS.

Avoid when: Your product is genuinely one thing for one buyer at one price. Adding tiers in that case creates fake decisions and slower conversions.

3. Usage-based pricing

The customer pays for what they consume. APIs charge per call, communications platforms per message, AI products per token.

Real example: Twilio. $0.0083 to send an SMS. $0.0085 a minute to receive a voice call. $0.0013 to send an email through SendGrid. No seats, no tiers, no annual minimums for the core API. You pay for usage.

Why founders pick it: The pitch aligns price with value perfectly. Customers don’t pay for shelfware. As the customer’s business grows, your revenue grows. Investors love this for the net revenue retention story.

The GTM consequence: Usage-based pricing crushes self-serve adoption inside enterprises. Procurement cannot approve a budget line that says “between $5,000 and $40,000 a month depending on traffic.” Every usage-based company that scales upmarket ends up adding committed-use contracts, platform fees, and minimum spends — because that’s the only thing enterprise finance will sign. Your “modern, fair, usage-based” pricing becomes a tiered annual contract with a usage rider underneath it. That’s not bad, but it’s not the original story.

Use when: Your product has a clean, defensible value metric that the customer already counts (messages, API calls, transactions). Your buyer is a developer or technical operator who can predict their own usage.

Avoid when: Your customer cannot predict their own usage. If your product creates the demand it then meters, customers will distrust the bill on principle.

4. Flat-rate pricing

One product, one price, regardless of users or usage. The simplest model in the market.

Real example: Basecamp Pro Unlimited. $299 a month, flat. Unlimited users, unlimited projects, 5 TB of storage. The pricing page has one number on it. (Note: Basecamp also offers a per-user “Plus” tier at $15/user/month, so Basecamp itself is not pure flat-rate — but the Pro Unlimited tier is the cleanest flat-rate model in B2B SaaS.)

Why founders pick it: Sales cycle of zero. Friction of zero. The buyer reads the price, decides yes or no, and moves on.

The GTM consequence: Flat-rate leaves money on the table at scale. A 500-person customer pays the same as a 10-person customer. You will spend years watching enterprise buyers happily pay 1/50th of what they’d pay anywhere else. Basecamp is comfortable with this trade because it matches their brand and their refusal to chase enterprise. Most startups discover the trade isn’t comfortable around Series B.

Use when: You serve SMB or prosumer markets, you have a strong brand position around simplicity, and you don’t plan to chase enterprise.

Avoid when: You want to land SMB and expand to enterprise. Flat-rate has no expansion path inside the customer — they buy once and never pay more.

5. Freemium

A free tier exists, with hard limits that push paying users into a paid plan. Technically freemium is an acquisition model, not a pricing model — but it’s where every modern self-serve company starts and so it has to be in this list.

Real example: Notion. Free (1 member, unlimited blocks for individuals; capped blocks for 2+ members; 7-day page history; 5 MB file uploads). Plus at $10/member/month. Business at $20/member/month. Enterprise custom.

The limits matter more than the price. Notion’s free tier is generous enough that an individual will never pay, but the moment a second person joins, blocks and uploads tighten and the upgrade prompt does its job.

Why founders pick it: It produces a top of funnel that paid acquisition can’t match for cost.

The GTM consequence: Freemium only works when conversion is engineered into the product, not bolted on at the end. The teams that win at freemium spend more time on the upgrade UX than the marketing site. The teams that lose at freemium have a free tier that does too much, an upgrade page that’s an afterthought, and a six-month runway problem.

Use when: Your product gets meaningfully better with collaboration, and the second user is the upgrade trigger. You have the engineering capacity to design the free→paid transition as a first-class product surface.

Avoid when: Your product is enterprise-priced and you’re hoping freemium will create awareness. It won’t. Sales-led products do not benefit from freemium.

6. Hybrid and outcome-based pricing

The model that almost no comparison article covers in any depth, and the one most mature SaaS lands on. You charge a base subscription (often per seat) plus a usage or outcome component on top.

Real example: Intercom + Fin. Seats start at $29/month on Essential, $85/month on Advanced, $132/month on Expert. On top of that, Intercom’s AI agent Fin charges $0.99 per resolution — and a resolution is defined as the customer confirming the issue is solved, the customer not asking again after Fin’s reply, or Fin completing a workflow handoff. You pay once per conversation regardless of how many questions get answered.

That’s the cleanest example of outcome-based pricing in market. You don’t pay per token, per minute, per agent — you pay per result.

Real example #2: Zapier. Tiered plans (Free, Professional from $19.99/month, Team from $69/month) sit on top of monthly task limits. Run a Zap, use a task. Hit the limit, you can pay 1.25× the base task rate for overage or upgrade to a higher task tier. This is tiered subscription plus metered usage in one model.

Why founders pick it: It compounds. The base subscription anchors retention. The usage or outcome layer captures upside without renegotiating the contract. The customer feels they’re paying for value as it accrues, not for shelfware.

The GTM consequence: Hybrid models require pricing operations the day they launch. You need usage reporting, threshold alerts, soft caps, and a billing system that can do mid-cycle prorations. Most early-stage startups can’t ship that, which is why hybrid is usually a Series A+ move.

Use when: You have a defensible outcome metric (a resolution, a closed ticket, a generated lead) and a buyer who’ll pay more for results than for access. AI products are the obvious fit.

Avoid when: You’re still figuring out which metric to charge against. Picking a value metric wrong is harder to walk back than picking a price wrong.

Pricing is not packaging — and the distinction matters

Pricing is the number. Packaging is what’s inside the box at that number.

Most startups that “have a pricing problem” actually have a packaging problem. The price is fine; the wrong features are bundled together. Champions can’t sell up because the feature they want is locked behind a tier their CFO won’t approve. Sales reps quote discounts to close because the Pro tier is missing a single SSO toggle that lives on Enterprise.

Repackaging is almost always cheaper, faster, and lower-risk than repricing. Move SSO down a tier. Pull team-management features out of Enterprise and into Business. Bundle the API into Pro. You can do this without telling existing customers anything; they’ll just unlock features they were already paying for, and your churn drops next quarter.

Repricing — actually changing the dollar amount — is a much larger event. It triggers grandfather clauses, communication plans, and a wave of renewal conversations. Most founders reach for it first because it feels like the obvious lever. It rarely is.

How your stage changes your pricing model

The pricing model that fits at seed is rarely the one that fits at Series B.

Pre-PMF. Stay flat-rate or one simple tier. Your job is to learn what customers value, not to optimize what they pay. Friction is your enemy. Anything that requires a quote slows you down. Pick a number, charge it, change it later.

Seed → Series A. Move to tiered. You should now know two or three customer segments well enough to package for them. Tiering forces you to ask which features belong to which segment, which is one of the most useful exercises you can run at this stage.

Series A → Series B. Add a usage or outcome layer if your product has one. You’re large enough to have pricing ops, you have customer data on actual usage patterns, and your investors want to see net revenue retention above 110%. A hybrid is how you get there without renegotiating every contract.

Series B+. Custom enterprise tier. Annual contracts. Committed-use discounts. None of this is glamorous. All of it is necessary.

How to choose your pricing model: a decision framework

Three questions, in this order.

1. What is the smallest unit of value your product creates? A user? A workspace? A message sent? A ticket resolved? A dollar earned? The honest answer to that question is your value metric. Your pricing model should charge against that metric.

2. What’s your dominant sales motion? Self-serve buyers need predictable, list-priced models — per-seat tiered or flat-rate. Sales-led motions can quote usage-based, outcome-based, or hybrid. Mixed motions need a list-priced floor with a custom-quoted ceiling.

3. Where do you want to be in two years? If you want to land SMB and expand to enterprise, you need a model that has room to grow inside the customer — that means tiered or hybrid. If you want to dominate SMB and stay there, flat-rate works. If you want to be the Twilio of your category, plan for usage-based from day one and accept the enterprise procurement friction that comes with it.

The matrix:

Frequently asked questions

What’s the most common SaaS pricing model?
Tiered subscription pricing is almost always combined with per-seat charges inside each tier. Slack, HubSpot, Zoom, and most major B2B SaaS run this structure.

How is B2B SaaS pricing different from B2C?
B2B is almost always per-seat or per-organization with annual contracts and committed-use minimums. B2C is closer to consumer subscription pricing — a single flat monthly or annual rate per individual user. The annual contract is the structural difference.

Which pricing model works best for early-stage startups?
Flat-rate or a single tier, until you know two customer segments well enough to package for them. Multi-tier pricing before product-market fit creates decisions you don’t have the data to make.

Why do most SaaS companies use tiered pricing?
Because it handles multiple segments with one product. The Pro buyer and the Enterprise buyer want different things; tiering lets you sell to both without forking the product.

When should a startup switch from per-seat to usage-based pricing?
When your customers tell you that the per-seat model is making them ration access. If your champion is locking new users out to control budget, you’re losing data and engagement to your own pricing model. That’s the signal to add a usage or hybrid component.

How often should you change your SaaS pricing?
Repackaging — moving features between tiers — can happen quarterly. Repricing — changing the actual dollar amounts — should happen at most once a year, and ideally tied to a feature launch or a major release that gives you a reason to talk to customers about value.

What’s the difference between pricing and packaging?
Pricing is the number on the page. Packaging is the set of features behind that number. Most startups blame pricing for problems that are actually packaging problems.

Pricing is downstream of your go-to-market plan. Pick the model that lines up with how you want to sell, who you want to sell to, and where you want to be in two years. The number is the easy part. The structure is what compounds.