
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

The seat is no longer the unit of software value. AI is absorbing seat-based workflows. Consumption is fragmenting across UI, API, MCP, and custom integrations. Low-cost competitors are commoditizing baseline capability. The new products in your portfolio were never seat-shaped to begin with. Customers, investors, and your own product roadmap are pulling you off seats faster than your sales motion can absorb.
Per-seat pricing is not just a packaging choice anymore. It is a strategic constraint on how you can grow. The companies that have made this transition cleanly (Twilio, Snowflake, Datadog, New Relic, MongoDB) treated it as a deliberate strategy reset, not a billing project. The companies that fumbled it lost 10 to 20 percent of ARR during the transition window and spent 12 to 18 months in revenue limbo.
We help software companies design and execute the move from seats to consumption. We work on the pricing strategy first (segmentation, packaging, metric selection, price point setting, willingness-to-pay validation) and then on the operational stack that has to ship behind it (sales comp, CPQ, billing, metering, revenue recognition, migration). Our team has implemented these transitions at Twilio, Zoom, DocuSign, Squarespace, and across enterprise clients in the $200M to $5B ARR range.
The Consumption Transition Spectrum (CTS) is our proprietary framework for designing a seat-to-usage pricing strategy. It evaluates your business across three dimensions and prescribes the right pricing architecture, migration design, and operational sequencing.
1. Value-Headcount Decoupling The degree to which the value your customers receive has separated from the number of seats they pay for. Low decoupling (collaboration tools, traditional CRM) means seats still capture value and a hybrid platform-plus-light-consumption model fits. High decoupling (AI agents, data products, automation platforms) means consumption is the value, and pure usage-based pricing becomes viable.
2. Consumption Surface Distribution Where consumption actually happens. Concentrated surfaces (single UI, single product) allow surface-specific pricing. Distributed surfaces (UI plus API plus MCP plus custom integrations) require a unified consumption currency that travels with the customer regardless of access mode. Most modern B2B software falls toward distributed, which is why token-based currencies have become the dominant pricing primitive.
3. Cannibalization Exposure The share of current ARR at risk of dropping under a consumption model. Shelfware accounts (paying for seats they do not use) and light users on heavy bundles are the highest risk. High exposure mandates a platform fee anchor, renewal-only migration, and grandfathering policy. Low exposure permits pure consumption launches.
The CTS produces a defensible pricing architecture rather than a copy-of-a-competitor packaging exercise. It anchors the strategy in your specific value, surface, and customer-base economics.
Most seat-to-consumption transitions go wrong, and the failure pattern is predictable.
Per-seat pricing is under structural pressure. Klarna replaced 700 seat-based agents with AI workflows. Intercom shifted to outcome-based at $0.99 per resolution. Salesforce launched Agentforce on Flex Credits at $0.10 per action. ZoomInfo, Datadog, New Relic, Snowflake, MongoDB, Cognition, Twilio, and dozens of other public-company transitions have moved off pure-seat pricing in the past five years. The companies that have not started yet are running out of time.
Pricing strategy decisions made before operational readiness create 12 to 18 month launch stalls. New Relic announced its consumption transition in July 2020 and finished rollout in late 2021. Datadog and Snowflake ran similar timelines. The cause is not pricing. It is that pricing decisions get locked before CPQ, metering, billing, and comp can absorb them, and engineering then loses 6 to 12 months arguing about specifications.
Poorly executed transitions leak 2 to 5 percent of ARR annually. On a $1B ARR base, that is $20 to $50 million per year through metering, billing, and reconciliation gaps (Lago, MGI Research). Bill shock drives renewal churn (78 percent of IT leaders report unexpected charges in 2026, per Zylo). CPQ and billing implementations overrun initial estimates by 40 to 50 percent.
Cannibalization risk is highest where companies look least. Shelfware accounts and light users on heavy bundles are the customers most exposed in a consumption move. The willingness-to-pay research, segmentation work, and platform fee design have to happen before the rate card is set.
The companies that win the transition do four things: they anchor the pricing decision in a structured framework, they validate willingness-to-pay before locking rates, they protect ACV through renewal-only migration, and they sequence operational readiness against the launch plan rather than after it.
Six workstreams, executed in sequence and tailored to your CTS profile.
1. Strategic Customer Segment Review - ICP and current-base segmentation with consumption-readiness scoring - Cannibalization exposure analysis by segment and account - Migration cohort design (which segments move first, which require grandfathering) - Persona and value-driver identification for each segment under the new model - Outcome: Segment-by-segment readiness map with migration sequencing
2. Hybrid Package Architecture and Design - Platform-plus-consumption tier design (good-better-best plus consumption layer) - Unified token currency design (token-to-event mapping, fungibility rules, expiration policies) - Capability-to-segment mapping under the new packaging - Bundle structures for committed usage with rollover and overage rules - Outcome: Defensible packaging architecture with token currency specification
3. Price Metric Selection via the CTS - Metric evaluation against the three CTS dimensions (decoupling, surface distribution, cannibalization) - Comparison of token-based, transaction-based, outcome-based, and hybrid metrics - Multi-surface alignment so the metric works across UI, API, MCP, and partner channels - Margin and predictability stress-testing against your cost structure - Outcome: Pricing metric selection with rationale, validated against unit economics
4. Unit Economics and Migration Modeling - Cohort revenue protection model (what each customer pays under each scenario) - Cannibalization scenario analysis (best, expected, worst-case ARR impact) - Cost-to-serve modeling under consumption (variable infrastructure, support, success) - Margin floor analysis by segment to set commit and overage rate floors - Outcome: Revenue and margin model with sensitivity analysis across migration paths
5. Data-Driven Price Point Selection - Willingness-to-pay research (qualitative interviews, Van Westendorp, MaxDiff, conjoint where budget permits) - Competitive benchmarking against direct peers and adjacent consumption transitions - Platform fee and committed-token bundle pricing - Overage rate setting with model-specific or feature-specific differentiation - Outcome: Defensible rate card with research backing for sales and finance teams
6. Market Testing and Operationalization - Pilot cohort design (6 to 8 weeks of structured testing with selected accounts) - Sales compensation framework redesign with rep calculator and worked scenarios - CPQ rules, approval flows, and hybrid contract templates - Billing flows for commits, overages, top-ups, and true-ups - ASC 606 treatment for token bundles and breakage accounting - Sales enablement (deal scenarios, calculators, rep quick-reference, Deal Desk readiness) - Outcome: Launch-ready pricing with full operational stack
The pricing strategy is the front half of the engagement. The operational transformation is the back half, and we cover the full scope.
Moving from seats to consumption changes seven systems at once: sales compensation, finance and forecasting, CPQ, billing, metering, revenue recognition, and channel partner economics. We deliver across all of them.
Sales Compensation. Quota redesign blending bookings and consumption ramp. Commission split structures with true-up and clawback mechanics. Rep calculator with worked scenarios. Compensation period calibration (quarterly versus semi-annual versus annual under consumption).
Finance and Forecasting. Consumption-era forecast model with cohort NRR and usage-ramp inputs. Investor narrative for the transition. Internal financial guidance for the ramp window. Revenue protection modeling through migration.
CPQ. Quote structure design for hybrid contracts (platform fee plus commit plus overage with model-specific rates). Approval workflow specifications. Runtime enforcement integration (pushing contract limits into the product layer for entitlement enforcement). Vendor selection across Salesforce CPQ, m3ter, and homegrown extensions.
Billing. Metered billing flows with mid-period true-ups. Top-up and overage handling. Vendor selection across Metronome, Orb, Lago, Zuora, and Stripe. Integration with NetSuite, RevPro, or your revenue subledger.
Metering. Billing-grade event ingestion specification (idempotent, fault-tolerant, audit-ready). Token-to-event mapping. Multi-surface metering across UI, API, MCP, and partner channels.
Revenue Recognition. ASC 606 treatment for token bundles, committed-use contracts, and breakage. Period-of-consumption recognition with quarterly close considerations.
Channel Partners. Partner margin restructuring (front-loaded on commit plus back-loaded on realized usage). Existing agreement amendment paths.
Migration. Renewal-only migration design. Grandfathering policy. Cohort sequencing. Customer-facing communication and rep enablement. Revenue protection through the 12 to 18 month migration window.
Launch Execution. Master project plan with critical path. Weekly executive status with risk register. Vendor and SI alignment. Cutover runbook and go-live readiness checklist.
Pricing strategy firms can design the model. Systems integrators can build what you spec. Neither writes the spec, validates it with willingness-to-pay research, or coordinates the seven-system launch. That is the gap, and it is where the 12 to 18 month stalls happen.
Our team has led seat-to-consumption transitions at Twilio, Zoom, DocuSign, Squarespace, and across enterprise clients moving from $200M to $5B ARR. We are vendor-agnostic across CPQ, metering, billing, and ERP. We sit between your pricing decision and your go-live, owning the strategy work and coordinating the operational build with your SIs, vendors, and internal teams.
We are the only firm that delivers both the pricing strategy and the operational transformation under one engagement.

