Financial research concept

Cloud Software Current RPO (cRPO): Contracted Revenue Expected Within 12 Months

Cloud software current remaining performance obligation measures contracted future revenue expected to be recognized within the next 12 months.

By Lee BaileyPublished Sep 22, 2026
Research context

See what supports this page, how current it is, and where comparable or historical context is available.

Research date
Sep 22, 2026Use the dated article and cited sources for the definition, examples, and stated limitations.
Operating-model context
12 connected conceptsPart of the reviewed Cloud Software Operating Model; issuer definitions remain distinct where disclosed.
Company examples
2 reviewed companiesRelationships reflect supported examples, not a normalized cross-company KPI ranking.

Cloud software current remaining performance obligation, or cRPO, is the portion of contracted future revenue expected to be recognized within the next 12 months.

ServiceNow and Salesforce both distinguish current RPO from total remaining performance obligations.

Why cRPO matters

cRPO can provide a nearer-term view of contracted revenue than total RPO because it excludes amounts expected beyond the next 12 months.

It can help investors assess:

  • near-term revenue visibility;
  • renewal and new-business timing;
  • contract duration; and
  • changes in backlog mix.

Investor caution

cRPO is not the same as revenue guidance.

Contract timing, foreign exchange, acquisitions, professional services, and customer consumption patterns can affect how RPO converts into recognized revenue.

Sources:

cRPO is a timing subset of RPO, not a separate revenue stream.

Part of the Cloud Software Operating Model

Connect contract backlog and retention, subscription revenue economics, large-customer expansion, and consumption-based product economics to understand cloud software growth quality and revenue conversion.

How the model fits together
  • Contract visibility, renewal, and enterprise depth: Current RPO narrows contracted backlog to the next 12 months, RPO recognition rate shows the expected near-term conversion share, renewal rate measures retained contract value without assuming expansion, and large-customer count adds enterprise-depth context. These measures complement existing RPO and net-revenue-retention concepts without replacing them.
  • Subscription monetization and service mix: Subscription revenue and subscription revenue mix show how much recognized revenue comes from subscription access, subscription gross margin shows delivery economics for that stream, and professional-services revenue mix separates implementation and service activity from software monetization.
  • Consumption commitments and realized usage: Capacity contract term describes commitment duration, product revenue measures realized platform consumption, product gross margin shows the infrastructure economics of that consumed revenue, and consumption overage captures usage above committed capacity. Contracted capacity and recognized consumption therefore describe different stages of the same customer relationship.

See It in Company Research

These companies are examples of how the concept is reported or discussed in public filings. Definitions can differ by issuer; these links open company research rather than a normalized metric comparison.

Continue Research

Continue from the concept into the Grizzly Bulls research surface that best matches the next question. These links are research continuations, not recommendations or required steps.

Compare stocks

Compare cloud software stocks

Continue into stock comparison for recurring revenue, contract backlog, customer expansion, consumption economics, service mix, and gross-margin context.

Explore more topics in the Financial Research Encyclopedia.