Results as a Service vs. Resolution as a Service

Results as a Service describes broad business impact. Resolution as a Service defines the billable unit around discrete business problems resolved by the platform.

Results as a Service is not the same as Resolution as a Service.

Results as a Service is a broad phrase that implies software should be paid for based on business results rather than access, usage, or seats. The problem is that “results” are often too vague to price, verify, attribute, or defend in a contract. Revenue growth, cost reduction, customer satisfaction, productivity improvement, and risk reduction may all be valuable business results, but they are usually influenced by many factors outside the software platform itself.

Resolution as a Service is narrower and more commercially durable. RaaS prices software around discrete business problems resolved by the platform. A resolution must be verifiable, attributable, finite, economically measurable, and contractually defensible.

The distinction matters. Results describe business impact. Resolutions define the billable unit.

A vendor may contribute to a result without controlling it. A RaaS vendor must prove that it resolved a specific unit of work.

For that reason, CPAG uses Resolution as a Service rather than Results as a Service. The category is not built around aspirational outcomes. It is built around completed work that can survive measurement, audit, pricing, and CFO scrutiny.


This distinction is central to the CPAG RaaS framework. Atomic Resolution defines the minimum unit of resolved work, while Resolution as a Service defines the commercial architecture for pricing that work.