Last updated:
A SaaS pricing model defines what the customer pays for and how the bill changes. Packaging defines which features, limits, and service levels sit in each offer. Good pricing makes the value exchange understandable while supporting delivery, investment, and a reasonable margin.
Start with the value metric
The value metric is the unit that grows as the customer receives more value: active users, locations, transactions, records, processed volume, or another measurable outcome. It should be understandable, auditable, difficult to manipulate, and predictable enough for budgeting.
Stripe’s pricing and packaging guide also starts with the value metric before model and tier design. The right unit depends on the product and customer, not on whichever pricing page is fashionable.
Seven SaaS pricing models
Flat subscription
One product at one recurring price. It is easy to understand, but customers with very different use can create weak value alignment or uneven support cost.
Tiered plans
Packages serve distinct segments through different features, limits, or service. Tiers work when they reflect real customer needs and create a natural upgrade path.
Per-seat pricing
The bill grows with users. This fits collaboration and workflow products where adoption across a team creates value. It can discourage broad use or undercharge a small high-value team.
Usage-based pricing
Customers pay for what they consume, such as messages, storage, API calls, or transactions. It aligns with variable use, but both customer bills and vendor revenue can become less predictable.
Hybrid pricing
A base subscription covers platform value and a variable component covers usage. It can balance predictability and growth, at the cost of more explanation and billing complexity.
Freemium
A free plan gives limited ongoing value and paid plans expand capability. It works only when the free population supports distribution or learning without consuming unsustainable service cost.
Outcome or transaction pricing
The vendor charges when a defined result occurs or as a percentage of processed value. Alignment can be strong when attribution is clear. Disputes arise when the outcome depends on factors outside the product.
Design packages around segments
Describe the smallest customer, the growing customer, and the customer with advanced control or service needs. Give each package a coherent job. Avoid moving one essential trust feature, such as basic security, into a high tier merely to force an upgrade.
List every limit and what happens when it is reached. A clear upgrade, overage, pause, or block is better than a surprise invoice.
Test willingness to pay
Interview recent buyers about alternatives, budgets, approval, and the cost of the current problem. Present a real offer and observe decisions. Test price with comparable segments and record discounts separately. A survey answer about a hypothetical product is weak evidence.
Protect the economics
Model direct delivery cost by segment: infrastructure, third-party usage, payment fees, support, implementation, and other costs that grow with service. Compare expected gross margin, acquisition cost, payback, and retention under low, expected, and high-use cases.
Change pricing carefully
State who is affected, when, why, and what choices exist. Honour contracts and applicable consumer or commercial rules. Test billing transitions, prorations, tax treatment, downgrades, cancellations, failed payments, and refunds before rollout.
Pricing cannot rescue a product customers do not value, but it can hide or reveal the quality of the business model. Connect the decision to the recurring revenue model and monitor it with consistent SaaS metrics.
Why this matters for Mauritius businesses
Mauritius is rolling out MRA e-invoicing in phases by taxpayer category. The timetable and status can change, and MRA may separately notify a taxpayer, so businesses should check the current MRA e-invoicing page and their own notices before acting on a deadline.
The Codeblix approach
Codeblix eInvoicing is MRA-listed as an EBS Solution Provider (SN 95, BRN C24214425). The system handles every aspect of MRA compliance automatically - real-time fiscalisation, IRN tracking, QR code generation, hash chain maintenance, and monthly transaction reporting. The local support team in Chamouny is available to help with any MRA query, audit, or transition question.
What to do next
If your present process does not support the fiscal-invoice requirements that apply to your business, document the gap and test an appropriate EBS workflow. Codeblix can review your business requirements and onboarding scope before preparing a proposal; regulatory conclusions remain with the taxpayer and its advisers.
Frequently asked questions
The most common questions about saas pricing models: choose a value metric that can grow are covered in the FAQ section below. If you have a question that is not covered, the local Codeblix support team is available by phone, WhatsApp, or email.
Related resources
Codeblix publishes a regular blog covering MRA e-invoicing, VAT compliance, payroll, and business management for Mauritius businesses. The blog is updated weekly with new guides, how-tos, and case studies. You can also find detailed product documentation, video tutorials, and a knowledge base in the Help Centre.
Frequently asked questions
What is the best SaaS pricing model?
There is no universal best model. Choose a unit customers understand that tracks value, supports acceptable margins, and remains predictable enough for the buyer and operator.
Should SaaS pricing be based on competitors?
Competitor prices are context, not a complete answer. Customer value, segment, usage, delivery cost, positioning, and willingness to pay should shape the decision.