Salesforce · one lens
Hamilton Helmer on Salesforce
Salesforce's per-seat pricing is under real pressure; whether the switching-cost Power under it is too is a different question.
Helmer’s Switching Costs power rests on a specific mechanism: a customer who has already paid the financial, procedural, and relational cost of adopting a platform faces a second, separate cost to leave it — and that second cost, not brand loyalty, is what lets an incumbent hold pricing power (7 Powers). Salesforce’s Sales and Service Cloud data model, workflow customizations, and integrations are exactly that kind of embedded cost. The agent-era attack, on the record, is aimed somewhere more specific: not at the platform’s stickiness, but at its unit of sale. An AI agent replaces a job, not a login, and Marc Benioff demonstrated the mechanism inside his own company, cutting Salesforce’s support headcount from about 9,000 to roughly 5,000 after deploying agents to do work employees used to do.
That’s a real threat to the seat as a pricing unit. It’s a weaker case against Switching Costs as Helmer defines the term, which concerns retention, not how the retained customer is billed. Salesforce’s own numbers through the disruption support that reading: revenue still up 13% year over year in the most recent quarter, and Agentforce’s own annual recurring revenue up 205% to $1.2 billion in the same report — growth inside the installed base, not against it. Salesforce’s response has been to widen the switching cost rather than defend the seat: Headless 360 opens the platform to outside agents via API, and the June 2026 acquisitions of Contentful and Fin add capability that makes leaving Salesforce’s stack a bigger project, not a smaller one.
The open question Helmer’s framework actually raises is the Barrier’s direction, not its existence: the same APIs that deepen third-party integration also make it structurally easier for an outside agent to touch Salesforce data without a Salesforce seat attached to it. A Switching Cost that holds the data and a Switching Cost that requires a login aren’t the same Power, and Headless 360 is a bet that Salesforce can keep the first while giving up the second.
The seven Powers, one by one
| Power | Status | Why |
|---|---|---|
| Scale Economies | absent | not argued in the record |
| Network Economies | absent | not argued in the record |
| Counter Positioning | absent | not argued in the record |
| Switching Costs | contested | data-model lock-in intact and being widened (Headless 360, Contentful, Fin acquisitions), but the same APIs may let outside agents touch Salesforce data without a Salesforce seat attached |
| Branding | absent | not argued in the record |
| Cornered Resource | absent | not argued in the record |
| Process Power | absent | not argued in the record |
An editorial application of Hamilton Helmer's published framework — not their actual view, affiliation, or advice.
Where this lens comes from
Hamilton Helmer's framework is set out at the lens page, drawn from 7 Powers. This page applies it to Salesforce and nothing else — the company's full record is in the dossier.