Understanding Salesforce's Agentic Work Unit (AWU)

Salesforce is reorienting its strategy around the "Agentic Enterprise," and the Agentic Work Unit (AWU) arrives with that shift. It moves AI measurement away from consumption and towards what the agent actually got done.

What an AWU counts

AI success has been quantified for years by tokens processed, API calls, or licensed seats. Those numbers matter for infrastructure planning, but they say nothing about whether the AI delivered a meaningful result. An AWU is a unit of completed work performed by an AI agent: a prompt executed, a reasoning chain completed, a Salesforce Flow successfully invoked.

An AWU marks the point where AI reasoning turns into AI action, which is much closer to how businesses already evaluate productivity and ROI. Efficiency is designed into it. The relationship between token usage and AWUs is elastic, so as implementations mature the goal is more completed work from fewer, cheaper tokens. In the agentic era, an agent's value comes from how effectively it completes its tasks, and consumption alone no longer measures that.

Partner metrics are moving to outcomes

Salesforce's partner program has historically run on certifications, project volume, and customer satisfaction scores (CSAT). That foundation is showing signs of evolution. As Agentforce becomes central to Salesforce's value proposition, success gets defined more by concrete customer outcomes, and the emphasis moves to whether agentic solutions are demonstrably generating value in production.

AWU is not a formalized partner tier metric yet, but the trajectory is clear enough. Customer value, delivery quality, and partner effectiveness are converging on outcome-based indicators, and partners will differentiate on their ability to turn Agentforce capabilities into sustained, measurable results. Counting delivered projects or certified consultants may matter less as that happens.

Implications for customers

You get what you measure. Once Salesforce and its partners prioritize agentic outcomes, nearly every project becomes an Agentforce project by extension. Expect fewer purely traditional CRM implementations and more work that builds agentic foundations, enables AI-driven processes, or delivers AI-enriched insights.

That puts more responsibility on both customers and partners to define success criteria upfront. Well-defined use cases, sound governance frameworks, and a realistic read on operational maturity are what keep AI development pragmatic and tied to a business need instead of becoming an end in itself.

Final thoughts

The AWU is an attempt to anchor AI adoption to something measurable and concrete. For organizations working through AI complexity, a shared unit of value gives Salesforce, partners, and internal teams a common language, which in theory reduces ambiguity and keeps AI capabilities pointed at clear objectives.

The risk I see is that a focus on agentic outcomes overshadows the what and the why of a project. The AWU measures agentic outcomes specifically, so it is worth asking whether this steers the ecosystem away from deterministic automation and configuration even when those approaches suit the use case better.