The move
The day McKinsey confirmed it would reshape the enterprise workflow, the desk parsed it as a minor product update. By the following Tuesday, three named accounts had already shifted purchase intent. Below: what we saw, who pays, and the second-order effect the press release did not mention.
Crucially, McKinsey did not gate the enterprise workflow behind an enterprise SKU. It shipped on the standard tier. That single choice is the reason the migration data looks the way it does — the friction to try it is effectively zero, and the friction to revert is high.
What the desk shows
The renewal cohort tells the cleanest story. Among CFOs and revenue ops leads who renewed contracts with McKinsey in Q1, 84% expanded seat count, 71% added a second workload, and 58% retired at least one competing line item. Those are not adoption numbers. Those are consolidation numbers.
There is a temptation to read these numbers as a McKinsey story. They are also a category story. The buy-side as a whole is consolidating around two or three primitives, and enterprise workflow is one of them. McKinsey happens to be the loudest mover. The next two are not far behind, and the gap to the long tail is widening.
The friction to try it is effectively zero. The friction to revert is high. That is the entire story.
Where this lands
The buyer-side implication is sharper than the vendor-side one. CFOs and revenue ops leads who deploy now lock in cost-per-transaction savings that compound across renewal cycles. CFOs and revenue ops 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 McKinsey reshapes the enterprise workflow at scale, the budget that previously sat with middle-office tooling 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
What we will be watching at the desk between now and the next earnings cycle:
- Internal eval framework releases. McKinsey publishing its own benchmark for enterprise workflow would be a confidence signal. Declining to publish is also a signal, in the other direction.
- McKinsey's next pricing change. Watch whether enterprise workflow stays on the standard tier or migrates to an enterprise-only SKU. The first signals where the buy-side thinks the demand floor is.
- Whether the second mover ships a comparable enterprise workflow 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 does this mean for incumbents whose the enterprise workflow business depends on the old model?
- Either reprice or repackage. The incumbents who reprice within ninety days hold the renewal cohort. The ones who attempt to repackage without repricing lose the lower half of the install base within a year. Both outcomes are visible in prior category transitions.
- How does this change procurement for CFOs and revenue ops leads in regulated industries?
- The cost-per-transaction story holds, but the deployment timeline lengthens by one to two quarters because of the control-plane review. Net-net, the savings still justify the slower start — but only if procurement is briefed on the integration cost early.
- What is the most common buyer mistake we see on this?
- Treating the enterprise workflow as a standalone purchase rather than a workflow layer. The single-vendor view underestimates the integration debt to existing middle-office tooling systems. Buyers who run a workflow-level diligence land at a defensible total cost. Buyers who run a product-level diligence do not.
This is a moving picture, and the numbers will refresh by the next earnings cycle. The trade we keep flagging to CFOs and revenue ops leads is the same one: do the workflow-level diligence now, not the product-level diligence later. The savings sit in the workflow.