
Tenant Data Isolation: Patterns and Anti-Patterns
Explore effective patterns and pitfalls of tenant data isolation in multi-tenant systems to enhance security and compliance.
Jul 30, 2025
Read More

Pricing is architecture. A bad pricing model doesn't just leave revenue on the table — it attracts the wrong customers, creates billing friction, and makes your unit economics impossible to fix later without a painful migration. Yet most SaaS founders spend 10% of the time on pricing that they spend on code.
This post covers the three dominant SaaS pricing models in 2025 — subscription, usage-based, and hybrid — what makes each work, and how to pick one for your stage.
Subscription pricing charges a fixed recurring fee — monthly or annually — regardless of how much the customer uses the product. It's the oldest SaaS model and still the most common.
Variants:
When it works best: When your product delivers consistent value irrespective of usage volume — project management tools, design software, identity providers.
Revenue predictability: Excellent. ARR/MRR is clean to forecast.
Risk: Customers who use 10% of the product feel they're overpaying. High churn from low-engagement segments.
Usage-based pricing (UBP), also called consumption-based or pay-as-you-go, charges customers only for what they use. Stripe charges per transaction. Twilio charges per SMS/call. AWS charges per compute-hour.
Common usage metrics:
When it works best: Infrastructure, API products, communication platforms, AI/ML tools, and any product where a single customer's usage can vary 100x month-over-month.
Risk: Sticker shock from unexpected bills causes support escalations and churn. Low-usage months generate almost no revenue from otherwise healthy customers.
Hybrid pricing combines a fixed base subscription with variable usage charges on top. A $99/month base gives the customer access, then they pay per unit beyond a bundled allotment. This is increasingly the dominant model in 2025 — Snowflake, OpenAI, Datadog, and Vercel all use variants of it.
Structure patterns:
| Dimension | Subscription | Usage-Based | Hybrid |
|---|---|---|---|
| Revenue predictability | High | Low | Medium |
| Low-usage customer satisfaction | Low | High | Medium |
| High-usage customer satisfaction | High | Low | High |
| Sales complexity | Low | Medium | High |
| Billing infrastructure cost | Low | High | High |
| Best for | Tools/platforms | Infrastructure/APIs | Complex SaaS |
Pre-product-market fit (0–$1M ARR): Use tiered subscription. You need revenue predictability to survive, and usage-based billing requires sophisticated billing infrastructure and usage instrumentation that distracts from finding PMF.
Post-PMF, pre-scale ($1M–$10M ARR): Evaluate whether your best customers are being under-billed. If your top 20% of customers use 10x more than your bottom 20% and pay the same price, it's time to evaluate hybrid pricing.
Scale ($10M+ ARR): Sophisticated buyers expect consumption alignment. Enterprise contracts often include usage minimums with rollover credits and annual commits with overage billing quarterly.
Stripe's billing primitives map cleanly to these models:
stripe.subscriptions.create() with a fixed recurring price ID.stripe.subscriptionItems.createUsageRecord() with metered billing and aggregation mode (sum or max).For hybrid models, use Stripe Meters (GA in 2024) to track usage events in real time. This avoids the anti-pattern of self-reporting usage at the end of the billing month.
// Report usage to Stripe Meter
await stripe.billing.meters.createEvent({
event_name: 'api_calls',
payload: {
stripe_customer_id: customer.stripeId,
value: '1'
}
});
The pricing page is a product. Three principles that consistently lift conversion:
For usage-based products, show a usage calculator on the pricing page. Letting customers estimate their own bill reduces sticker shock and increases conversion from high-volume prospects.
Related: Common SaaS Development Challenges and How to Solve Them
Tiered subscription remains the most common model, but usage-based and hybrid models are growing fast — especially for AI, infrastructure, and API products where consumption varies significantly between customers.
When your top cohort consistently hits plan limits and either upgrades or churns, that signals your pricing doesn't scale with delivered value. That's when to evaluate hybrid or usage-based pricing seriously.
Create a subscription with two price objects — one flat recurring price and one metered price — on the same subscription. Use Stripe Meters to report consumption events in real time rather than batch-reporting at month end.
It can reduce churn from customers who feel they're overpaying on a subscription, but it can increase churn during low-usage periods when the product provides little value. Hybrid models with a base subscription protect against low-usage churn better than pure usage-based pricing.
Need an expert team to provide digital solutions for your business?
Book A Free CallDive into a wealth of knowledge with our unique articles and resources. Stay informed about the latest trends and best practices in the tech industry.
View All articlesTell us about your vision. We'll respond within 24 hours with a free AI-powered estimate.
© 2026 Propelius Technologies. All rights reserved.