What Is the Resolution-to-Seat Ratio?
The Resolution-to-Seat Ratio (RSR) measures how much of a vendor's current ARR could theoretically be repriced as outcome-based resolutions rather than seat-based access fees.
The Resolution-to-Seat Ratio (RSR) is the diagnostic metric that measures how much of a vendor’s current ARR could theoretically be repriced as outcome-based resolutions rather than seat-based access fees. It is the single most important diagnostic number produced in Phase 1 of the Three-Phase RaaS Transition Roadmap and the primary input for determining how quickly a vendor can move toward Resolution as a Service (RaaS) pricing.
The Formula
RSR is calculated as:
Estimated annual resolution volume multiplied by average resolution value, divided by total ARR.
For most SaaS companies running this analysis for the first time, the RSR falls between 0.3 and 0.8, meaning 30 to 80% of the value currently delivered could theoretically be priced as resolutions. The gap between the current RSR and 1.0 represents the portion of the vendor’s value that is pure access pricing, the most vulnerable portion of the revenue base when AI-driven headcount contraction accelerates.
How to Read the RSR
The Vendor Transition Playbook defines four interpretation ranges with corresponding Phase 2 priorities.
RSR below 0.3. Resolution pricing covers less than 30% of current ARR. Significant product work is needed to define resolutions before a hybrid pilot is viable. The immediate action is to build the Atomic Resolution Catalogue before attempting any pilot instrumentation. Attempting Phase 2 at this RSR produces inconclusive data because the resolution types are not yet well enough defined to generate meaningful cost-to-serve measurement.
RSR between 0.3 and 0.6. A solid foundation. Between 30 and 60% of ARR can be reshaped as outcomes on a standard transition timeline. Begin the Phase 2 hybrid pilot with the highest-RSR customer segments first, where resolution definition is clearest and margin validation will be fastest.
RSR between 0.6 and 0.8. A strong position. The majority of delivered value is resolution-definable. Accelerate the pilot timeline. Fast-track the highest-margin resolution types to pricing. The vendor is closer to the transition than most Phase 1 teams expect when they begin the audit.
RSR above 0.8. An exceptional position. The platform delivers predominantly outcome-indexed value. Phase 2 measurement infrastructure can begin immediately. Prioritize instrumentation over further discovery. A vendor at this RSR has the raw material for RaaS pricing. The work is now proving the margins, not defining the resolutions.
The Calculation in Practice
The RSR calculation requires two estimates that most SaaS companies have not previously made at this level of specificity.
Estimated annual resolution volume. For each candidate resolution type in the Atomic Resolution Catalogue, estimate how many resolutions are delivered per year across the customer base. This requires the product and customer success teams to translate their usage metrics, tickets closed, workflows executed, documents processed, into resolution counts per the Atomic Resolution standard. The most common error here is counting activities rather than outcomes. Tickets closed is not the same as tickets autonomously resolved without human intervention within the defined SLA. Apply the Atomic Resolution three-criteria test to every count to avoid overstating the resolution volume.
Average resolution value. This is the customer’s willingness to pay per resolution, not the vendor’s cost to serve. The starting point is the implied value: if the customer is paying $X per seat per year and those seats coordinate $Y of business value, what is the per-unit value of each discrete outcome the platform delivers? Customer success interviews, customer ROI data, and competitive pricing signals all feed this estimate. The Vendor Transition Playbook recommends triangulating between three methods: bottom-up from seat count and workflow volume, top-down from customer business value, and market-based from early pilot pricing signals.
The RSR as a Strategic Filter
The RSR is not only a diagnostic number. It is a strategic filter that determines which of a vendor’s product lines, customer segments, and resolution types should be prioritized in the transition.
Not every part of a SaaS product is equally amenable to resolution pricing. Some features deliver discrete, verifiable outcomes that pass the Atomic Resolution test cleanly. Others deliver ambient value, network effects, brand credibility, or workflow coordination that is genuinely difficult to carve into billable resolution units. The RSR analysis forces product leadership to distinguish between these categories explicitly.
The output of a thorough RSR analysis is not a single number for the whole company. It is an RSR by product line, by customer segment, and by resolution type. The highest RSR segments are the transition-ready segments. The lowest RSR segments are either product strategy questions (the value is hard to define as an outcome because it is not outcome-oriented) or pricing strategy questions (the value is outcome-oriented but has not been measured at the resolution level yet).
The RSR and the Bypass Test
Every resolution type that contributes to the RSR numerator should pass the Resolution Architecture Audit Bypass Test before it is counted. The Bypass Test asks a single question for each workflow: can an AI agent achieve this outcome without touching your product?
A workflow that can be fully bypassed by a general-purpose agent does not contribute durable RSR. The customer can achieve the same outcome without the vendor’s platform, which means the resolution value is not defensibly attributable to the vendor’s system. Workflows that survive the Bypass Test, where the vendor’s platform provides unique data, logic, or institutional context that the agent requires to execute the resolution, are the foundation of a defensible RSR.
The gap between the raw RSR and the bypass-adjusted RSR is the product vulnerability gap. Resolution types that fail the Bypass Test are not RaaS candidates. They are product strategy questions about what to build or acquire to create defensible resolution value.
The Resolution-to-Seat Ratio is Step 4 of Phase 1 in the Three-Phase RaaS Transition Roadmap. The full calculation methodology and interpretation framework are in the Vendor Transition Playbook. The Atomic Resolution standard that governs which workflows count toward the RSR is defined at What Is Atomic Resolution?