Feature-Based Pricing

Feature-based pricing is a packaging and pricing strategy in which a product is offered at multiple tiers — typically three: Basic, Professional, and Enterprise — where each tier is defined by the set of features available to the buyer at that price point. Buyers self-select their tier by choosing the capability level that matches their needs and budget, and vendors use the tier structure to segment the market, capture revenue from buyers with high willingness to pay, and create a natural upgrade path as customer needs grow.

The fundamental commercial logic of feature-based pricing is price discrimination through self-selection. A company with 500 employees and a dedicated revenue operations function values advanced analytics, API access, and custom integrations differently than a 10-person startup that needs only core functionality. By offering the same product at multiple capability levels, the vendor can serve both segments profitably: the startup pays a price calibrated to their limited feature needs and lower willingness to pay; the enterprise customer pays more for the advanced features they require. The vendor extracts more total revenue across the customer base than a single-price model would permit.

Feature-based pricing is distinct from several adjacent pricing models. It differs from usage-based pricing, where cost scales with consumption volume rather than feature access. It differs from seat-based pricing, where cost scales with the number of users rather than capability level (though feature-based and seat-based pricing are often combined). It differs from outcome-based pricing, where cost is tied to delivered business results rather than product access. Feature-based pricing is primarily a product packaging decision — which capabilities are available at which tier — rather than a billing model decision about how charges are calculated.

Signalon's own pricing reflects this model: Basic at $18/user/month, Professional at $24/user/month, and Enterprise at custom pricing. Each tier provides a different feature set calibrated to different buyer profiles, with the tier structure designed to make the upgrade path commercially natural when customer needs grow beyond the capabilities of their current tier.

---

Feature-based pricing shares terminology with adjacent concepts:

• Tiered pricing — the most common synonym; describes the same model from a packaging structure perspective rather than a feature logic perspective
• Good-better-best pricing — informal framing of the three-tier model that has become the standard structure for SaaS feature-based pricing
• Versioning — the academic economics term for the same practice; originating from Hal Varian's pricing research on information goods
• Product tiers — refers to the output of the feature-based pricing design process rather than the strategy itself
• Plan-based pricing — operational framing, particularly common in SaaS where tiers are marketed as "plans"
• Capability-based pricing — a slightly broader framing that includes service level and support availability as tier differentiators, not just feature access
• Feature gating — the technical implementation practice of restricting feature access based on the buyer's tier; feature gating is the product engineering complement to feature-based pricing strategy
• Freemium — a specific variant of feature-based pricing where the lowest tier is offered free, with paid tiers providing access to additional features

---

Feature-based pricing requires decisions at three distinct levels: how to define the tiers, which features to include in each tier, and how to design the upgrade path.

Defining the tiers

The three-tier model (Basic/Professional/Enterprise) has become the dominant structure in B2B SaaS because it maps efficiently to three distinct buyer archetypes: the cost-constrained buyer who needs core functionality without paying for features they won't use; the growth-stage buyer who needs expanded capability and is willing to pay for productivity-enhancing features; and the enterprise buyer who needs advanced control, customisation, and compliance capabilities that justify a premium price point. The price ratio between tiers is typically 1.3–1.6x between adjacent tiers, maintaining a price difference significant enough to create meaningful trade-off decisions without pricing the middle tier out of reach for the primary target segment.

Feature allocation logic

The decision about which features belong in which tier should be driven by value analysis, not by development cost or feature complexity. The relevant question is: which features are valued most by enterprise buyers relative to SMB buyers? Features that provide disproportionate value at scale — advanced analytics, custom integrations, API access, SSO, audit logging, multi-region deployment, dedicated support — belong in higher tiers not because they are technically complex but because they are disproportionately valued by buyers who can afford to pay more. Features that are table stakes for all buyers should be in all tiers; withholding them from the basic tier damages conversion and creates buyer resentment.

Common tier allocation principles:

