Salesforce made Agentforce Help Agent generally available at $2 per successful autonomous resolution — no charge when the agent escalates to a human or the customer is dissatisfied, sold in 1,000-resolution pack minimums. The unit carries over from the per-conversation model, but the trigger condition changed: the vendor now gets paid only when the outcome lands. Salesforce brought vendor-reported proof — 4.3 million inquiries on its own support site, 70% resolved autonomously — and a pending definitive agreement to acquire Fin, the SMB customer-service agent used by 30,000+ companies. Two days earlier, Sierra launched Horizon, extending its agents from single conversations to long-horizon goals spanning weeks or months: loan origination, prior authorization, specialist-referral scheduling. Read together, the largest CRM incumbent and the best-funded CX startup converged on the same commercial architecture in the same week. Outcome pricing is no longer a pilot SKU to watch — it is the default track, and W27-W28's Zendesk, HubSpot, and Coupa moves now look like the early adopters rather than the outliers.
Capital delivered the same verdict one layer down. Databricks put Inkling — Thinking Machines' open model — on Unity AI Gateway day-0, and the next day announced a Coatue-led strategic round at a $188 billion valuation, explicitly earmarked for Unity AI Gateway, Genie, and Lakebase. The caveat matters: this is a signed term sheet expected to close later in the summer, not closed capital — but the earmark is the signal. The largest private-market valuation event of the year is a bet on the gateway, not the model. The CEO's own framing — 'tokenmaxxing to valuemaxxing' — says the quiet part: selling tokens is a commodity business; owning the control plane between enterprise data and every model is the platform business. Snowflake reached the same conclusion by another route, signing its largest-ever AWS commitment at $6 billion, tied explicitly to agentic AI adoption with Marketplace go-to-market and migration incentives attached.
The connective tissue between the two stories is the thesis this publication exists to track: if the application is priced per outcome and the model is a swappable component behind a gateway, the durable layers are the data platform below and the measured workflow above. This week showed the distribution channel forming between them. Clay took its prospecting data and functions GA inside six assistants — Claude, ChatGPT, Claude Code, Codex, M365 Copilot, and Glean — via MCP, with admin permissioning, function allowlists, and per-rep credit budgets, and no MCP surcharge. Glean answered with the inverse play, pulling seven sales tools into its index. Atlassian conceded the coding-agent layer entirely — Jira work items are now assignable directly to Claude Code, Cursor, or GitHub Copilot — and claimed the context and governance layer instead, shipping AI cost-vs-output measurement alongside. The pattern is consistent: vendors are deciding, in public, which layer they can actually defend.
The governance clock is the urgent part. Microsoft message center notice MC1422074 confirms that OpenAI-operated GPT-5.6 becomes an M365 Copilot subprocessor that auto-enables for eligible tenants on July 24 unless admins set the control to 'No users.' That changes the data-processing chain under the DPA, and silence is consent. This is the second suite auto-enable event in three weeks — the W28 pattern of defaults replacing sales cycles, now applied to the data-processing chain itself. The same window produced the counter-current: OpenAI's GPT-Red disclosure claims an internal adversarial model hardened GPT-5.6 Sol to resist 99.95% of direct prompt injections (vendor-reported), making injection-resistance a published competitive axis for the first time — while SAP moved the opposite direction from everyone else, restricting direct third-party autonomous API access to SAP data and positioning Joule as the single mandatory window. One secondary source carries that report, so treat it as provisional — but if it holds, SAP is testing whether a closed gateway can survive in a week when $188 billion just priced the open one.
What to do with this week: CIOs have one hard deadline — audit the MC1422074 setting and set tenant posture before July 24, then fold injection-resistance evidence and subprocessor-chain disclosure into every AI vendor questionnaire. Function heads negotiating outcome-priced SKUs should contract the outcome definition, measurement rights, and audit access before signing — Salesforce's own carve-outs (no charge on escalation or dissatisfaction) show the definitions are negotiable now and will not be later. SaaS investors should reprice per-seat vertical SaaS against a world where the two data clouds just raised the cost of competing for the control plane, and should read the Databricks term sheet as directional but not closed. Vertical-AI founders: Clay just demonstrated the MCP distribution playbook — ship your function into every assistant your buyer already pays for, with admin controls as the enterprise unlock — and Sierra's Horizon shows the next defensible wedge is the long-horizon workflow, not the conversation.