Opening hook
Replaces the first line of the post. Pick one, or write your own.
Artwork
Clifton Flack
Chief Commercial Officer, SLA Pharma
Last week the world's biggest CRM shipped itself as a plugin inside somebody else's chat window. On 26 August, Salesforce and Anthropic announced Claudeforce. It runs in two directions at once. Claude goes
into Salesforce — the reasoning model behind the Atlas engine, powering Agentforce Vibes and Coworker by default. And Salesforce goes into Claude: a plugin with 37 prebuilt sales skills — meeting prep, deal health, pipeline review — with pilot customers now and an open beta expected this month. The second direction is the one worth sitting with. The company that taught a generation of sellers to live inside its tabs has accepted that some of them will now work somewhere else, and would rather be present there than be missed. Read that against your own product. For years, distribution meant getting someone into your interface and keeping them there. Sessions, seats, stickiness. If the assistant becomes where work starts, your interface stops being the destination and becomes one of the places the work lands. Which raises an uncomfortable question for anyone selling software or a service: if a customer rarely opens your screen, what are they actually paying for? The answer has to be the layer underneath — the data, the permissions, the governed action, the record someone can be held to. That is the bet: the screen loses its monopoly, and the substrate keeps the value. If a company that owns the screen is willing to stop owning the screen, it's worth asking what you'd have left if you lost yours. If your customers only ever reached your product through an assistant they already trust, what would still make them pay for it? #Claudeforce #GTM #B2BSoftware

1,690 / 3,000 · folds at ~210
Workflow
“Post to LinkedIn” goes out publicly, straight away. The draft button is the safe rehearsal.
Recorded as posted on .