Salesforce Headless 360 logs 4.5M calls as Anthropic usage surges fivefold through Claude

Salesforce waves bye-bye to UI in 'headless' embrace

Anthropic's use of Sales Cloud increased five-fold as its workers access Salesforce through Claude and Slack Salesforce's decapitated response to the SaaS-pocalypse has quickly won adoption, as Headless 360 - which allows customers to access all of their Salesforce data from Cursor, WhatsApp, ChatGPT, Claude, or a terminal - has processed 4.5 million MCP calls, and a nearly a trillion API calls, since launching at Trailhead DX in April, CEO Mark Benioff said on Wednesday. "It's going to lead implementations, drive consumption, more actions, more workflow, more data, more intelligence, all compounding across Salesforce. We're meeting our customers where they are," Benioff said during the company's first quarter 2027 earnings call. "With Headless 360, Indeed is building and deploying Agentforce agents right from Cursor." Salesforce chief revenue officer Miguel Milano said the real breakthrough wasn't for builders but for knowledge workers, because they can now access Salesforce through Slack, Claude Cowork, or other tools in their daily flow without context-switching into a separate app. "We're going to bring our number one agentic CRM to every surface, meeting customers where they are, and we're going to work together with our customers and with our partners to find the right ways to, in a fair way, to monetize those new interactions and those new uses are accessing our platform," he said during the call. Headless 360 attempts to expand Salesforce's addressable market into areas it's never previously entered. Milano said it is a fourth monetization vector beyond seat upgrades, new user pockets, and flex credits -- though he said they're still working with customers and partners to figure out the right pricing for the new headless interactions. Milano gave two customer stories. Adecco, a staffing company, had been building recruiter agents with outside AI labs that needed to pull data from Salesforce. He said when Headless 360 launched, they called and asked if those external agents could now access the platform natively. "Are you saying that now these agents that we are building outside Agentforce can also leverage Salesforce?" Milano said. "And we said, 'Exactly.' " Milano's second example was Anthropic, which he described as one of Salesforce's biggest users of CRM, Sales Cloud, and Slack. He said Anthropic's Sales Cloud usage with Salesforce grew fivefold in Q1 because employees started accessing it through Claude Cowork and Slack rather than logging in directly. "Sales Cloud has become more prominent and more strategic for them than ever, because of headless," Milano said. Analysts questioned whether making Salesforce data available from multiple platforms outside of Salesforce's native app may abstract the value of the product. Salesforce chief marketing officer Patrick Stokes said on the contrary, customers still need and rely on the data that is inside the platform, even if they don't need the UI. "What's so exciting about headless is two things: one, it's having a real impact on making it easier to implement with Salesforce, so building out with Salesforce has now become easier than ever because we've seen these coding agents Claude and Codex from from Open AI, as you use these things, what you realize is you need to be able to connect the underlying APIs which you do through this layer that's MCP, and if you can connect those into the coding agents, it makes it faster than ever to implement and deploy Salesforce," he said. Stokes said customers aren't using coding agents to replicate Salesforce capabilities themselves. Instead, they want to consume Salesforce in more ways and get more value from it -- plugging MCP servers into ChatGPT, Claude, or Slack rather than logging into discrete applications. Salesforce president and chief engineering and customer success officer Srini Tallapragada said this is part of a trend the company is seeing where customers still rely on the architecture, the data, the compliance, and the security they find in Salesforce, but they want to access the data from where they are working. To prove this point, he said in addition to the millions of calls to Salesforce headless MCP server since it launched, Slack's headless MCP server has seen between 30 to 50 million tool calls from customers, which also represents a new avenue for Salesforce to monetize. "We want to capture value wherever the work is happening, and that's the conversation we are having with our customers, and as we talk to our customers, ISV partners, and all," he said. "We'll figure out the right value. So, I think it's a new monetization area for us." Compared to the previous earnings call, where Benioff cited 200 new deals and name checked three ServiceNow take outs, Salesforce's chief SaaSquatch was relatively muted about its nascent ITSM rivalry with ServiceNow. He noted that anti-virus firm McAfee left ServiceNow for Salesforce Agentforce ITSM during the quarter. "They are using it for everything, ticket deflection, hardware provisioning, incident management. Really cool," he said. Salesforce reported first-quarter fiscal 2027 revenue of $11.13 billion, up 13% year-over-year. Net income rose to $2.10 billion, or $2.42 per diluted share, up from $1.54 billion, or $1.59 per share, in the year-ago quarter. For the next quarter, Salesforce guided to revenue of $11.27 billion to $11.35 billion, implying 10% to 11% year-over-year growth. The company also raised its full-year fiscal 2027 revenue guidance to a range of $45.9 billion to $46.2 billion, representing roughly 11% growth. The stock dipped very slightly in after-hours trading on the results. ®

