I run 200+ production agents. I'll take one job your team already runs, put a governed agent on it inside Slack, and name a person to own the outcome.
CDLTO, Asymbl
Salesforce MVP Hall of Fame
200+ production agents
Founded Dazeworks, through its acquisition
Dreamforce 2026
Spoke twice at Moscone, September 16 and 17.
Read the recap →
Three lines
The pilot answered the question in the room.
It never took a job the team already runs.
After the agent acts, nobody can name the owner.
Four steps
- Pick the job One workflow the team already runs, written down well enough to hand to someone new.
- Map the context The Slack threads, records, and permissions the agent is allowed to see.
- Put the agent on it The company talks to that agent in Slack, on that job.
- Go live A named person owns the outcome, including the exception.
Three ways to start
First Agent in Production
One job your team already runs, a governed agent inside Slack, and a named person on the outcome.
Agent Governance
Registry, permissions, memory, and a named owner after the agent acts.
Keynotes and workshops
Talks and workshops on governed agents. The archive is the record. Booking a talk starts at contact.
Before you book
Will security sign off?
Least privilege, a named identity, and traces are part of the build.
Do we need new software?
Usually no. The work uses the Salesforce, Slack, and MuleSoft already in place.
What if the agent gets it wrong?
A named owner reviews the exception.
Speaking and writing
Talks and workshops stay on the events archive. The operating notes are The Dark Factory.
Book the conversation
About · Services · Portfolio · Success Stories · Writing · News · Events · Contact · Tools I use · Media kit · Privacy Policy