SaaS pricing models are not just packaging choices; they determine how software cost grows as a team adds users, uses more compute, or adopts higher service tiers. For B2B buyers, the practical task is to identify the real billing unit behind each product, because vendors in the source pack use materially different structures: Slack charges per user on paid plans, Railway combines usage billing with monthly minimums and included credits, and Notion mixes per-member plans with separate credit-based charges for some AI-related usage.
What it is and who it’s for
Stripe’s guide defines several common SaaS pricing models: subscription, usage-based, tiered, freemium, per-user, and flat-rate. In this context, subscription pricing means a set recurring charge, often monthly or annually, while usage-based pricing means the bill changes based on how much of the service a customer consumes.
For B2B buyers, the three models in this guide matter because they map to different operating realities:
- Per-seat pricing ties cost to the number of users or members.
- Usage-based pricing ties cost to measurable consumption such as compute, storage, or network use.
- Hybrid pricing combines more than one billing component, such as a recurring minimum plus metered usage, or per-member access plus separate consumption charges.
Stripe also notes that SaaS pricing differs from one-time software sales because it depends on ongoing access and support. That makes pricing structure a workflow and budgeting issue for team leads, finance owners, and procurement teams, not just a line-item comparison.
How it works
Per-seat pricing is the most straightforward model in the source pack. Slack’s paid plans are priced per user, per month, with both monthly and annual billing options on standard tiers. Notion’s paid plans are also charged per member, and its pricing page states that paid seats are prorated when members are added mid-month. In plain terms, that means the invoice rises as headcount rises, and timing of seat additions can affect the current billing cycle.
Usage-based pricing works differently because the bill follows actual consumption. Railway says it bills by usage, by the second, and then lists separate rates for memory, CPU, volumes, egress, and object storage. That means the customer is not simply buying a bundle of named features; the customer is paying for underlying resources consumed over time.
Hybrid pricing appears when a vendor combines access pricing and consumption pricing in the same offer. Railway’s Hobby and Pro plans are examples because each plan has a monthly minimum usage amount and includes that same amount in monthly usage credits, after which extra resource usage is charged separately. Notion also shows a hybrid pattern for some AI-related functionality: Custom Agents are free to try and then cost $10 per 1,000 monthly Notion credits, while the underlying workspace plans are charged per member.
Tiering sits across these models as a second layer. Slack organizes its product into Free, Pro, Business+, and Enterprise+ plans. Notion offers Free, Plus, Business, and Enterprise. Railway offers Free, Hobby, Pro, and Enterprise. Plan names alone do not reveal the underlying billing model; the buyer still has to determine whether each tier is primarily seat-based, usage-based, quote-based, or mixed.
Pricing and cost considerations
The biggest mistake in evaluating SaaS pricing models is to stop at the label and miss the actual cost components. A buyer should separate four questions: what triggers the base charge, whether there is a monthly minimum, whether usage overages apply, and whether annual billing changes the effective rate.
The source pack shows those patterns clearly:
| Vendor | Model in practice | Confirmed cost components |
|---|---|---|
| Slack | Per-seat subscription | Pro and Business+ are priced per user per month, with standard monthly and annual billing rates; Enterprise+ requires contacting sales |
| Notion | Per-member subscription with additional credit-based charges for some usage | Paid plans are charged per member; yearly billing can save up to 20%; Custom Agents cost $10 per 1,000 monthly Notion credits after the trial period; Enterprise is quote-based |
| Railway | Usage-based with monthly minimums | Hobby: $5 minimum usage with $5 credits included; Pro: $20 minimum usage with $20 credits included; metered usage billed after credits; Enterprise is custom |
A few buyer implications follow from these facts.
First, seat growth and usage growth are different budget risks. In Slack or Notion, headcount expansion is the main visible cost lever on paid plans because billing is tied to users or members. In Railway, the bill can rise even without adding more seats if workloads consume more CPU, memory, storage, or egress.
Second, annual billing affects comparability. Slack publishes different regular rates for monthly and annual billing on Pro and Business+. Notion says yearly billing can save up to 20%. When teams compare vendors, they need to decide whether they are comparing month-to-month flexibility or annual commitment pricing, because mixing those views distorts the analysis.
Third, minimums matter as much as rates in hybrid models. Railway does not operate as pure pay-as-you-go on its paid tiers; the Hobby and Pro plans each include a monthly minimum usage amount paired with included credits. A team with low usage still needs to account for that floor before it looks at metered overages.
Fourth, quote-based enterprise tiers reduce forecasting precision. Slack Enterprise+, Notion Enterprise, and Railway Enterprise all require sales engagement or custom pricing. That shifts part of the pricing exercise from self-serve comparison into negotiation, approvals, and scope definition.
How to choose
Start by identifying which resource grows fastest in your environment, then match the pricing model to it.
If the product’s value spreads mainly through collaboration, a per-seat model may be easier to forecast because the cost driver is the planned number of members or users. Stripe explicitly notes that per-user pricing may fit B2B services where value grows with team size. That can suit tools adopted department by department, where procurement already tracks licensed headcount. HubSpot, for instance, mixes per-seat pricing with edition tiers.
If the product’s cost is created by infrastructure consumption, a usage-based model may be a closer match. Railway’s pricing page makes that structure explicit by attaching rates to memory, CPU, volumes, egress, and object storage, as detailed in our Railway pricing guide. For engineering teams, that means forecasting depends less on procurement’s seat assumptions and more on expected workload behavior.
If the tool combines access and consumption, buyers should test whether the hybrid model matches how spend will actually accumulate. Notion is one example of why this matters: the workspace itself uses per-member billing on paid plans, while some AI-related functionality is measured in credits, as our Notion pricing guide details. In procurement terms, that creates at least two separate cost levers inside one product relationship.
A simple evaluation checklist from the source-backed facts is:
- Count whether spend will grow faster through members or through resource consumption.
- Check whether the vendor uses monthly or annual billing, or both.
- Identify any monthly minimum usage before modeling overages.
- Separate standard self-serve tiers from quote-based enterprise tiers.
- Match pricing structure to value delivery, because Stripe recommends pricing reflect customer value, costs, and market positioning.
Stripe also says SaaS companies can use customer data to inform pricing decisions and can adjust pricing over time as products and markets change. Because pricing can move, buyers should review renewal terms and vendor pricing-change notices before committing to an annual contract.
Limitations and gotchas
Per-seat pricing looks simple, but buyer assumptions can still break. Notion charges paid plans per member, yet guests are free of charge and can only access invited pages. That distinction matters for organizations that collaborate with external users, because “who needs a paid seat” is not always the same as “who needs some access.”
Usage-based pricing gives granular alignment between cost and consumption, but it can be harder to predict from a static procurement spreadsheet. Railway’s pricing is billed by the second and includes separate metered components, including egress at $0.05 per GB and object storage at $0.015 per GB-month with free egress. A buyer that models only average compute use and ignores network or storage behavior can underestimate spend.
Hybrid pricing can hide the true floor if a team notices the usage rates but misses the minimum commitment. Railway’s Hobby and Pro plans each combine a minimum usage amount with matching monthly credits rather than offering unlimited use inside a flat subscription.
Tier names can also obscure the commercial path to advanced security and administration controls. In the source pack, Business and Enterprise tiers carry items such as SAML SSO, SCIM provisioning, audit logs, RBAC, HIPAA BAAs, and customer success support, but those capabilities are not uniformly available on lower tiers or self-serve entry plans. Railway also ties some enterprise capabilities to minimum commitments, including HIPAA BAAs at $1,000, log history, RBAC, SSO, and audit logs at $2,000, support, cloud regions, and higher limits at $5,000, and dedicated VMs at $10,000.
Stripe recommends transparency about pricing structures and pricing changes. Buyers should therefore prefer vendors that make billing units, upgrade triggers, and plan-change mechanics explicit on the pricing page rather than only in the sales process.
FAQ
What happens when a team downgrades a plan?
Notion says downgrades take effect at the end of the billing cycle, so a mid-cycle downgrade does not free up budget immediately.
Are refunds addressed on any of the pricing pages in the source pack?
Notion says refunds are available within 3 days for monthly billing and 30 days for annual billing, and that EU and UK customers may have mandatory refund rights beyond 72 hours.