Seat-based pricing charges a fixed fee per logged-in user per period. Usage-based pricing charges based on actual consumption: API calls, tokens, transactions, data volume, or completed outcomes.
Seat-based pricing assumes one user equals one unit of value. It works for collaboration software (Slack, Notion, Salesforce CRM) where value scales with people. Usage-based pricing decouples revenue from headcount, which fits products where AI does the work, where consumption fragments across UI and API, or where heavy users generate dramatically more cost than light users. Most modern B2B software companies are moving to a hybrid model: a platform subscription that grants access plus a usage component for premium consumption (Datadog, Snowflake, MongoDB, Salesforce Agentforce).
Most B2B software companies should run a hybrid platform-plus-consumption model, not pure usage-based pricing.
Pure consumption creates four problems: revenue volatility for the vendor, budget unpredictability for the customer, no floor against shelfware accounts dropping to zero, and weak alignment with annual procurement cycles. Pure consumption works for developer-tools categories with high-velocity sign-up and low-friction billing (Stripe, early Twilio, Snowflake’s free tier) but not for most enterprise sales motions.
A hybrid model preserves a revenue floor through the platform fee, gives customers predictable budget anchors through committed bundles, supports annual contracts and procurement cycles, and isolates consumption variability to the overage layer. It is the dominant structure across post-transition incumbents (New Relic, Datadog, MongoDB, Confluent, Salesforce Agentforce, Intercom).
The CTS framework prescribes which structure fits your business based on value-headcount decoupling, consumption surface distribution, and cannibalization exposure.
The right metric is the one that aligns with where customer value is created, can be metered accurately, scales predictably with cost, and fits your sales motion.
Four common metric families: - Token-based: unified currency that travels across surfaces. Best for multi-surface products (UI plus API plus MCP) and AI-native products. Used by ZoomInfo, OpenAI, Anthropic, Salesforce Agentforce. - Transaction-based: counts discrete events (API calls, lookups, messages). Best when one transaction equals one unit of value. Used by Twilio, Stripe, SendGrid. - Outcome-based: charges per completed outcome (resolution, qualified lead, generated campaign). Best when the outcome is unambiguous and measurable. Used by Intercom Fin, Hippocratic AI, Sierra AI. - Hybrid: combines a platform fee with one of the above. Best for enterprise sales motions where customers need predictability.
The CTS framework selects the metric based on your value-headcount decoupling, consumption surface distribution, and customer-base economics. Most B2B companies land on hybrid platform-plus-token or hybrid platform-plus-transaction.
A unified token currency translates heterogeneous events (API calls, AI actions, data lookups, model inferences, UI interactions) into a single billable unit the customer understands and can budget against.
Five design decisions: - Token-to-event mapping. What costs one token, what costs ten, what costs a hundred. The mapping should reflect underlying cost and customer-perceived value, not just technical cost. - List token pricing. Dollar-per-token at list, with volume discounts for committed bundles. - Bundle structures. Pre-purchased token packs with rollover rules and expiration policies. - Cross-product fungibility. Whether tokens spent on Product A can also pay for Product B. Fungibility increases customer flexibility and complicates revenue recognition. - Customer education. A clear mental model of what one token does. ZoomInfo, OpenAI, Salesforce Agentforce have all iterated multiple times on token communication.
The token design must be aligned with metering, CPQ, and billing specifications. Designing the token model and the systems separately is the most common reason consumption launches confuse customers.
Segmentation for a seat-to-usage transition uses two axes the seat-pricing world ignores: consumption readiness and cannibalization exposure.
Consumption readiness. How prepared each segment is to absorb the new pricing model. Power users on heavy workflows are usually consumption-ready. Light users on broad-access bundles are not. Self-serve segments adopt faster than procurement-heavy enterprise.
Cannibalization exposure. What share of current ARR drops under each scenario. Shelfware accounts (paying for seats they do not use) and light users on heavy bundles are highest risk. Power users on light bundles are lowest risk and often expand under consumption.
The segmentation drives migration sequencing: highest-readiness, lowest-cannibalization-risk segments migrate first. Highest-cannibalization-risk segments either get grandfathered, restructured at renewal, or moved last with bespoke handling. The segmentation model is built before the rate card is set.
Three research methods cover the willingness-to-pay decision space for consumption pricing.
Qualitative interviews (15 to 25 calls). Best for hypothesis validation, surfacing customer mental models for token currencies, and understanding budget approval dynamics. Cheapest and fastest. Required for any consumption transition.
Van Westendorp Price Sensitivity Meter. Quick survey method that establishes a defensible price range for the platform fee and committed-bundle pricing. Useful for board-level defensibility of rate decisions.
Conjoint analysis or MaxDiff. Higher-budget research that quantifies trade-offs between platform fee, included tokens, overage rate, and feature access. Best for high-stakes rate-setting decisions where 10 to 20 percent rate variance translates to tens of millions of ARR.
For most seat-to-usage transitions, we recommend qualitative plus Van Westendorp at minimum, with conjoint reserved for clients where the rate decision warrants the budget.
The platform fee in a hybrid model serves three jobs: it preserves a revenue floor against shelfware accounts, it anchors annual contracts to a predictable budget number, and it captures the value of platform access independent of consumption.
Four inputs drive the platform fee: - Cost-to-serve floor. The platform fee must cover non-variable costs (CSM, support, infrastructure baseline) per account. - Cannibalization protection. It must be high enough that shelfware accounts do not drop dramatically under consumption. - Willingness-to-pay ceiling. It must be low enough that customers see the move as fair, not as a forced rate hike disguised as a model change. - Competitive context. Where peers have set their platform anchors.
The platform fee typically lands between 30 and 60 percent of legacy seat-based ACV for the same account, with the remainder coming through committed and overage consumption. The exact ratio depends on the CTS profile.
Cannibalization risk is highest with shelfware accounts (paying for seats they do not use) and light users on heavy bundles. When the seat construct is removed, those accounts often pay less under any rational consumption rate.
Four mitigations: - Platform fee anchor. A meaningful platform subscription floor prevents shelfware accounts from dropping to a token-only spend. - Renewal-only migration. Customers move at renewal rather than mid-contract, giving you a negotiation moment to bundle, upsell, or restructure. - Cohort sequencing. Migrate high-utilization growth accounts first; delay shelfware risk until last. - Hybrid model design. Seat licenses with usage entitlements rather than pure consumption preserve the revenue floor for low-readiness accounts.
The cannibalization model is built before the rate card is set. Most companies build the rate card first and discover the cannibalization problem in customer-by-customer modeling later, which forces a re-pricing cycle and pushes launch by a quarter.
Revenue forecasting under consumption pricing replaces ARR with cohort net revenue retention (NRR) plus consumption trajectory by cohort.
The forecast model has three components: - New logo committed value. What new customers commit at signing. - Cohort consumption ramp. How each cohort’s actual usage grows over the contract term. - Net retention. How cohorts expand or contract at renewal.
Seasonality matters in a way it does not for seat-based pricing. Investor narrative typically shifts to cohort retention curves and consumption-per-customer growth. Companies that have made the public-market transition well (Datadog, Snowflake, MongoDB) talk about consumption growth and cohort behavior on every earnings call. The forecast model is built as part of the engagement and handed to your finance team for ongoing operation.
Both. The most successful migrations combine renewal-only conversion with a structured grandfathering policy for strategic accounts.
Renewal-only migration. Customers retain their existing seat-based contract until renewal, then choose between extending the legacy model or moving to the new consumption model. Mid-contract forced migrations almost always destroy revenue and trust.
Grandfathering policy. A defined set of strategic accounts retains their existing pricing for an additional 12 to 24 months. Used to protect the largest accounts and accounts with active expansion conversations.
A typical migration timeline runs 12 to 18 months from launch as customers cycle through annual renewals. Companies that try to compress this window with mid-contract forced moves typically lose 15 to 20 percent of ARR. Companies that run a structured renewal-only program with grandfathering typically retain 95 percent or more.
Five strategy mistakes show up repeatedly.
Skipping willingness-to-pay research. Companies set rates based on internal cost-plus or competitive benchmarking and discover at launch that the rate card is misaligned with customer budget approval dynamics.
No segmentation before rate setting. A single rate card across all segments leaves money on the table for power users and prices out light users. The segmentation has to come first.
Ignoring cannibalization in modeling. Companies build the rate card and discover the cannibalization problem in customer-by-customer modeling later, forcing a re-pricing cycle and a quarter of slip.
Copying a competitor’s structure. Copying Datadog’s hybrid model when your value-headcount decoupling, surface distribution, and cannibalization exposure are different produces the wrong architecture.
Treating the metric as a surface choice. Picking tokens because OpenAI uses tokens, rather than evaluating the metric against your CTS profile. Token-based pricing is dominant for a reason, but it is not universally right.
The CTS framework prevents all five by anchoring the strategy in your specific business profile.
Pre-launch testing combines structured research and a live pilot cohort.
Phase 1: Hypothesis generation (week 1-2). Internal alignment with product, finance, and sales leadership. Two to three beta customer interviews to validate direction.
Phase 2a: Qualitative validation (week 2-4). 15 to 25 structured customer interviews testing the metric, packaging, and price points. Focused on mental model fit, budget approval, and cannibalization signal.
Phase 2b: Quantitative testing (week 3-6). Van Westendorp Price Sensitivity Meter for platform fee and bundle pricing. MaxDiff or conjoint for high-stakes rate decisions.
Phase 3: Pilot cohort (week 6-14). Six to eight weeks of live pricing with a selected cohort. Monitor consumption ramp, billing accuracy, customer perception, sales motion, and revenue per account.
Total pre-launch timeline: 8 to 14 weeks depending on research depth. The pilot data feeds the final rate card, comp framework, and migration sequencing.
Operational readiness covers seven systems that change at once: sales compensation, finance and forecasting, CPQ, billing, metering, revenue recognition, and channel partner economics. We deliver across all of them as part of the same engagement.
The operational track runs in parallel with the strategy track. Pricing strategy decisions feed system specifications. System specifications feed vendor selection (Metronome, Orb, Lago, Stigg, m3ter, Salesforce CPQ, Zuora, Stripe, NetSuite). Vendor selection feeds the SI build plan. The build plan feeds the launch sequence.
The reason this matters: when pricing strategy and operational readiness run separately, there is a 12 to 18 month gap between strategy lock and production launch. New Relic, Datadog, and Snowflake all hit this stall. We compress the operational stack to 6 to 9 months by owning the specification layer ourselves rather than handing it to engineering.
For deeper operational scope, our Monetization Engineering practice handles the systems engineering layer end-to-end, including CPQ PRDs, billing flow specifications, ASC 606 treatment, and vendor coordination with SIs.
Three reasons.
Strategy depth. Seat-to-usage transitions require pricing strategy work that goes beyond a packaging review: cohort cannibalization modeling, willingness-to-pay research on multi-component pricing, token currency design, hybrid platform fee setting. Generalist consulting firms do not have repeatable methodology for this work. Internal pricing teams typically have not done it before.
Operational complexity. Seven systems change at once. The specifications for CPQ, billing, metering, and ASC 606 treatment are not in your engineering team’s domain. The 12 to 18 month launch stall happens here, not in pricing strategy.
Migration risk. The 12 to 18 month customer migration window is where 10 to 20 percent of ARR can be lost to churn or grandfathering concessions. Designing the migration cohort sequence, grandfathering policy, and revenue protection model requires experience seeing the failure patterns.
Monetizely combines pricing strategy depth (Twilio, Zoom, DocuSign, Squarespace, LinkedIn experience) with operational delivery (CPQ PRDs, vendor coordination, ASC 606 specifications, sales enablement). We are the only firm that delivers both under a single engagement.
A typical engagement runs 12 to 20 weeks for the strategy and operational specification phases, with optional execution support running 6 to 12 months through migration.
Phase 1: Diagnostic and Segmentation (weeks 1-4). Current-state pricing diagnostic. Segment-by-segment consumption readiness and cannibalization analysis. CTS profile development.
Phase 2: Architecture and Metric Selection (weeks 3-8). Hybrid package architecture. Token currency design (if applicable). Pricing metric selection via the CTS framework. Unit economics and cohort revenue modeling.
Phase 3: Research and Rate Setting (weeks 6-12). Willingness-to-pay research (qualitative plus Van Westendorp at minimum). Competitive benchmarking. Platform fee, commit, and overage rate setting.
Phase 4: Pilot and Operational Specification (weeks 10-18). Pilot cohort design and execution. Sales compensation framework. CPQ rules and approval flows. Billing and metering specifications. ASC 606 treatment. Migration cohort design.
Phase 5: Launch Execution (weeks 16+). Vendor coordination, SI alignment, sales enablement, cutover runbook, go-live. Optional ongoing support through the 12 to 18 month customer migration window.
Engagements scale from $80K (strategy-only) to $400K+ (full operational transformation) depending on scope, segment count, and migration complexity.
Join companies like Zoom, DocuSign, and Twilio using our systematic pricing approach to increase revenue by 12-40% year-over-year.