Pricing and packaging should be a growth lever for SaaS companies. However, few businesses effectively manage to build a responsive, flexible pricing infrastructure that serves the company as a lever rather than a bottleneck.
Homegrown systems governing SaaS pricing and packaging end up costing companies millions of dollars per year as they scale. These primarily come from development, maintenance, and opportunity losses.
These systems force engineering to work on logic that isn't new value instead of product innovation. They also delay new pricing initiatives.
In this article, we'll teach you how to build a flexible pricing and packaging system to maximize control and eliminate the need to reinvent the wheel when it comes to the code architecture.
To build a flexible SaaS pricing and packaging system, you should analyze your target market, identify your value metric, and combine pricing models to match how your product delivers value.
Develop your packaging strategy, decouple pricing from code, and keep iterating to use pricing and packaging as a growth lever.
An effective system depends on key components: product catalog, company profile, metering, subscriptions, and flags to control access and limits.
Schematic supports flexible pricing and packaging in addition to hybrid selling without hard-coded logic.
Before building a flexible pricing and packaging system, you need the right elements to support its architecture. Here are the core components to have:
The product catalog is a policy file that describes a company’s products, also known as SKUs or plans, and their associated entitlements.
Products can describe platforms, pricing tiers, or add-ons. The definition of a product should include default values for allocations or limits and their pricing strategy.
The catalog should also reflect all changes to enterprise products offered to customers, including those that may no longer be actively sold. This can be referenced across systems to inform support, billing, marketing, and sales teams.
The company profile is a centralized record of existing customer accounts. It integrates all relevant company traits, subscription information, and usage data into a single, coherent profile.
Assign a unique key to every profile and enforce it across the system to prevent duplicates.
Keep every company profile updated, whether the account is free, paid, or inactive.
It's also important to maintain history to track profile changes over time.
Metering involves tracking usage patterns of features or services. This is especially important in usage-based pricing, where you charge customers based on actual consumption.
Metered features can be monetized or unmonetized (e.g., tracked for telemetry or enforcing a packaged usage limit).
Make sure usage tracking supports idempotency. It should also include a company key, feature key, and a datetime, which forms the basis for billing and insights into company behavior.
You can process usage in real time or in batches based on performance requirements.
The subscriptions component is the relationship between the product catalog and the company profile. It should describe information about the start and end time of the subscription, price, and allocations or limits.
Add a subscription as soon as a new customer converts. You can create extra subscriptions at any time for free trials, upgrades, or plan cancellations.
A company profile may have more than one active subscription. These subscriptions should never be deleted.
In aggregate, subscriptions should represent a historical record of change orders.
This component also helps GTM or RevOps teams answer questions about a customer’s bill, what products they have access to, and upcoming pricing changes.
Flags define who gets access to what features or services based on their context. This ensures customers can use only the features they should have access to. It is useful for restricting access in trials, free tiers, and premium offerings.
Company access is technically a smart flag check that occurs at the feature level, informed by the parameters of a company’s subscription and the product catalog. This check should never occur at the plan level so that plans can shift as the business changes.
You should grant flags permissively. If SaaS entitlements for a given company are conflicting, apply the more permissive one.
The steps below help product and engineering teams build a flexible pricing and packaging system that can accelerate revenue growth.
Before developing your SaaS pricing and packaging system, you should know your target market.
Start with a clear view of your customers. Group them by industry, business size, location, and average revenue, which can affect the customer's willingness to pay for your SaaS product.
Next, conduct interviews and surveys to learn customer needs. Ask them about their current pain points, budget, and decision-makers.
If you already have existing customers, you can analyze their usage data. This reveals which specific features they use and where they exceed limits. It also ties directly to product market fit. If your pricing does not match how your best users see value, it will not scale.
Don't forget to study your competitors. Look at how they structure pricing packages. This helps you understand the market and shape your own business model.
Your value metric defines how you charge for your SaaS product.
Ask yourself this simple question: What do customers value in your own product?
It could be seats, data volume, actions taken, or usage.
Review your product data to learn how customers engage with your product. These signals help you find the right value metric.
It's important to choose a key metric that scales with product usage. Doing so allows you to charge higher prices as the right customers get more value.
A single pricing model is often not enough and may feel too rigid as your market share expands. Your SaaS product should serve different users, use cases, and buying patterns.
Combining SaaS pricing models gives you more flexibility. You can align pricing and packaging decisions to how people buy, use, and scale with your product.
Here are some pricing models you can adopt:
Subscription-based pricing - Set a fixed price for access to the product that customers pay monthly or annually.
Seat-based pricing - Charge based on the number of users or seats on an account.
Pay-as-you-go pricing - Bill customers based on their actual usage, such as API calls or compute minutes.
Credit-based pricing - Give users credits they can spend on your product.
Tiered pricing - Offer paid plans with different feature sets, limits, or service levels.
The right hybrid model combination depends on how your product delivers value and how customers interact with it. It should also align with your go-to-market strategy.
For example, self-serve teams may lean toward subscription and usage-based pricing, while sales-led motions may rely more on tiered packaging and credits.
Packaging defines how you group features into plans.
Organize features based on how much value they provide. Keep basic features in plans with lower prices. Place advanced capabilities in higher tiers to create clear differences.
You also need to consider how customers' needs change over time. Your packaging should guide businesses toward upgrade paths as they transition from an early-stage startup to a mid-market company.
Avoid sharp jumps and price increases between tiers. Make upgrades feel natural and easy.
You can also use packaging to introduce new features. Decide early where each capability should live. This helps you control access and avoid confusion later.
Keep plans simple. Too many options can slow down purchasing decisions and make it difficult for your growth team to manage pricing.
Many SaaS companies hardcode pricing rules into their product. This works early on, but it does not scale and introduces complexities later on.
Every pricing and packaging change will depend on engineering. Adding a new plan, updating limits, or conducting pricing experiments requires code changes, reviews, and deployments. This slows down the entire business.
You should move pricing logic into a separate monetization layer like Schematic.
Store plans, entitlements, limits, and access rules in a system that you can quickly update without touching application code. Your product should read and enforce these rules at runtime.
This approach gives different teams more control. Engineering stops writing and maintaining billing code. RevOps can launch new trials, offers, and plans without waiting on developers.
According to OpenView research, 94% of B2B SaaS leaders update pricing and packaging at least once per year.
You should continuously iterate on pricing and packaging to adapt to product, users, and market changes.
Analyze conversion rates, deal sizes, and which tiers customers pick. You can also track how users move across different plans. Look at upgrades, downgrades, and churn. Use this pricing data to understand what's working and what's not.
Experiment with different price points to test the customer's willingness to pay for additional features or services.
Measure the impact before making wider changes. Staggered pricing rollouts reduce risk and are easier to manage.
Constant iteration helps you capture more value over time. When you adjust pricing based on actual usage and behavior, you reduce underpricing and missed revenue opportunities. Small changes, such as higher limits, add-ons, or more features bundled in a plan, can increase revenue per account.
Better pricing decisions can also lead to improved cash flow. Billing becomes more consistent and predictable because pricing aligns with how and when value is delivered.
Even with the right setup, operating pricing and packaging brings real challenges. Below, we'll discuss the challenges SaaS companies often face and share tips on how to solve them.
The major problem with existing implementations of the product catalog is that many SaaS companies maintain it in multiple places.
For example, the sales team usually manages a product catalog in the CRM software. Finance often maintains a product catalog in the billing system, ERP, or both. Meanwhile, product and engineering teams control product catalogs directly in the application database.
Multiple product catalogs create a number of significant operational problems and pain points.
For one, it takes several months to coordinate even a small change in the system. And if a change in the market impacts your existing customers or alters your customer segments, you may find yourself unable to react in time.
Solution: Designate one representation to maintain all product definitions and reconcile product catalogs from other systems. It should also make the application code agnostic to the commercial product definition.
Many companies face challenges with fragmented company data scattered across various systems, such as CRMs, billing platforms, and support tools. This makes it difficult to create a clear, accurate, and complete customer profile.
That fragmentation leads to inconsistencies in customer information. It can complicate analysis and billing operations, impact entitlement delivery, and lower customer satisfaction.
Engineering leaders highlight the need for a system that aggregates customer state, inclusive of context that traditionally lives outside of the application. Meanwhile, business leaders struggle with assembling detailed profiles that combine account, usage, and billing information.
Solution: Implement company profiles to consolidate data into a single source of truth for business telemetry and for the application to reference. The profile serves as the foundation for entitlements, personalized user experiences, and streamlined account management across different teams.
Most SaaS companies struggle with accurately tracking usage across their products. This leads to missed revenue opportunities and potential billing disputes.
It's difficult to build a scalable and reliable metering system. Teams have to track usage in a distributed environment, manage large data volumes, and integrate with existing systems. Providing real-time alerts adds another layer of technical and operational complexity.
Solution: Implement a metering component to align pricing and packaging with the value customers derive from the application. Tracking usage accurately ensures transparent usage-based billing and helps inform product strategy.
Many SaaS businesses manage subscriptions through strict plan assignments in their application database. These usually require manual data entry in admin panels, which can lead to drift and errors.
There is also no clear history of changes, which makes support and debugging harder.
Application databases often lack references to pricing data. When subscriptions include usage-based components, teams need to export usage data and handle invoices manually.
Solution: Use the subscription component in your system to fulfill contracts immediately. Self-service subscriptions can be self-managed. Those sold via other channels (e.g., direct sales) can go through a more rigid approval process. GTM and RevOps can easily review current subscriptions.
Feature flag management often relies on ad hoc setups, where implementations vary across the application. This creates rigid systems that are hard to manage without engineering support.
In many cases, plans are hardcoded into the codebase and enforced using internal or third-party feature flags.
Entitlements are also disconnected from other systems. For example, if sales convert a new customer outside the product, engineering should manually grant access. This disjointed process is prone to errors, delays fulfillment, and complicates business growth.
Solution: Decouple pricing logic from application code. You should also use a centralized flag component to dictate feature access based on active subscriptions. Make sure it automatically reflects usage or context changes.
Most SaaS companies struggle to manage pricing and packaging as they grow. Pricing logic sits in application code and eventually spreads across different systems. Every change requires engineering time. Plans become hard to update, and launching new pricing takes longer than expected.
Schematic solves this by providing a system of record for your product catalog. It centralizes plans, entitlements, limits, trials, credits, add-ons, and exceptions. That makes it easier to orchestrate pricing and packaging in your SaaS product.
Schematic sits between your application and Stripe. Stripe continues to handle payments and invoices. Meanwhile, Schematic evaluates and enforces access in-product at runtime while keeping entitlements aligned with subscription and billing state in Stripe.
Engineering no longer needs to maintain the billing and entitlement code. Product teams can continuously iterate on packaging, limits, and enforcement.
Schematic handles pricing and packaging at every stage, from defining plans to enforcing access. You can focus on what makes your SaaS product great, not how you price, package, or bill.
SaaS pricing defines how you charge for your product. Packaging defines how you group features and limits into plans. Managing both effectively helps you achieve a balance between control and flexibility.
A flexible pricing and packaging strategy can help you maximize revenue as your SaaS product grows. You can test new pricing, adjust plans, and respond to market changes without delays. It also supports predictable revenue by aligning pricing with how customer accounts expand over time.
Common SaaS pricing models include subscription-based, seat-based, pay-as-you-go, credit-based, and tiered pricing. Many SaaS companies start with a subscription model, so users can quickly buy plans based on their budget and needs. But over time, businesses turn to a hybrid model so they're not forced to charge the same price, especially if customers have various usage patterns.
