Pricing is one of the most consequential decisions a SaaS founder makes. It signals value, filters customers, and directly shapes revenue velocity. Yet most early-stage products default to whatever felt familiar at the time of launch.
This guide breaks down the five most common SaaS pricing models, when each works, and what trade-offs you are accepting when you choose one.
The Five Core Models
| Model | How it works | Best for |
|---|---|---|
| Free | No charge, ever | Developer tools, open source |
| Freemium | Core free, premium features paid | Consumer apps, viral B2C |
| Flat-rate | One price for everything | Simple tools, small teams |
| Per-seat | Price scales with users | B2B collaboration tools |
| Usage-based | Pay for what you consume | APIs, infrastructure, AI |
Free
Free products generate no direct revenue. They survive on adjacent monetisation: donations, consulting, a paid hosted tier, or strategic distribution that feeds a commercial product.
Free works when adoption itself is the goal — when distribution creates defensibility or when the free product is a funnel top for something else.
When it works: Open source projects, developer tools that benefit from ecosystem adoption, loss leaders for a paid product.
Watch out for: Sustainability. Free without a clear path to revenue is a liability, not a strategy.
Freemium
Freemium gives away a functional product and charges for expanded limits, advanced features, or team capabilities. The bet is that enough free users convert to paid to make the model work.
The math is brutal: most freemium products convert between 2% and 5% of free users to paid. Your free tier needs to be large enough to drive meaningful trial but constrained enough that valuable users hit the limit.
Conversion levers:
- Storage or usage limits
- Collaboration features (inviting teammates)
- Integrations with paid tools
- Analytics or reporting depth
- White-labelling or branding removal
When it works: Consumer apps with viral loops, tools where peer sharing drives adoption, products with clear upgrade triggers.
Flat-Rate
One product. One price. Everyone pays the same.
Flat-rate pricing is simple to understand and simple to sell. There is no pricing page to navigate, no tier comparison to study, and no negotiation. A customer either pays or does not.
The downside is revenue ceiling. Large enterprise customers who would happily pay 10x cannot, and small customers who barely use the product pay the same as power users.
When it works: Focused, single-purpose tools. Products with a narrow, homogeneous customer base. Early-stage products that need clarity over optimisation.
Per-Seat
Per-seat pricing charges based on the number of users accessing the product. It is the dominant model for B2B SaaS because it aligns cost with organisational value: as a team grows and adopts the tool more deeply, revenue grows naturally.
| Seats | Monthly (at $15/seat) |
|---|---|
| 5 | $75 |
| 20 | $300 |
| 100 | $1,500 |
| 500 | $7,500 |
Per-seat pricing creates a natural upsell path. Each new hire is a new billing unit. Each team that adopts the tool is new revenue.
Watch out for: Enterprises that negotiate hard on seat count, teams that share logins to avoid paying per user, and products where solo power users need to pay as much as a 50-person team.
Usage-Based
Usage-based pricing charges for consumption: API calls, messages sent, tokens processed, storage used, or compute time. The customer pays for exactly what they use.
Usage-based pricing is the most honest pricing model. It perfectly aligns cost with value delivered.
For infrastructure, APIs, and AI-powered products, it is often the only model that makes economic sense. A customer who makes 10 API calls should not pay the same as one who makes 10 million.
The challenge: Usage-based pricing is harder to budget for, harder to forecast, and harder to sell to procurement teams who need predictable costs.
Hybrid approaches combine usage-based variable cost with a flat base fee: a committed minimum that buys a block of usage, with overage charges above it. This gives customers predictability and gives you a revenue floor.
Choosing a Model
The right pricing model depends on three factors:
- Who your customer is — developer, team, or enterprise?
- How value scales — does it grow with users, usage, or features?
- What your GTM motion is — product-led growth, sales-led, or community?
Product-led growth products almost always start with freemium. Sales-led products do better with per-seat or flat-rate. Infrastructure products trend toward usage-based.
There is no universally correct answer — only the model that fits your product, customer, and growth motion best at this stage.