It's what the market's asking for, so why have there been so many questions since the launch? Salesforce CDO Joe Inzerillo weighs in on the Headless 360 story

The response has just been unprecedented. People are super-excited about it. But there's been a lot of questions about what it is. Last week it emerged during the Salesforce post-earnings analyst call that the launch of its flagship Headless 360 offering at the TDX developer conference in April hadn't perhaps been as seamless as it might have looked. Customers, according to CEO Marc Benioff, haven't really understood the real message, which left CMO Patrick Stokes to do some on-the-fly course correction. Such is the importance of getting the story straight that Chief Digital Officer Joe Inzerillo has followed this up with that admission above and his own explanation of what customers need to understand about this big push, pitching: The thing about the whole concept of Headless 360 is really leveraging the stuff that we already have...But Headless 360 is really meant to be that glue that gives the customers and actually ourselves internally huge flexibility in how we want to represent all of that goodness that sits in the stack below it. Liberation It's all about "liberating" users through agentics, he went on, echoing a theme first raised by Salesforce co-founder Parker Harris back at the start of April when he stated: We are basically saying, 'Why should I ever log into Salesforce?'. Inzerillo expanded on that thus : Previously, at Salesforce, we and our Salesforce admins were really talking to the computer to provide instructions in advance to create an interface for humans to use. We're now in a world with agentics where we could actually have the agents create the UI on the fly. Headless 360 is the way that the agents know how to use the Salesforce platform and leverage 27 years' worth of goodness and history that's baked into it. He went on: Generally, in the Salesforce ecosystem, you have a user who is asking for something directly, and so they may be talking, let's say, to Claude. The agent knows how to then go and hit MCP (Model Context Protocol) endpoints inside the Salesforce ecosystem to ask questions, and it knows what questions to ask because these aren't just APIs, they are MCPs so they describe semantically what they're capable of doing. That allows humans and agents working together to drive more value. Obviously, this works all over the place - it works in Slackbot under the hood, it works in Codex, it works in Claude, it works on all the major AI platforms. It really is where you want to work, with the tool you want to use, but still leverage the capabilities of the Salesforce platform. As all roads lead to Slack, it will come as no surprise when Inzerillo confirms: Headless 360 brings the humans and the agents together in Slack. And so we use this internally when we're building Salesforce experiences in Slack, they come pre-integrated. So if you think about, for example, our Slack CRM is really Salesforce power sitting behind the scenes, the trust layer, the application layer, the context, everything that you've always loved on this, and at the same time, it's actually in Slack, looking native. Nobody would ever know that Salesforce is behind the scenes because the Headless interface is Slack. Then again there customers who like knowing they're in the Salesforce vertically-integrated stack, he points out: For them, Agentforce is just natural. They have that skill set. Their 'Trailblazers' know how to use Salesforce. They know what they want to get out of the Salesforce, Agentforce unlocks these new potential applications of it, and so they want to do that. I also talk to customers that say, "Hey, I have this investment in my coding agent or tools or whatever, and I would like to do it this way." I think Headless 360 speaks to both of them. Steering towards a car analogy Inzerillo drives this argument home with an automotive analogy: I'd say the vast majority of us buy a car and then we drive it around. Maybe we hang an air freshener, we certainly play our own music in the car. We do a bunch of things to make that car [suit]ourselves, but we don't physically change the car. There are people that modify cars, they change the suspension, they switch out the rims, they do all those sorts of things, and that's the way they want to drive their car. With us, we give you a couple of different series of cars that are fit for purpose for those particular industries or size companies, small business, etc. We give you a bunch of different choices in cars, and you can take the vertically-integrated car and not touch it, just customize it in the ways that we talked about, or you can go and fully modify that car. You can give them components of it and say, 'I want the Salesforce engine transmission and tires, but I'm going to put my own chrome on it. I'm going to do this and that'. The other thing is if you want to take that Salesforce version of it and you want to do really great things with it, it also comes with a pit crew, right, and a mechanic.That's really the testing center and all those sorts of thing. The aim of all this straightforward, he said: We're really trying to provide choice. We would like to win more than our fair share of folks that want to use the vertically-integrated stack because it just delivers so much value so much faster, but we also want a rich environment of people taking components of it that they think are going to make their particular application - their 'car' better for them. We're trying to do both of those things and Headless 360 is the mechanism by which we're actually able to do both of those at the same time without having randomly different development efforts to try to support that. This multiple choice approach is what the market is asking for, he concluded: [People] saw what the capabilities were with Agentforce and what it could do internally. I think it's one of those things that have clicked for us and it clicked for the market at around the same time, like, 'Wow, wouldn't it be great if all the coding agents could take advantage of everything that Salesforce had to offer?'. The Headless 360 strategy is really about empowering the ecosystem of agents. My take If you can keep your head(less) while all around are losing theirs, as Kipling didn't quite say. But the great man's exhortation to keep calm and carry on isn't actually that appropriate here. As I noted last week, it's such early days for Headless 360 that no lasting damage is likely to have been done by any inadvertent mixed messaging post-launch, even if there is only one chance to make a first impression. It is important to put the record straight here though, such is the significance of the headless strategy as a whole. It's Salesforce Connections in Chicago from Wednesday - I imagine we may be hearing the clarified/polished Headless 360 pitch one or two times more before the week is out.

