Per-seat pricing

Charge per user, per month

The default for collaboration software. Every person who logs in is a seat, and revenue grows as your customer rolls you out to more of the team. Buyers understand it instantly because most of their stack already bills this way.

Best when

  • Value clearly grows with each extra person who uses the product.
  • The product is collaborative: shared workspaces, assignments, approvals.
  • Your buyer budgets by headcount and expects per-user prices.

Watch out

  • Seat prices punish adoption. Customers ration logins, and shared accounts appear.
  • If AI does more of the work in your product, seats stop tracking value. Fewer people get more done, and your revenue shrinks while delivered value grows.
  • Champions under-buy seats to keep the invoice small, which caps expansion.

Value metric: Active users. Charge for people who use it, not for names on a list. Seat minimums per tier keep small plans honest.

Three tiers, priced per user per month

Good, better, best. Gate collaboration depth, admin controls, and security (SSO, audit logs) as you go up. Never gate the core value a single user came for.

Anchor with the top tier

Show the enterprise tier even if it says Contact us. It makes the middle tier look reasonable, and the middle tier is where you want most buyers to land.

Default to annual

Show annual per-user prices first with a visible discount of 15 to 20 percent. Seat products live and die by retention, and annual billing buys you four quarters to prove value.

Flat-rate tiered pricing

Charge one price per plan, regardless of users

One price per tier, unlimited or generous limits inside each. The simplest model to explain, the fastest to buy, and the best fit for self-serve products where the whole account gets the same value no matter who logs in.

Best when

  • The product is single-player, or the whole account shares one outcome.
  • You sell self-serve at a low price point and every ounce of friction costs signups.
  • You want a pricing page a buyer can understand in five seconds.

Watch out

  • Your biggest customers pay the same as your smallest. Without capacity limits per tier, you leave real money with exactly the accounts that value you most.
  • You need a believable reason to upgrade. If the tiers only differ on minor features, everyone parks on the cheapest plan.

Value metric: A capacity limit that tracks value: projects, tracked competitors, monitored pages, contacts. Pick the one number customers grow with your product.

Three tiers with one clear capacity axis

Differentiate tiers on the capacity limit first and features second. Upgrades then happen naturally as the customer grows, without a sales conversation.

Price the jump between tiers at 2x to 2.5x

A $29 / $79 / $199 ladder reads as small, serious, team. Bigger jumps stall upgrades, smaller jumps are not worth the pricing-page complexity.

Put the middle tier forward

Mark it as most popular and make it the default selection. The top tier exists mostly to anchor, the bottom tier exists to remove risk.

Usage-based pricing

Charge for what customers consume

Pay for what you use: per request, per record, per gigabyte, per run. Revenue tracks delivered value one to one, entry price is near zero, and expansion happens without a renewal conversation. The trade is revenue predictability, on both sides of the invoice.

Best when

  • Value is machine-driven: APIs, infrastructure, data pipelines, AI workloads.
  • Your own costs scale with customer usage, so margins need protection.
  • Customers start small and grow a lot. Usage pricing removes the entry barrier.

Watch out

  • Bill shock kills accounts. One surprise invoice erases a year of goodwill.
  • Finance teams hate unpredictable line items. Expect pressure for committed-spend contracts as deals grow.
  • Forecasting your own revenue gets harder. Cohort usage curves replace simple seat math.

Value metric: The unit customers already use to describe their need: requests, messages, contacts, minutes. If you have to explain the unit, it is the wrong unit.

Give a free allowance, then meter

A monthly free quota lets developers integrate before procurement gets involved. The paid meter starts where hobby use ends.

Publish volume discounts

Stepped unit prices reward growth and pre-answer the negotiation every larger buyer starts. Predictable discounts beat secret ones.

Ship spend caps and alerts with the pricing

Budgets, alerts at 80 percent, hard caps on request. Bill-shock protection is not a feature of the billing page, it is the reason buyers trust the model.

Hybrid pricing

Charge a platform fee plus usage, or seats plus credits

A stable base price for access plus a variable part that tracks consumption. This is where much of SaaS is heading, because AI features put real usage costs inside products that used to have pure software margins. The base protects your floor, the meter captures the upside.

Best when

  • Both people and volume grow as the customer succeeds.
  • You sell mid-market or enterprise deals where a predictable base plus overage is the norm.
  • AI features give you real per-customer costs that seats alone would hide.

Watch out

  • Two pricing axes are harder to explain than one. Your pricing page has to work harder, and so does your sales team.
  • Billing complexity is real: metering, proration, credit expiry, overage invoicing. Budget engineering time for it.
  • Set the base too high and you lose the easy entry. Set it too low and the base stops protecting your floor.

Value metric: Seats for the humans, plus one consumption unit for the machine work: credits, runs, tokens, enriched records. Keep it to exactly two axes.

Base plan includes a usage allowance

Each tier bundles enough usage for a typical customer of that size. Most invoices stay flat, which keeps finance calm, while heavy users pay for what they burn.

Sell credits, not raw units, if usage is spiky

Prepaid credit packs smooth spiky consumption and turn overage from a surprise into a top-up decision the customer makes.

Let the meter drive expansion

Design the base to land the deal and the usage line to grow it. Expansion revenue from the meter is the whole point of running two axes.

Freemium vs free trial: the second decision

Whichever model you charge with, prospects still need a way in. This is an acquisition decision, not a pricing model, and it deserves its own answer.

Free trial

Full product, limited time. The right gate when value takes setup, data, or a workflow change to show up, and when serving a free user forever would cost you real money. A 14-day trial with an onboarding push beats a 30-day trial nobody finishes. Ask for the card only if your funnel can afford the drop: a card wall roughly halves trial starts and doubles trial-to-paid quality.

Best when

  • Value builds over days: integrations, imported data, monitoring baselines.
  • Each active account has real serving costs, so free forever does not scale.
  • Your buyer evaluates seriously and then decides, rather than dabbling.

Freemium

A free plan forever, limited by capacity or features. The right gate when the product proves its value in minutes, marginal cost per free user is near zero, and the market is big enough that a small conversion rate still feeds the funnel. The free tier is a marketing channel with a COGS line: size the limits so real business use bumps into them within weeks.

Best when

  • First-use value is instant and self-evident.
  • Serving a free user costs you close to nothing.
  • You are in a big market where free users compound into word of mouth.

Unlock the PDF playbook

Enter your email and the download starts right here in your browser. No spam. At most an occasional, genuinely useful pricing tip.