• Basic tier: Core workflow features, standard reporting, standard integrations, email support
• Professional tier: Advanced analytics, additional integrations, higher usage limits, collaborative features, priority support
• Enterprise tier: Custom integrations/API, SSO/SAML, advanced security and compliance controls, dedicated customer success, SLA guarantees, custom contract terms

Designing the upgrade path

Feature-based pricing only generates expansion revenue if the upgrade path is commercially natural — if customers routinely reach the limits of their current tier and are motivated to upgrade rather than churn. This requires designing the tier boundaries at points where buyers actually get stuck: where a feature they genuinely need is unavailable at their current tier. Tier boundaries set too conservatively (basic tier includes almost everything) reduce upgrade incentives; set too aggressively (basic tier lacks even obvious table-stakes features) damage conversion and brand perception.

Communicating the pricing structure

Feature-based pricing requires clear, accessible communication of what each tier includes. The most effective pricing pages use a comparison table format that makes the feature differences between tiers immediately scannable rather than requiring buyers to read through detailed feature lists. The Signalon pricing page demonstrates this structure for the platform's own feature tiers.

The role of CPQ in feature-based pricing

For enterprise deals where custom pricing is negotiated, the published tier structure is the starting point for commercial conversations rather than the final price. Signalon's CPQ capabilities support configurable feature sets and pricing that depart from standard tier definitions when enterprise requirements call for custom packaging — maintaining commercial flexibility while preserving the clarity of the standard tier structure for the majority of buyers.

---

Pain points: SaaS companies designing feature-based pricing face the challenge of feature allocation — specifically, whether features are allocated to tiers based on value analysis (which features do high-willingness-to-pay buyers value most?) or based on arbitrary rules (new features go in Enterprise, mature features get moved down). Arbitrary feature allocation produces tier structures where the price differences are not matched by value differences, creating buyer resistance at the premium tiers and channel conflict between the sales team (who see enterprise features being withheld from customers who could benefit) and the product team (who use feature gating as a revenue mechanism regardless of value logic).

Use case: A SaaS company providing revenue analytics software reviews its tier structure after observing that upgrade rates from Professional to Enterprise have been declining for three consecutive quarters. Analysis reveals that several features in the Enterprise tier — specifically, custom dashboard creation, data export to CSV, and advanced filtering — are valued by Professional-tier buyers who have been requesting them in support tickets. A feature value analysis, conducted through a combination of support data, user surveys, and sales call insights, determines that these three features would increase willingness-to-pay for the Professional tier by approximately 22% while not meaningfully affecting Enterprise tier adoption. The features are moved from Enterprise to Professional in a tier restructuring. Professional tier subscription revenue increases by 18% in the following two quarters (a combination of reduced churn and accelerated upgrades from Basic), while Enterprise revenue is unaffected because Enterprise buyers' primary tier-selection drivers are SSO, API access, and SLA guarantees — all of which remain exclusively in the Enterprise tier.

Pain points: Financial services SaaS products — treasury management platforms, compliance tools, risk analytics — often have feature tiers that are shaped by regulatory requirements as much as by willingness to pay. Certain features (audit logging, role-based access controls, data residency controls) are regulatory requirements for financial services buyers that may not be valued (and therefore not paid for) by buyers in less-regulated segments. Including these features in all tiers imposes cost on segments that don't require them; restricting them to premium tiers creates compliance barriers for lower-tier buyers who may have regulatory requirements. Feature-based pricing in regulated sectors requires careful mapping of feature value to regulatory context.

Use case: A compliance software vendor serving both regulated (financial services, healthcare) and less-regulated (professional services, technology) B2B customers designs its tier structure to separate regulatory compliance features from general productivity features. The Basic tier includes core compliance workflow tools available to all segments. The Professional tier adds collaborative review features and advanced reporting valued by both regulated and unregulated buyers. The Enterprise tier includes audit logging, GDPR data processing features, FCA/CNMV regulatory reporting modules, and SOC 2 compliance documentation — features that are specifically required by regulated buyers and priced accordingly. The tier structure allows the vendor to serve unregulated buyers without charging them for regulatory features they do not need, while capturing full value from regulated buyers who require those features for legal compliance.

