I enjoy extreme sports because they provide evidence of the human ability to do remarkable things when the alternative is extreme catastrophe. Psychologists call it goal-shielding: commitment to one goal can push competing alternatives into the background.

History has given us a more dramatic expression for the same idea: “Burn the boats.” Put less dramatically, removing plan B changes the incentives around making plan A work. That’s what I found when I looked very closely at Salesforce’s adoption of Agentforce as part of our customer zero case-study series.

Salesforce’s website is its lead generation engine. As visitors engage, it produces 200 signals that feed attribution models, show the pipeline in real time, and determine the next best experience to move a visitor toward becoming a customer. As part of the launch of Agentforce, Salesforce made agents touchpoints in the customer journey and therefore part of its revenue engine, aligning its incentives so there was no comfortable path back to business as usual. You can imagine the dread of proposing that for your own revenue engine.

Spoiler alert: It all worked out. But there were some scratches and bruises along the way — learnings, too. Here are three that technology leaders’ operating agents should understand:

  • Knowing what agents do isn’t the same as knowing whether they’re producing good outcomes. Salesforce discovered that it needed to expand observability beyond traditional analytics, ultimately using large language model-based evaluation techniques to assess agent responses and improve behavior with greater confidence.
  • Your peer leaders will need confidence that agents behave reliably across customers, contexts, and channels. Building that confidence requires greater discipline in how agent knowledge is organized, accessed, and governed.
  • Agents need knowledge that traditional publishing processes weren’t designed to provide. Salesforce found that it needed to create agent-specific knowledge assets, including content stored in its content management system (CMS) but never published to the public website. In the process, content management started becoming knowledge management.

That third shift also reveals another source of value for a headless CMS: providing part of the knowledge substrate for agents. That makes the Contentful acquisition particularly interesting.

Putting agents into production is one thing. Making them governable is another. If you’re working through that transition, let’s talk.

Schedule an inquiry or guidance session with me to discuss what Salesforce’s customer-zero experience means for your own agent strategy, operating model, and digital experience platform. In a world of abundant technology, I offer a refreshed perspective on how to drive the selection of your digital experience providers that aligns with your strategic commitment to take control of your AI voyage.

Forrester clients can read Customer Zero Case Study: How Salesforce Made Agents Governable At Scale.

Share