SaaS & Product

You built a SaaS. Now comes the part that actually matters: how much do you charge? Pick the wrong model and you'll either leave $500k/year on the table or watch customers churn when they scale. Pricing isn't a number — it's the structure that ties your unit economics to your customer's value. Three patterns dominate SaaS in 2026: per-seat (team tools), usage (APIs and compute), and flat (productised services). Each works for a specific business shape. Picking the right one is a 10–15% swing in your lifetime value.

The Three Pricing Models Defined

Per-Seat (Team Tools)

You charge per user who accesses the product. $30/user/month, billed annually. Linear charges this way. So does Slack (historically), Notion, Figma. The model works when:

• Friction scales with headcount (more people = more chaos to organise)

• Switching costs are high once embedded (tight integration into workflow)

• Usage is unpredictable but adoption is binary (once they buy a seat, they use it)

Per-seat aligns your revenue with customer headcount, so you win when they grow. Downside: customers gate access ruthlessly ("we'll share one login") and you hit ceiling at $50k/seat when you try to move upmarket.

Usage-Based (APIs and Compute)

You charge per unit: API calls, inference tokens, storage gigabytes. Anthropic charges per million input/output tokens. AWS charges per compute second. This works when:

• Value scales directly with consumption (more data processed = more value extracted)

• Customers can't predict their bill in advance (they don't know if they'll hit 1M or 100M tokens)

• You want "bottoms-up" adoption (start free, scale paywalls as usage climbs)

Usage-based is fair in theory but terrifying in practice — a customer's surprise $50k bill kills renewal. It works best for infrastructure where enterprises have procurement teams that grok variable cost.

Flat-Rate (Productised Services)

One price, everyone pays. $99/month, $999/month, $2,999/month for three tiers. Webflow does this. So does HubSpot's entry tier. This works when:

• You serve SMBs who can't stomach variable cost (predictability matters)

• Usage is capped by product design (not every customer will hit 10M API calls)

• You want simple sales (no calculator, no negotiation, one price fits all)

Flat-rate is the simplest to sell but you'll leave money on the table from power users and lose upmarket deals because you're not priced for enterprise use.

Real Teardowns: Linear, Anthropic, Notion

Linear ($20–30/seat/month)

Team collaboration tool. Per-seat works because every engineer who joins your team needs access — you can't have half your staff blind to issues. They also offer a free tier (up to 10 teammates) which is smart conversion funnel. The catch: once you have 50 engineers, $20/seat becomes $12k/month, and you start looking for cheaper alternatives. Linear mitigates by selling into companies that are cash-heavy and value simplicity — growth companies that crossed $10M ARR. They don't price for bootstrappy agencies.

Anthropic API ($0.80–$2.40 per million tokens)

Usage-based because LLM cost is actually variable (they pay compute cost per token). But they give you monthly spending limits so you don't get surprise bills. This is genius — customers feel safe. They also tier pricing (Claude 3.5 Haiku is 8× cheaper per token than Opus) so you can start cheap and upgrade if you need better reasoning. The catch: a customer building a production app with 100k users will hit 1M+ tokens per day and suddenly realize usage-based is bleeding cash. That's when they switch providers or negotiate a volume deal (which Anthropic does).

Notion (Free + $10–$25/user/month)

Hybrid. Free for up to 10 members, then $10/user/month (billed annually). They also have a flat-rate "Notion Plus" tier for power-users who don't want team billing. Smart because they capture solo creators (free), grow into teams (per-seat becomes reasonable at $5–10 CAC), then keep power users who hate per-user pricing by offering a $10/month flat upgrade. It's like three pricing models bolted together and somehow it works.

Six Decision Branches: How to Pick Your Model

Branch 1: Does your customer's value scale with headcount or usage? If headcount (more engineers = more work to manage), per-seat wins. If usage (more API calls = more value extracted), usage-based. If neither changes much (productised service), flat-rate.