Pain points: Manufacturing software products — ERP modules, supply chain analytics, quality management systems — often have complex feature-based pricing structures that reflect the operational specificity of manufacturing contexts. A tier that includes "advanced inventory management" may mean something very different to a discrete manufacturer versus a process manufacturer versus a contract manufacturer — and the features that define "advanced" in each context may be entirely different. Feature-based pricing for manufacturing software requires either a high degree of horizontal feature generality (features that are genuinely valuable across manufacturing types) or vertical specialisation (separate tier structures for different manufacturing sub-segments).

Use case: A supply chain visibility platform serving both discrete and process manufacturing segments implements a horizontally structured feature-based pricing model with three tiers differentiated by data volume, integration depth, and analytics sophistication rather than by manufacturing-specific features. The Basic tier provides supplier visibility and delivery tracking for companies managing up to 100 supplier relationships. The Professional tier adds predictive analytics, exception management, and ERP integration for companies managing 100–1,000 supplier relationships. The Enterprise tier provides custom data models, API access for proprietary system integration, and dedicated analytics consultancy for companies managing more than 1,000 supplier relationships or requiring custom analytics. The horizontal structure allows the vendor to apply the same tier structure across manufacturing types while still differentiating meaningfully between small, medium, and large manufacturing operations.

Pain points: Software products serving professional services firms — project management, resource planning, document management, client portal — often have feature-based pricing structures complicated by the fact that the primary value driver for professional services buyers is time saving and client experience improvement, both of which are difficult to partition cleanly into tier-level features. Professional services buyers also tend to be small (many firms have fewer than 50 employees), making enterprise-tier pricing commercially unattractive even for firms that would benefit from enterprise-tier features.

Use case: A client portal software vendor serving law firms, accountancy practices, and architecture firms redesigns its feature-based pricing after discovering that 68% of revenue comes from firms with fewer than 50 employees, but the Enterprise tier features (custom branding, client mobile app, document signing integration, and API access) are disproportionately requested by this segment despite the cost barrier. The vendor creates a "Professional+" tier priced between Professional and Enterprise, containing the three most-requested enterprise features (custom branding, mobile app, and document signing) at a price point 30% above Professional rather than 100% above. The introduction of the intermediate tier reduces Enterprise tier revenue per seat but increases total tier revenue by 34% as firms that previously stopped at Professional because of the pricing gap between tiers now upgrade to Professional+ instead.

Pain points: MSPs and IT services companies that white-label or bundle third-party SaaS products within managed services packages face a feature-based pricing challenge: the feature tiers of the underlying product may not map cleanly onto the service tiers they offer their clients. An MSP that packages a cybersecurity SaaS product as part of a managed security service needs to decide whether to purchase the Enterprise tier for all clients (ensuring full feature access) or to match client tier to client needs (requiring per-client tier management). The per-client approach is more margin-efficient but operationally complex; the all-enterprise approach simplifies operations but reduces margin on smaller clients.

Use case: An MSP managing endpoint security services for clients ranging from 20 to 800 endpoints implements a hybrid approach: all clients get Professional tier access as the baseline (ensuring a consistent service standard), and clients with more than 200 endpoints or specific compliance requirements (healthcare, financial services) are upgraded to Enterprise tier. The MSP negotiates a volume pricing arrangement with the software vendor that makes Professional tier access commercially viable across all client sizes, while Enterprise tier pricing is reserved for the 25% of clients whose requirements justify it. The structured approach reduces the MSP's total software cost by 18% compared to providing Enterprise tier access to all clients, while maintaining service quality standards across the client base.

---

