SaaS pricing models, explained

Pricing is a product decision disguised as a spreadsheet. The model you choose shapes who buys, how fast you grow, and whether revenue tracks the value you deliver. Most founders copy a competitor's page and hope, but the right model depends on how your product creates value, not on what looks familiar.

The main models

Four patterns cover almost every SaaS on the market:

• Flat-rate. One price, everything included. Dead simple to sell, but leaves money on the table with big customers and scares off small ones.
• Per-seat. Charge per user. Predictable and easy to reason about, but it penalizes adoption, since adding teammates costs more, and it invites password sharing.
• Usage-based. Charge for what customers consume: API calls, storage, messages sent. Revenue scales with value, but bills become unpredictable and can trigger sticker shock.
• Tiered. Bundle features and limits into a few named plans. The most common model because it segments customers naturally and creates a clear upgrade path.

Match pricing to how you create value

The core question: when a customer gets more value, what metric grew?

If value scales with team size, per-seat is honest. If it scales with volume, transactions processed, tokens generated, gigabytes stored, usage-based aligns your revenue with their success. If value is roughly flat once someone adopts you, tiered or flat-rate keeps things simple.

Pick the metric your customer already associates with getting value. Billing for something they don't perceive as valuable feels like a tax.

The hybrid that usually wins

In practice, the strongest model for B2B SaaS is tiered with a usage component: named plans that bundle the features a segment needs, plus metered overages for the one dimension that scales. You get predictable base revenue and expansion as customers grow, the "land and expand" motion investors love.

• A free or low-friction entry tier to drive signups.
• Two or three paid tiers mapped to real customer segments.
• One metered dimension that grows the bill as usage grows.

Practical rules

• Anchor with three tiers. A middle option most people should pick, framed by a cheaper and a premium plan.
• Price on value, not cost. What you spend to run a feature is irrelevant to what it's worth to the buyer.
• Make the upgrade obvious. Customers should hit a limit that naturally pushes them up, not a wall that pushes them out.
• Instrument everything. From a PostgreSQL metering table to your billing provider, track usage precisely so invoices are never a surprise.

Don't over-optimize your first pricing. You will change it, pricing is iterative, and you learn the real willingness to pay only after customers are on the product. Ship a defensible v1, watch which plan converts, and adjust.

If you're building the billing and metering layer behind a pricing model, Stripe integration, usage tracking, tier gating, let's talk.