The Forrester Wave™: Revenue Orchestration Platforms, Q3 2026, just published.
In it Forrester evaluated 12 providers, conducted customer reference interviews, reviewed detailed product demonstrations, and analyzed how providers are evolving their platforms in response to rapid advances in AI.

While providers differed significantly in strategy and execution, here we highlight three key findings that consistently emerged across evaluations and customer conversations. Some reinforce existing market directions, while others expose tensions that buyers should pay close attention to as they plan future revenue technology investments.

What surprised most was not the rapid adoption of AI. More interesting was where the market appears to be concentrating value. Across providers and customer conversations, the discussion repeatedly returned to three interconnected themes:

  • Trusted revenue context
  • The emergence of headless AI
  • Governance and management of the agentic lifecycle in ROP

 

  1. Revenue context has emerged as a contested strategic asset

Across revenue orchestration platforms, the narrative is remarkably consistent: the future belongs to platforms that can establish and maintain trusted revenue context. Increasingly, providers argue that their ability to unify signals, activities, interactions, and outcomes into a persistent understanding of customers and opportunities will determine the effectiveness of AI and, ultimately, the future of revenue execution. The argument is compelling. AI systems cannot make intelligent decisions without context, and fragmented context remains one of the greatest barriers to automation, orchestration, and autonomous execution.

However, as providers race to build richer contextual foundations (context graphs, MCP etc.), a paradox emerged in the discussions with both providers and customers. Buyers are increasingly treating revenue context as a strategic asset that must be shared across systems, users, workflows, and AI agents. Yet many providers are simultaneously attempting to place that shared context inside their own platforms.

This raises an uncomfortable question: if context becomes truly strategic, should it belong to any individual platform? Today, most providers assume the answer remains yes, despite their embrace of context sharing standards like MCP. But the industry’s pursuit of unified context may risk creating a new generation of context silos. If five different platforms each claim to provide a complete understanding of the customer, are organizations creating shared context or competing versions of it?

 

  1. Headless AI poses new challenges for ROP

Traditionally, if a seller wanted to update an opportunity, review pipeline risk, inspect an account, or generate a forecast, they would open the application that owned that workflow. In a headless model, the seller might interact through an AI assistant, Copilot, Teams, Slack, voice interface, or agent platform instead. The application still exists, but it increasingly operates behind the scenes while agents orchestrate the experience.

The promise again is compelling: less navigation, fewer context switches, and more focus on outcomes rather than software. The debate, however, is not whether headless interaction is growing. The debate is where value, differentiation, and control migrate once the interface becomes fluid.

Across demonstrations, providers increasingly showed work being initiated through copilots, conversational interfaces, embedded experiences, collaboration tools, and agent interactions rather than traditional application workflows. Providers are clearly anticipating a world in which users interact less with applications and more with intelligent intermediaries. Yet very few reference customers explicitly described a headless strategy, suggesting buyers are generally further behind here.

  1. Agent lifecycle management is becoming key

The ability to create agents is now table stakes in this category. Discussions across both providers and customers in the Wave increasingly centered on governance, oversight, interoperability, control, and auditability. Customers want to know how agents operate alongside existing workflows, systems, users, and other agents. The Wave raised another interesting question for both parties: which agent-management responsibilities belong inside the ROP, and which should be delegated to an enterprise agent platform?

It would appear challenging for some providers to attempt to replicate the full agent-development and AgentOps stacks of Salesforce, Microsoft, or Oracle etc. Reproducing that breadth would require investment in capabilities such as enterprise identity, security, model management, registries, compliance, observability, testing infrastructure, and cross-domain agent governance. Much of this lies outside the ROP’s core competency and duplicates controls that customers may already obtain from other platforms.

However, ROPs need enough native capability to make their revenue agents safe, explainable, and operationally manageable, but their durable differentiation should come from revenue-specific context, orchestration, controls, and outcome measurement. A horizontal agent platform may provide the underlying control mechanisms, but Forrester’s view is that ROPs are better positioned to understand the business meaning and consequences of an agent’s behavior. At least for now.

To support this Wave, we’ve also published a buyer’s guide for the category. This report helps buyers of this technology identify the capabilities, readiness factors, and vendor traits that matter most.

 

 

Share