What We’re Watching at Dreamforce 2026: Top Trends
Dreamforce 2026 preview: the agentic enterprise, Data 360, governance and adoption. What Spire is watching, and why it matters.
An AI agent pilot rarely stalls on technology. Discover five signs that yours has stalled, and what each one tells you to fix first
An AI agent pilot rarely stalls on the technology. More often it stalls on steps that got skipped along the way: scoping the role, giving the agent proper access, watching the first months closely, and deciding who runs it once it’s live.
The signs below are the ones we come across most. Each points to a specific phase you may have skipped, which also tells you where to pick things back up.
“It helps with customer questions” describes an intention, not a scope. If you can’t name the systems it touches, the outcome it owns and the cases it has to escalate, there isn’t a role to govern yet.
That’s why scoping matters. It may read like paperwork, but it’s what makes everything after it measurable.
Usually not because it doesn’t work. Instead, nobody wants to sign off on what happens when it gets something wrong. Give the agent a supervised, time-boxed probation period with a clear pass mark. Otherwise, that hesitation doesn’t resolve on its own. It settles in.
“Let me double-check that number.” If your own team doesn’t fully trust the data, an agent working from it won’t earn that trust either. In other words, grounding a digital worker in numbers nobody stands behind moves the problem rather than solving it.
Copying between systems, chasing statuses, answering the same question again. This one is worth reading as an opportunity rather than a failure, because it points to work that is well-defined, repetitive and high-volume. And that’s exactly the kind of role a digital worker handles well.
No owner, no KPI, no review cycle. It’s the most common gap we see, and the most straightforward to close. An agent in production needs someone accountable for its performance, whether that’s a team internally or a managed service.

Start with the earliest phase you skipped rather than the most visible one. A pilot that has never met a customer usually has a scoping problem underneath it, so tightening the role does more good than adding another round of testing.
From there, work forward through the lifecycle. Member of Spire Biztory sets out the full lifecycle – workshop, MVP hire, probation, managed staffing and expansion — in their approach to building a digital workforce. We covered the same ground, phase by phase, in our previous blog.
On September 17, Geoffrey Smolders walks through how Biztory hired its own digital worker for sales discovery, and what it took to get it doing real work. Registration for this free webinar is open here.
Get in touch with Spire – we help teams put AI to work in practical, everyday ways.
Dreamforce 2026 preview: the agentic enterprise, Data 360, governance and adoption. What Spire is watching, and why it matters.
AI agent pilots are easy to start. Getting an AI agent into production is a different kind of work, and it’s where most initiatives slow down.
Back from vacation with hundreds of unread Slack messages and a full inbox? Here’s how Slack AI (Slackbot) turned weeks of catch-up into a prioritized to-do list in minutes.