Have Salesforce customers been heading down the wrong path with their idea of Headless 360? CMO Patrick Stokes does a little course correction

CEO Marc Benioff calls it "probably the most exciting announcement" of the past three months for Salesforce. So why are customers seemingly confused by what the firm has to say about its Headless 360 offering? That was a topic aired during the post-earnings analyst call with Salesforce management last night and while what emerged wasn't a full scale course correction, it did suggest a need for clarification to get the real message across better. Benioff noted: This was the quarter where as we used the word Headless for the first time, we talked about it at TrailheaDX. I used it in a tweet, the tweet went really viral. It was a surprise to me, I'll be honest, because...the system was always built to be API-first. It has always done massive amounts of transactions and complex transactions. We've always reported those API figures. And now we even have a new API, which is our whole user interface basically spinning out of the platform as an API. He went on: In all cases, the platform has always been API first, all the applications have been API first, but when we announced Headless, everybody is like, 'Oh, they've lopped the top off of it', or, 'They've cut the applications off.' They kind of got confused in my opinion. Did they? Or was the messaging just not as clear as it needed to be? Discuss! Or as Benioff went on to ask: Where did that confusion come from for people? Why do they think headless means that there's no more application or Salesforce app? It was left to CMO Patrick Stokes to make a very obvious point here: Well, probably from the name 'Headless', which does seem to imply that. Er, well, yes...fair point. So what are they saying? But regardless, the wrong impression appears to have been given in too many quarters, so what's to be done to tidy up this misreading at what it is, fortunately, still very early days for the offering? Stokes argues: If you're in the technology world, it's been a term that's been used in technology for quite some time to imply that the UI is not directly linked to the underlying capabilities or services that are underneath it in this case, APIs. And yes, Salesforce has always been open. I think what people got so excited about here is this idea that Salesforce was endorsing this way of working. We were basically saying, 'Hey, we want you to take the value of Salesforce and the value that you get from our apps, from Sales, from Service, from Commerce and Marketing, and we want you to be able to work however you want to work, whether that's in Slack or whether that's in Claude or whether that's directly in the app'. That's what this capability really enables. I think people were really excited about that - and maybe a little inappropriately skeptical that we would have just locked it all down and said, 'No, it has to be in our app'. Salesforce is the most used set of APIs on the planet, he contends: What that means is when you're a builder, when you're out there building something - and this is especially true today because there's now an ocean of builders that have been created as a result of this coding agent boom - when you go to build something for your business, you, at some point, are likely going to want to connect to Salesforce. That is what we see. And it doesn't matter what platform you're doing it on - you can be building something on a competitive platform to Salesforce or on Google or AWS or one of our partners - but at some point, you're going to want to connect into Salesforce. That's why those APIs have always been hugely, hugely used. But when you are building with an agent, you need a slightly different type of API. That's what we call MCP (Model Context Protocol). By really putting those MCP servers out and saying, 'Yes, this is how we want people to build', I think it was a big surprise and a big move in the right direction. OK, so all that being said, what's the correct messaging that customers ought to take away from all this? Stokes pitches that there are two main things that are exciting about Headless 360: One, it's having a real impact on making it easier to implement with Salesforce. Building out with Salesforce has now become easier than ever because we've seen [with] these coding agents, Claude and Codex from OpenAI, as you use these things, what you realize is you need to be able to connect the underlying APIs, which you do through this layer that's called MCP. And if you can connect those into the coding agents, it makes it faster than ever to implement and deploy Salesforce. The second thing that he cited was that Headless 360 changes how people get value and consume Salesforce: In my experience, we're not seeing people take this capability and the coding agents, for example, and try to build all of this stuff themselves. What they want to do is they want to take this capability and they want to use Salesforce in different ways and get more value out of it. So rather than logging into this discrete application and this application and this application to get an answer to one question that might span multiple applications or multiple kind of sources of information, you can now just take these MCP servers and plug them into any tool that you want. They are inside our application, of course, with Agentforce Coworker, right up at that search bar. If you're a Slack customer, you can get to it right with Slackbot - that's really a Headless experience as well. But if you want to plug these into ChatGPT and Claude, you can do that as well. And all of this just results in more and more value being delivered to our customers from the Salesforce platform. What about the customers? While it is ludicrously early days for the Headless 360 push, there are examples of all this out there in the wild, with takeaway delivery firm JustEat cited as a case in point. The online delivery platform is using Headless 360 to bring agents into WhatsApp and other channels, engaging with 350,000 partners across 15 countries. But is the message going to get through to customers in general? According to the man on the customer frontline, Chief Revenue Officer Miguel Milano: The fact that we announced Headless at TDX made people think that this was just for builders and that now they can take our CRM apart and which they can now also, by the way. But I think the big breakthrough was not with the builder workers, but with the knowledge workers. He cited two examples to back up his point, beginning with Adecco, a firm which is a user and also partners with Salesforce in its r.Potential joint-venture: They have amazing recruiter agents going there, millions of transactions. They're moving into Voice. When we announced Headless, they called us and they are like, 'Wait a minute, let me try to understand what you're doing'...They have agents [from] some of the AI labs that [are] also trying to access our data. 'Are you saying that now these agents that we are building outside Agentforce can also leverage Salesforce?'. And we said, 'Exactly, we did it for that [reason]'. So now there's going to be a lot of new agents that are going to be accessing our platform. Example number two is AI firm Anthropic: Anthropic is one of our biggest users of CRM of Sales Cloud and Slack. Their usage through Q1 has exploded fivefold because now they are using Sales Cloud from a Headless perspective, and they are approaching it from Coworker, from other applications, from Slack, they're hitting Sales Cloud. So Sales Cloud has become more prominent and more strategic for them than ever because of Headless. Milano concludes: These are two examples, extreme examples, but this is every single conversation that I have with the customer, their smiles are big because of Headless. My take As noted above, it is very, very early days in the Headless adventure for Salesforce, so a minor course corection in terms of messaging at this stage is hardly a disaster from which the firm will struggle to recover. The two examples offered up by Milano are interesting, but they are also very specialist/technical. The JustEat use case sounds more like something 'Joe and Jean Salesforce' could get their heads - sorry! - around in terms of that important knowledge worker empowerment idea. Hearing more about that would be useful I suspect.