Research / Coverage area 02
Coverage area 02Automation & Workflow Orchestration
Coverage of the connective tissue: integration platforms, workflow orchestration, agent frameworks, and the RPA lineage that reinvented itself around models. This is the area where leverage is most often claimed and least often measured, so we track the failure side as carefully as the adoption side.
Which automated workflows survive contact with a process change — and which quietly rot into manual work nobody reports?
Sample Data
Three figures from this area's dataset, in the form they publish in.
Illustrative sample — these figures show the structure of the dataset and the form a published finding takes. They are not published findings. Sourced figures publish with the report, each carrying an openable source.
Automation sprawl is the dominant pattern at this size band, not automation absence. The buying decision in front of most companies is consolidation, not adoption — and the dormant-workflow rate is the number vendors never publish.
What We Track
- Platforms deployed per company and the overlap between them
- Workflows in production, and how many are still firing twelve months on
- Ops roles not backfilled after a workflow went live
- Consumption pricing exposure — what a volume spike actually costs
- Whether failure alerting exists at all
In scope
- iPaaS, workflow builders, and orchestration platforms
- Agent frameworks and tool-calling infrastructure in production
- Process automation replacing a named operations role
- Automation maintenance burden — the cost after go-live
Not covered
- Single-purpose vertical SaaS with an automation feature
- Internal scripts with no owner, no monitoring, and no runbook
Adoption Depth Rubric — 0 to 5
The Leverage Index scores automation and agent adoption depth at 25% of the composite, applied as a 0–5 rubric to each coverage area and then averaged. This is that rubric for this area. A capability scores above 2 only if it is in production, used at least weekly, and displacing or avoiding a named role — not piloted, not licensed-and-idle. See the full inputs and weighting →
Handoffs run by people, in inboxes and spreadsheets.
A few native app-to-app syncs. Nobody owns them.
One team builds real workflows on a platform. Not shared, not monitored.
Named owner, failure alerting, and a runbook. Breakage is visible within a day.
End-to-end processes cross department boundaries unattended. A coordination role was not backfilled.
New processes are designed automated-first. Retirement and maintenance are budgeted, not deferred.
C.A.S.E. in This Area
The same four-stage method runs in all six coverage areas. Here is what each stage actually does in this one.
Nightly sweeps of vendor pricing and packaging pages, template and connector directories, partner listings, release notes, and operations job postings. Pricing changes are diffed against the prior crawl.
Vendor "hours saved" claims are checked against headcount evidence in the same company. A saved-hours figure with no corresponding role change is recorded as an unverified claim and labeled that way in every report it appears in.
The Automation & Orchestration landscape, the consumption-pricing exposure model, and the automation-decay finding — the part of the market with no vendor incentive to publish it.
Vendor selection inquiry: shortlist review, consolidation sequencing, and pricing-model risk on a live buying decision.
Sample Insights
Findings in the form we publish them: each one carries a confidence level, and the ones the evidence does not yet support are labeled open rather than quietly dropped.
Consolidation onto one orchestration platform outperforms adding a second, at every size band we have data for. The second platform is almost always bought to route around an ownership problem.
Consumption pricing is the most under-modeled cost in the category. Buyers price the pilot volume and get surprised by the production volume.
Vendor-published "hours saved" figures are the least verifiable claim class in our corpus. We report them only alongside a headcount change or not at all.
Illustrative sample — these figures show the structure of the dataset and the form a published finding takes. They are not published findings. Sourced figures publish with the report, each carrying an openable source. Research integrity policy →
What Publishes Next
Want this area applied to your decision?
Book an inquiry with the analyst covering it, or commission research on a question this area does not answer yet.