• Revenue maximisation through price discrimination. Feature-based pricing allows a vendor to capture different amounts from buyers with different willingness to pay without alienating lower-willingness-to-pay buyers. The Basic tier captures revenue from buyers who would not pay Professional prices; the Enterprise tier captures premium revenue from buyers who value advanced features. A single-price model loses one of these groups.
• Natural expansion revenue mechanism. Feature-based pricing creates a clear upgrade path: as customer needs grow, they encounter feature limitations at their current tier and have an incentive to upgrade. This organic expansion revenue — driven by product usage rather than sales outreach — is the most capital-efficient revenue growth path available.
• Market segmentation clarity. The tier structure provides a framework for segmenting the buyer market by need and willingness to pay. This segmentation informs not just pricing but also marketing messaging, sales targeting, and product development prioritisation — different tiers serve different buyer personas with different needs.
• Simplified buyer decision-making. A well-designed feature-based pricing structure reduces the complexity of the purchase decision. Instead of evaluating a full feature list and then negotiating price, buyers can identify which tier matches their needs and the price is clear. Reducing the decision complexity improves conversion and reduces the sales cycle length for standard deals.
• Competitive positioning signal. The features included in each tier communicate what the vendor considers table stakes (available at all tiers) and what it considers differentiated value (available at premium tiers only). This feature allocation signals the vendor's product philosophy and competitive positioning — which features the vendor is confident enough in to charge a premium for.
• Sales team support for commercial conversations. Feature-based pricing gives sales reps a structured framework for commercial conversations: "here is what you get at each tier, here is the price difference, here is the value difference." This clarity reduces the negotiation overhead that custom pricing requires and enables reps to run more deals in parallel.
• Reduced enterprise negotiation friction for standard deals. For buyers who fit clearly within a standard tier, the feature-based pricing structure eliminates the need for commercial negotiation entirely — the price is published, the features are documented, and the buyer can sign up without engaging a sales rep. This self-service efficiency reduces the cost of acquiring smaller enterprise customers significantly.
• Framework for product development prioritisation. The tier structure creates a mechanism for connecting product development decisions to commercial outcomes. Building a feature that will unlock Enterprise tier upgrades is a higher-priority investment than building a feature that will only benefit Basic tier users — and the tier structure makes this commercial logic explicit.

---

Feature usage data — which features are used by which customers, at what frequency, and with what correlation to retention and expansion — is the most valuable input for feature tier design. Features with high usage and high correlation to retention belong in all tiers; features with high usage concentrated among enterprise buyers are candidates for premium tier placement; features with low usage regardless of tier are candidates for removal or consolidation.

Upgrade and downgrade data reveals where tier boundaries are set correctly or incorrectly. High upgrade rates from Basic to Professional suggest the Basic tier is compelling but genuinely limited; low upgrade rates suggest the Professional tier is not offering sufficient additional value to justify the price difference. High downgrade rates from Professional to Basic suggest the Professional tier price is not justified by the feature value available at that tier.

Win/loss data by tier shows where the feature-based pricing structure is succeeding and where it is creating competitive disadvantage. Deals lost because Basic tier features are insufficient for the buyer's needs may indicate that table-stakes features have been incorrectly placed in higher tiers; deals won because Enterprise tier features differentiate strongly against competitors validate those feature placements.

Churn analysis by tier reveals whether the feature-based pricing structure is creating unsatisfied customers at any tier. High churn from the Basic tier may indicate that Basic tier features are insufficient to create long-term value; high churn from Enterprise may indicate that the Enterprise price is not matched by adequate feature value.

Willingness-to-pay research — through conjoint analysis, customer surveys, or sales call insights — provides direct measurement of which features buyers value and at what price premium. This data is the primary input for initial tier design and for ongoing tier restructuring decisions.

---

CPQ is the operational tool that translates feature-based pricing strategy into commercial execution.

• Tier-based product catalogues in the Signalon CPQ system enable sales reps to generate accurate quotes for any tier combination without manual price calculation
• Feature availability matrices that reflect the current tier structure ensure that quotes accurately represent what buyers are purchasing, preventing post-sale feature access disputes
• Enterprise tier custom pricing configuration supports the negotiated commercial terms that enterprise buyers require while maintaining the integrity of the standard tier structure for other segments
• Multi-year contract pricing for feature-based tiers requires CPQ support for annual price escalation and tier upgrade commitment discounts

