Salesforce’s “Agentic Work Unit” Is the Pricing Shift Marketers Must Prepare For

On February 25, 2026, Salesforce reported 2.4 billion “Agentic Work Units” (AWUs) delivered to date alongside $72B RPO and $15B operating cash flow—explicitly tying AI to measurable output, not seats or tokens (Salesforce FY26 Q4 earnings). The next day, Salesforce published an AWU framework, positioning it as the atomic unit of “real work” done by agents across clouds (Agentic Work Unit explainer). This isn’t branding. It’s a billing and governance shift your lifecycle stack will feel.

What changed

• Salesforce linked AI performance to a unit of completed work (AWU), not raw compute. Expect packaging and budgeting to orient around outcomes like “journey steps executed,” “profiles resolved,” or “content variants produced,” not token counts.
• The FY26 Q4 recap framed the quarter as closing “the last mile,” moving from model access to governed, production agents executing work across CRM and marketing apps (Q4 Highlights).
• The market is converging here. WPP and Adobe deepened an alliance to embed agentic AI across marketing ops—evidence that output-based agent models are becoming operating reality, not a pilot (marketech apac, Feb 26, 2026).

Why AWUs matter to your lifecycle program

1. Budgeting shifts from seats to work. If you model SFMC costs around users, studios, and send volumes, expect a parallel line item tied to agent work completed. Efficient orchestration is rewarded; noisy automations are taxed.

2. Governance must define “work.” AWUs force clarity on which events, steps, merges, enrichments, and actions count as useful completions. In SFMC Journey Builder, think evaluation nodes, Decision Splits, and API Event triggers. In Agentforce, think Flow steps and action handoffs. Ambiguity = runaway AWUs.

3. Architecture debt hits the P&L. Middleware misfires, duplicate profile stores, and ad hoc webhooks that restart journeys become cost multipliers under AWU-style pricing. Salesforce Ben flags the same risk pattern in “connected” portals and middleware debates: unmanaged complexity breaks data flows and inflates ops (Salesforce Ben on partner portals; Salesforce Ben on middleware).

What changes for SFMC, Braze, and Iterable

• SFMC: Journey Builder logic is both cost center and growth lever. Expect AWU-like accounting to surface in Agentforce-aligned SKUs first, then into Marketing Cloud. Over-personalization that evaluates five attributes when two drive 90% of lift will quietly tax your budget.
• Braze: Braze bills on MTUs and sends. If Salesforce normalizes “work” pricing, procurement will ask Braze to report “actions completed per outcome.” Map Canvas steps to revenue events to stay defensible, as investors scrutinize AI narratives (Rolling Out on Braze stock swings).
• Iterable: Similar story—Iterable markets adaptive programs. Finance will push efficiency metrics: variants per win, steps per conversion, recomputes per resolved profile. Third-party reviews already compare tool efficacy; expect “work per result” next (G2 comparative review).

The new KPI layer: work per outcome

Track these five ratios now. You’ll need them when procurement asks why your agent budget spiked in Q3.

1. Steps per incremental conversion: (evaluations + actions) / incremental conversions attributed to that flow.
2. Personalization ops per send: dynamic content resolutions, catalog lookups, and profile merges per delivered message.
3. Recompute rate: profile/audience recalculations per unique user per week; spikes signal bad triggers or overlapping segments.
4. Agent handoffs per ticket/order: autonomous actions needed to resolve a task; high counts = fragmented context.
5. Cost per governed decision: estimated AWU-equivalent per decision node that changes outcome; if 80% of nodes never divert traffic, delete them.

Where teams burn AWUs

• Dead-end branches that evaluate but don’t act
• Overlapping triggers (webhook + event + nightly batch) restarting the same journey
• Unbounded AI content variants when a 3-variant bandit would converge faster
• Profile stitching at send time instead of precomputed identities
• “Test message” glitches pushed to production—see the Xbox test SMS noise via Braze label leak (Bitdefender report)

What to do

• Rationalize triggers: one canonical event per journey; de-dupe webhooks and batches
• Cap evaluations: limit decision nodes to proven lift; remove decorative splits
• Move identity upfront: resolve profiles pre-journey; cache lookups; avoid send-time recompute
• Instrument work: log step-level “completed work” with journeyId, nodeId, entityId, outcome to compute work-per-outcome before the invoice
• Add a production gate: no agent or journey ships without rollback and an anomaly threshold on work rate

Quick diagnostic

• Do we know our top 10 journeys’ steps-per-conversion?
• Can we attribute 80% of personalization lift to ≤3 attributes?
• Are duplicate triggers disabled at the source?
• Do we have a cost proxy per decision node?
• Is QA catching test-message and sandbox label leaks before prod?

Key takeaway

AWUs turn AI from R&D into operating model. If your stack produces “activity” without outcomes, you’ll feel it in governance and budget. The fix isn’t more agents—it’s cleaner triggers, fewer decisive steps, and instrumentation that proves work maps to revenue.

If your SFMC, Braze, or Iterable programs are drifting toward noisy automations, that’s what we refactor. We’ve helped teams cut 30–50% of dead work steps while increasing conversion. If AWU-style scrutiny is coming, let’s pressure-test in a working session. For adjacent planning, see our take on agentic orchestration tradeoffs in From AI Features to an AI-Run Lifecycle.