Branch 2: What's your ICP's size? Bootstrapped SMBs (under $2M ARR) hate variable cost. They want per-seat or flat. Enterprise customers with $100M+ revenue have procurement teams that budget for variable cost — usage-based is actually what they prefer (justifiable to finance).

Branch 3: Is adoption bottom-up or top-down? If your CTOs buy it (top-down), you can do per-seat or usage and negotiate enterprise pricing. If teams discover it, spread it, and demand it (bottom-up), per-seat is easier to justify to finance ("$100/month for Slack" is an easy yes).

Branch 4: Can you predict customer usage? If customers land in predictable buckets (small team, medium team, large team), flat-rate tiers work fine. If usage is genuinely unpredictable (API call volume varies 100×), usage-based is more fair.

Branch 5: What are competitors charging? If Linear (per-seat) is your closest comp, don't try to be cheaper on per-user pricing — you'll compress unit economics. Instead, move to a different model (per-project flat tier) and own a different segment.

Branch 6: What's your LTV vs CAC ratio today? If you're already at 3:1 LTV:CAC, you have breathing room to experiment. If you're at 1:1, you need a model that captures more revenue per customer — upgrade to usage-based tiers or expand per-seat pricing with add-ons.

Packaging Your Own SaaS: The Hybrid Playbook

Pick one primary model, then add a secondary escape hatch. Linear is per-seat but offers a free tier. Notion is per-seat but offers a flat Plus upgrade. Anthropic is usage-based but offers a $600/month flat cap.

For most bootstrapped SaaS, start with per-seat if you're a team tool (Slack-shaped) or flat tiers if you're a horizontal service (Zapier-shaped). As you scale past $1M ARR, bolt on a usage-based upgrade tier for power users. That way you don't leave money on the table, but customers who don't need it aren't gouged.

Six FAQs

Should I ever use pure usage-based from day one?

Only if your customers are technical (APIs) or you're B2B2C and your customer can absorb variable cost into their product's margin. Otherwise, start with a flat tier and move to usage tiers once you have 20+ customers and can model what "normal" looks like.

How do I stop customers from sharing one account?

Per-seat models can't stop seat-sharing perfectly. Notion lost millions to password-sharing. The real solution: tie per-seat pricing to value (we log logins, you only pay for active users), or move to per-feature pricing (everyone gets read, power users pay for write).

What's the right price for each seat?

$10–30/seat/month for SMB tools, $50–200+ for enterprise. If you're cheaper than $10/seat, you're losing money per customer. If you're pricing for enterprise ($100+/seat), your ICP has to be mid-market or above. Test during sales calls: would a 50-person team at $20/seat ($1k/mo) buy?

Can I mix per-seat with flat-rate?

Yes. Notion does it. Have per-seat as your default for teams, but sell a flat "Notion Plus" tier that caps spending ($192/year) so individuals or small teams don't feel nickeled. Makes them feel in control.

Should I offer a discount for annual commitment?

Yes, but discount off monthly not off annual sticker price. If you price at $30/month ($360/year), offer $300/year (15% discount for annual). That's enough to incentivize cash upfront without signalling that your monthly price is inflated.

When do I add "enterprise pricing"?

Once you have five customers spending $5k+/month. Before that, "enterprise pricing" is just you guessing. You'll leave money on the table or price so high you win zero deals. Get repeatable pricing from 5–10 mid-market customers first, then you can sell upmarket with data.

The Verdict

Price wrong and you'll either hemorrhage revenue or trigger churn the moment your customer scales. Per-seat for team tools, usage for infrastructure, flat for productised services. But the real move is hybrid: pick one primary model, add a secondary escape hatch, and watch your LTV:CAC ratio breathe. By the time you hit $1M ARR, you should have tested all three on your customer base and picked the shape that actually works. If you want help scoping pricing for your SaaS, check our pricing page — discovery calls are $499 and applied to your project.