Usage data is the primary evidence base for feature tier design and optimisation.

• Product usage analytics that track feature adoption by tier enable data-driven decisions about where tier boundaries should be set and which features are driving upgrade motivation
• Cohort analysis comparing feature usage patterns between tiers that have churned versus those that have expanded reveals which features are most correlated with long-term customer value
• Revenue attribution by feature tier shows which tier is contributing most to ARR growth, informing where product investment is most commercially valuable
• Signalon's analytics capabilities connect commercial data (tier revenue, upgrade rates) with usage data (feature adoption, engagement depth) for integrated feature pricing analysis

CRM maintains the commercial record of tier adoption and upgrade history.

• Account records should track the current tier, upgrade history, and feature usage summary to inform renewal and expansion conversations
• Opportunity tracking for tier upgrades should be a first-class workflow — distinguishing tier upgrade opportunities from new seat addition opportunities and from new logo opportunities
• Integration with the billing system ensures that tier changes are reflected accurately in invoicing without manual reconciliation
• Win/loss attribution that includes tier context — was the deal lost because the buyer's requirements exceeded the purchased tier? — enables systematic improvement of the tier structure

The product team's feature release and roadmap planning must be aligned with the commercial tier structure.

• Feature flag systems that implement feature gating based on tier should be connected to the billing system so that tier upgrades automatically unlock the relevant features without engineering intervention
• Roadmap visibility into planned feature releases enables pricing teams to plan tier restructuring in advance of new feature availability
• A/B testing infrastructure for tier restructuring — testing different feature allocations across user cohorts — provides controlled evidence for tier design decisions before broad rollout

Billing accuracy and flexibility are prerequisites for feature-based pricing to function commercially.

• The billing system must support multiple tier prices with automatic tier-change billing (prorated for mid-period upgrades), ensuring that customers who upgrade mid-subscription are billed correctly
• Downgrade protection rules — preventing downgrades that would reduce feature access below what has been provisioned and used — reduce churn that comes from price sensitivity without reducing product adoption
• Usage limit monitoring and enforcement (for tiers that include usage caps alongside feature limits) requires integration between the product usage tracking system and the billing system

---

• Allocate features by value, not by development timeline. The most common feature allocation error is placing new features in the Enterprise tier automatically because they are new, and moving them to lower tiers when they mature. This produces a tier structure that reflects product development history rather than buyer value, and creates feature tiers that do not cleanly differentiate by willingness to pay.
• Protect the Basic tier. Withholding table-stakes features from the Basic tier to drive upgrades creates buyer resentment and review site criticism. Features that buyers need to achieve any meaningful result should be in all tiers; the Basic tier should be genuinely useful, just genuinely limited relative to higher tiers.
• Design upgrade triggers intentionally. The features you place in Professional and Enterprise tiers should be the ones that naturally become relevant as customer needs grow. If Basic tier buyers never encounter the limitations that would motivate them to upgrade, the tier structure generates no expansion revenue. Design tier boundaries at the natural inflection points of customer need growth.
• Price the gap between tiers carefully. The price ratio between adjacent tiers (typically 1.3–1.6x) should reflect the value ratio between tiers. If the Professional tier includes features that buyers consistently describe as transformative, a higher price ratio is justified. If the additional features are marginal, a lower ratio is appropriate. Misaligned price-to-value ratios at tier boundaries produce high churn at the over-priced tier and low upgrade rates at the under-priced transition.
• Revisit tier structure annually. Feature-based pricing structures become misaligned with market reality over time as the competitive landscape evolves, customer needs shift, and the product feature set expands. Annual review of feature allocation, tier pricing, and upgrade/downgrade data keeps the tier structure commercially optimised.
• Communicate feature differences clearly. The commercial value of feature-based pricing depends on buyers understanding the differences between tiers. Pricing pages that obscure tier differences — through long feature lists, vague feature descriptions, or qualification markers like "advanced" without explanation — undermine conversion and upgrade motivation.

---