Forrester published its first Wave evaluation of revenue orchestration platforms this quarter, scoring twelve vendors across 22 criteria and surfacing, in the analyst’s own words, real unresolved tension in the category. Read the trade coverage of that report instead, and none of that tension survives. Three separate accounts of the same 12-vendor study collapse into one company’s win, described in nearly the vendor’s own language, with no other evaluated platform named once.
One Wave, one winner, in every account
The Forrester Wave: Revenue Orchestration Platforms for B2B, Q3 2026 is a category-defining document. It is Forrester’s first formal evaluation of a market it argues has consolidated sales engagement, conversation intelligence, and revenue operations into a single platform layer, and it graded twelve providers on everything from forecasting accuracy to agent governance. That is a genuinely large piece of reporting to compress into a story.
SalesTech Star reported that Outreach earned a perfect score in 15 of the 22 criteria, leading with Revenue Orchestration and Revenue Context and Continuity, and quoted Forrester’s line that Outreach is “best suited to organizations seeking industry-leading buyer engagement, conversation intelligence, and increasingly agentic workflows to improve seller productivity, pipeline quality, and forecast outcomes at scale.” MarketScale framed it the same way a few days later, citing the identical 15-of-22 figure but pulling different criteria to the front: administration and configuration, pricing flexibility, and the governance line item the outlet called a “usable requirements list” for teams running agents in production.
Advertisement
Neither piece names Gong, Clari, Salesloft, or any of the other ten providers Forrester actually scored. Neither piece cites a customer, a competitor, or an analyst outside the report’s own language. Read back to back, they are the same story told with a different subset of the same scorecard, both sourced to the vendor whose result they cover.
Where the accounts actually diverge
The one real difference between the two is which criteria each writer chose to foreground, and that choice tracks suspiciously well with which numbers Outreach’s own Forrester Wave recap had already led with. SalesTech Star’s emphasis on revenue context and conversation intelligence mirrors the categories Outreach’s own post opens with. MarketScale’s emphasis on post-sale governance and pricing transparency mirrors language further down the same post. That is not disagreement in the sense the format usually means: two outlets reading the same event and drawing different conclusions about what it signifies. It is two outlets selecting different highlights from the same press kit and running with whichever one they picked first.
If the accounts genuinely agree on anything past the vendor’s own framing, it is what they leave out. Both are silent on the eleven other platforms Forrester evaluated, on any customer named outside the vendor’s own reference list, and on the tensions Forrester’s own analysis raised about the category as a whole.
What the analyst said that the coverage did not
Forrester’s own writeup of its Wave, published by lead analyst Anthony McPartlin, is a different document from either piece of trade coverage, and it argues something considerably less comfortable for any single “Leader.” McPartlin’s post describes a structural contradiction running through the entire category: buyers want revenue context, the record of every signal and interaction that explains why a deal is moving or stalled, to be portable and shared, while the platforms selling that context are trying to keep it inside their own walls. “If five different platforms each claim to provide a complete understanding of the customer, are organizations creating shared context or competing versions of it?” McPartlin, VP and Principal Analyst at Forrester, wrote in the firm’s own analysis of the Wave.
That question applies to every vendor Forrester scored, Leader status or not. It is also exactly the question neither SalesTech Star nor MarketScale asked about the platform they were covering. McPartlin’s post raises a second unresolved point that the trade coverage skips entirely: as buyers increasingly work through AI assistants, Copilots, and chat interfaces rather than a vendor’s own application screens, “which agent-management responsibilities belong inside the ROP, and which should be delegated to an enterprise agent platform” run by Salesforce, Microsoft, or Oracle is still an open question, not a solved one, for every provider in the study.
The interface question nobody in the coverage raised
McPartlin’s post makes a third observation that neither trade account picked up at all: reference customers in the Wave interviews mostly described using these platforms the conventional way, logging into a dashboard, working inside the vendor’s own screens, even though the vendors themselves are all racing to build headless access through Copilots, Slack, Teams, and standalone AI assistants. Forrester’s post puts it as buyers lagging providers on where the interface is actually heading. That gap matters more than a scorecard line item, because it means the criteria Forrester used to grade “user experience” and “adoption” this quarter were largely scored against an interface model the category itself expects to be secondary within a year or two. A platform that wins today’s Wave on dashboard usability is not automatically the platform that wins the next one, scored against how well its data serves an agent working through a chat interface instead of a screen.
None of that is a knock on Forrester’s methodology. Reference interviews and live demonstrations are exactly how a rigorous first-of-its-kind evaluation should be built, and a first Wave in a newly formalized category is always going to grade the market as it exists today rather than the market as vendors say it is going. The point is narrower: the trade coverage treated the score as a finished verdict, when the analyst who produced the score was explicit that the category, and the interface it will be judged on, is still moving.
What it means for the sales leader
None of this makes Outreach’s result invalid. A 15-of-22 top score against a 22-criteria rubric, evaluated with customer reference interviews and product demonstrations, is a real result and a defensible reason to shortlist the platform. What it does mean is that “Leader in the Forrester Wave” is doing more marketing work in trade coverage than the underlying report supports on its own, and a sales or RevOps leader reading only the press coverage would come away thinking the category question is settled when Forrester’s own analyst is on record saying it is not.
The practical test the coverage skips is portability: if your team ever needs to leave a revenue orchestration platform, or run a second one alongside it after an acquisition, does the context travel with you, or does it reset? That question determines more about total cost of ownership over a three-year contract than any single criterion score, and it is precisely the dimension the vendor-sourced coverage has no reason to raise. This site’s own reporting on platform unification claims found the same gap: vendors describe unification in marketing copy well before any customer can point to a forecast that updates itself from engagement data in a named, auditable account. A prior piece on Outreach’s IDC MarketScape placement made a related point about analyst validation filling a proof gap vendors will not fill themselves, but even that proof has a limit: an analyst’s Wave is a snapshot of a scored demo and a handful of reference calls, not a guarantee that context survives a platform switch.
The takeaway
Before treating any “Leader” placement as a purchase decision, run three questions past the vendor and past whichever runner-up platform made the shortlist, since none of the trade coverage of this report asked them on your behalf:
First, what happens to accumulated revenue context, deal history, conversation records, forecast trend lines, if the contract ends. Ask whether that data exports in a usable, structured form or only as a flat file dump nobody on the team has time to rebuild into anything useful. Second, how the platform’s roadmap for headless, agent-driven access compares with what it demonstrated to Forrester this quarter, since that demonstration graded today’s dashboard-first interface, not the chat-first one the vendors themselves say is coming. Third, ask for a reference customer who has actually run the platform through an external AI assistant in production, not a roadmap slide, and see how long the vendor takes to produce one.
The Wave itself raised the right questions about context ownership and interface migration. The coverage of it did not carry those questions forward to the buyers who most need to ask them, and that gap, not the scorecard itself, is what a revenue leader should close before any contract gets signed.
Source: Outreach
