Salesforce + Contentful: From Website Content to Agent Context
This week Salesforce signed a deal to acquire Contentful, and most of the coverage is filing it under CMS M&A. I think that misses what’s actually being bought. The interesting part is what an AI agent does with a content platform.
An agent doesn’t take your content and show it to someone. It reads structured, governed source material – your context – and writes the content itself: the answer, the reply, the assembled page, generated on the fly, per customer, per channel. So the most valuable thing you can hand an agent is context it can trust.
That distinction matters more than it sounds. Agents are moving into production quickly, and they will answer your customers and your own staff straight from that material. Point one at clean, governed context and it’s useful. Point it at stale, contradictory, ungoverned content and it will hand back a fluent, confident, wrong answer. Garbage in, confident-sounding garbage out. Either way, it’s speaking for you.
I’ve argued before that content won the web, but context wins the agents, that the CMS was quietly becoming the layer agents reason over. This deal is the biggest CRM on the planet putting real money behind exactly that. Oomph is a gold-certified Contentful partner. We build on the platform daily, and we’ve integrated it with Salesforce and the systems around it. So I’ve been watching this one closely.
So look at what Salesforce already owned. Customer data, and plenty of it – they paid $8 billion for Informatica last year to pull it all together. CRM, marketing, commerce, service. Agentforce on top, ready to act. The one thing they couldn’t pull out of a customer record was the context an agent needs to say something trustworthy: approved product facts, current pricing, the disclosure that has to run in a regulated market, the brand voice, and the right localized version for each audience. Contentful holds all of that. It fits a pattern, too – Informatica, then Momentum, Qualified, Cimulate, and now Contentful. That’s a company building an agent stack on purpose, one acquisition at a time. They decided the context layer was worth buying rather than building.
A customer record can’t tell an agent what it’s allowed to say
Your CRM knows who the customer is. It has no idea what you’re allowed to say to them.
That gap is the whole game. Ask an agent “what’s the current return policy in Germany for this product line” and it will answer either way. Whether the answer is right comes down to three things. Your data tells the agent who is asking. Your context, the structured, governed, current truth behind everything, is what it reasons from. And the content is what the agent generates out of that context in the moment. Data and content are the parts most companies already plan for. Context is the part that gets treated as an afterthought, and it’s the part an agent leans on most.
Jujhar Singh, who runs the applications group at Salesforce, framed the deal around three things working together: the data, the AI-driven content, and the experience. Context is the thread running through all of it. The agent generates the content live, the experience is only as good as what it generates, and both stand on whether the context underneath is trustworthy. That’s what Salesforce bought: the governed context everything else gets built from.
The old acronym survives. The job is changing.
For twenty-five years a CMS has been a Content Management System: somewhere to keep content and push it onto a page for a person to read. An agent uses the same system for a different job. It reasons over that governed context and generates whatever needs to be said from there. Same three letters, new system. The CMS is turning into a Context Management System, and Salesforce just paid to own one.
The headless platforms saw this coming. They had already solved the hard parts an agent needs – structured models, versioning, permissions, and audit trails – and were adding the connective tissue to talk to agents directly. When the biggest player in the category backs that direction with a checkbook, the rest of the market should take the hint.
The old job doesn’t go anywhere, to be clear. Plenty of organizations are running Contentful today purely to manage website content, several of them clients of ours, and that work is the foundation the rest of this gets built on. The structured models, the editorial workflows, the governance, the API-first delivery you set up to run a modern website are the exact things an agent reasons over. You built it to publish pages. You were also building the context layer, whether you planned to or not.
And context reaches well beyond the public website. A lot of it lives in intranets and internal systems: the policies, the procedures, the product knowledge, and the operational detail that actually run the business. That changes who owns the platform. For most of its life a CMS was a marketing purchase, a tool for the brand and the website. Once agents need that governed internal context too, it outgrows marketing, and ownership moves to IT, data, and the enterprise. That shift is already underway, and if you sit in one of those teams, it’s landing on your desk whether you asked for it or not.
The part most of the coverage will skip
The blast radius isn’t the same for everyone. For a retailer, a wrong answer is a bad refund. For a hospital, a bank, a university, or a regulator, it’s a misinformed patient, an exposed internal document, or a benefit you never actually offered. Same technology, very different exposure, which is why governed context is a bigger deal for the organizations we work with most – in healthcare, higher education, government, and associations – than the headlines suggest.
There’s a sovereignty question here too, and it lands hardest on the public sector. Contentful is a German company, and bringing it under a US owner pulls it under US law, including the CLOUD Act. With the EU moving to restrict sensitive public-sector data on US clouds, a government or higher-ed buyer should put that on the question list, not in a footnote.
Where this leaves you
The instinct in most organizations is to make more content. The work that matters now is getting your context in order – structured, current, owned, and governed – because your agents will generate from it whether it’s clean or not. The content platform becomes a system of record: where brand, policy, product knowledge, and compliance live, and where your agents go to find the truth.
If you already run Contentful, the practical news is reassuring. Salesforce has said it keeps operating on the same platform, APIs, and support model, with tighter Agentforce integration as the roadmap rather than a forced migration. Nothing about your current build breaks. The move now is to point the foundation you’ve built at what’s coming next, and that’s a conversation we’re already having with clients.
The organizations that get their context right now are the ones whose agents will be worth trusting later. The big platforms have started spending real money to get there. The window to do the unglamorous work before your agents go live is open right now, and I don’t think it stays open long.
Oomph is a digital experience consultancy serving regulated industries and mission-driven organizations, including healthcare, higher education, government, and associations, where compliance, accessibility, and trust are non-negotiable.
