The four jobs AI actually does at work: A first look inside Zapier's AI Workflow Index
Wednesday, July 29
1 PM ET
"Until now, what AI actually does inside companies has been a guess. We stopped guessing and read it straight from the workflows our top customers are running on Zapier."
— Andre Vanier, Head of Orchestration Strategy, Zapier
On LinkedIn, every company looks AI-native. Inside most of them it's quieter. A few real wins, a lot of stalled pilots, and no clear picture of what's actually working. Every leader is being asked the same question: how do we get AI actually working in practice?
Most answers come from surveys and self-reported maturity scores. Those are just guesses dressed up as data.
Zapier's AI Workflow Index takes a different route. It's a census of every durable AI workflow running in production across 375 of the mid-market and enterprise companies furthest along with AI. It's read straight from the usage patterns. For the first time, we're opening the box on what leading orgs are actually doing with AI.
And beneath thousands of individual use cases, the same shape shows up everywhere: AI plays four roles at work.
But knowing what AI does is only half the story. Most organizations still stall. Rebecca Hinds, who leads Glean's Work AI Institute, studies exactly that: why individual AI wins so rarely add up at the org level (what she calls "coordination neglect"), and the hidden tax of "botsitting" the AI to make it usable.
Join Andre Vanier (Zapier) and Rebecca Hinds (Glean's Work AI Institute), hosted by Ryan Anderson, for a live walkthrough of the data + a candid look at what it takes to make it stick.
You'll walk away with a clear framework for where AI belongs, what to build next, and how to get those wins to actually land across your teams.
This session is for executives and functional leaders shaping their organization's AI strategy, along with the teams building and operating AI workflows.
Save your seat. Recording shared with registrants.
This session digs into the data and actual workflows. We'll go deep on:
– The four AI roles, defined by where the output goes: Not by what a vendor calls it. A role is read from the workflow itself: writes to a person, a record, a ticket, or a decision.
– The adoption sequence: Communicator and Clerk first, then Analyst, then Coordinator. And what it means for your AI roadmap if you've only built the first two.
– Operating signatures: How often these workflows are triggered, how much they do each run, and why so much of the work happens outside business hours.
– Real workflows from real usage data: Customer spotlights across GTM, Operations, and IT showing each role in production.
– Your Monday takeaway: How to read your own company's progress against the benchmark, find the role you're missing, and decide what to build next.
Can't attend live? Register today and we'll send you the recording, and the full report.
Can’t attend live?
Register today, and we'll send you a recording after the webinar ends.
Register now