You cannot buy your company brain, and this week proved it

AWS started this in June. The rest of the market caught up this week: three announcements in three days, and somewhere in the middle of them the "context layer" finished its journey from a phrase engineers use in architecture diagrams to a category you can put on a purchase order. Salesforce shipped a way into its version. A London company that had gone nine years without outside money took $22M to build one, and a startup founded by three ex-AWS engineers went generally available with a seed round behind it.

The category is real, and I want to say that up front because most of what follows is an argument against buying it. But the conclusion a small business is being invited to draw from this week is wrong, and it will cost people money.

What an AI context layer for business actually is

Strip out the vocabulary and every one of these products does the same job. It points at systems you already run - the CRM, the ticketing queue, the warehouse, the job management platform - reads what is in them, works out how the records relate, and hands your agent a governed view of it at the moment it needs one.

AWS calls its version Context. It was announced at the New York summit in June, and the pitch is that it builds the knowledge graph automatically from your existing organisational data rather than making somebody curate it, so you stop hand-rolling retrieval pipelines. VentureBeat called that entering "the context layer race". The rest of the field spent this week proving the race exists.

Yesterday Salesforce expanded Headless Data 360 for MCP, exposing 200-odd existing APIs as programmable endpoints so an agent can pull governed customer context with no UI in the way. The same day Prevalent AI raised $22M from Integrity Growth Partners to scale trusted enterprise context, and the detail worth noticing is that this was the first primary outside investment in the company's nine-year history. A security data fabric business repositioned around context and the cheque arrived. Two days before that, xpander went GA on a $7.5M seed, selling a vendor-neutral control plane to enterprises drowning in agents.

Different companies, one sentence: point this at your systems and your agents will finally understand your company.

That sentence has a hole in it, and the hole gets wider the smaller you are. A graph is an index of what you already recorded, and it is very good at that. But in a fifteen-person business, the knowledge that decides whether an agent is useful or dangerous is the knowledge nobody ever recorded.

The 45-point gap nobody can sell you out of

The Modern Data Company released interim findings from its third annual survey yesterday, and the numbers accidentally make my case better than I can. Across 540-plus qualified responses from 66 countries, 60.9% consider a reliable context layer necessary. Only 16.0% deliberately engineer context as a product.

Hold the caveats where you can see them. This is interim, it is self-selected, the respondents are data leaders and practitioners who chose to answer, and it skews enterprise. These are not small businesses. They are the professionals whose job this is.

Which is what makes the gap interesting. Forty-five points separate the people who believe they need a context layer from the people who are actually building one, among a sample that could sign a vendor contract this afternoon. Budget is not the binding constraint. Neither is belief. Every one of those 60.9% could buy AWS Context or Salesforce Data 360 by Friday and the gap would still be 44.9 points wide on Monday, because engineering context means deciding what your own terms mean and writing that down. Nobody sells that.

The rest of the survey reads the same way. 8.4% say the data feeding their AI is production-ready. 63.5% name missing context and lineage as an obstacle. 75.9% rank data quality and trust among their top three barriers. Meanwhile 57.3% are already piloting or running agents, with 23.5% in production. Saurabh Gupta, the chief executive, puts it as "the harder question is whether those agents have the trusted data and business context they need to operate reliably."

Agents in production, data nobody trusts. That combination is the whole reason this week happened.

Why AI agents give confidently wrong answers about your business

Sit with an estimator for an afternoon and you can watch this happen.

Your job management system records that you quoted job 4821 at a particular number. It does not record the margin you will not go below. It has nothing to say about the two customers who get a different number because of what happened in 2019. It has never heard of the loading your best estimator applies to anything involving a two-storey install, which they have never written down because to them it is not a rule, it is just how you do the job.

Index all of that and you get a beautiful graph of outcomes with the reasoning stripped out. An agent reading it can tell you what you charged. Ask it what you should charge and it will produce a number, confidently, because it has 4,000 examples of numbers and no statement of the rule that produced them. The honest response would be "nobody has told me", and that is not what these systems do.

This is where the reflex kicks in, and it is the same one I keep writing about: a knowledge problem gets met with a purchase order. It feels like progress, and it is a great deal faster than sitting down with your estimator for a morning. It also leaves the gap exactly where it was.

Where buying an AI context layer does pay off

There is a real case on the other side of all this, and it starts at a scale most people reading this will never reach. At 5,000 staff and 400 systems, writing things down is not your constraint. Your constraint is that "customer" means four incompatible things across four platforms and no human alive can hold the relationships in their head. TechTarget's Scott Thompson framed it this week as "the bottleneck isn't volume, but context", and quotes Collibra's chief executive Felix van de Maele on the "hallucination tax" enterprises pay when agents run without governed context. Thompson's own read on what that tax buys you: a human-in-the-loop verification bottleneck that "erodes the productivity gains that justified the AI investment." A real cost with a real remedy, and the remedy is infrastructure.

Scale makes it worse fast. Gartner estimates, as reported by VentureBeat, that the average Fortune 500 company will run more than 150,000 AI agents by 2028, up from fewer than 15 last year, while only 13% of organisations think they have the right governance today. If that is your 2028, buy the control plane. Buy two.

So no, the vendors are not selling snake oil, and I have no interest in the cheap version of this argument. AWS Context building a graph automatically instead of by hand is a genuine improvement on the previous state of the art. Salesforce exposing 200 APIs so agents get governed customer data is straightforwardly good engineering.

My argument is about category, not quality. Infrastructure moves recorded knowledge around and makes it reachable. It cannot manufacture unrecorded knowledge, and no amount of funding changes that, because the missing input is a judgement somebody in your business has to make out loud for the first time. The coverage of the Prevalent AI round gets within one word of it: the challenge is shifting "toward whether it has access to accurate information about the organization in which it is operating". Access to accurate information. Access assumes the information exists.

Do I need a knowledge graph for AI agents, or do I need to write things down?

Anthropic published a number in June that I have quoted in client rooms more than any other this year. On its own internal evals, for analytics questions specifically, Claude's accuracy "didn't exceed 21%" without skills. With them, "consistently above 95%". Skills, in that post, are defined as procedural knowledge encoded in markdown files.

Take the caveats seriously. Those are Anthropic's evals, on Anthropic's data model, measuring one narrow class of question. Do not carry 21-to-95 into a board paper as a general business benchmark, because it is not one.

The shape of it is still the point. Anthropic has as much data infrastructure available to it as anyone on earth, and what closed the gap between useless and reliable was somebody writing out how the question gets answered. Not a new retrieval architecture. Files.

That is the same argument I made from the other direction a week ago, when OpenAI's telemetry showed frontier firms pulling 8.3 times the output per user out of identical models. That post was about what the winners write. This week is about what the market would like to sell you instead.

What I would actually do with a Thursday afternoon

If you run a business under a hundred people and this week has you worried, the useful response is smaller and less satisfying than a procurement process.

Pick the workflow where a wrong answer costs real money. Usually that is quoting. Sit with whoever is best at it and get the rules out of their head and into a file: the floor, the thresholds, the exceptions, and an honest note about which situations the rules do not cover. Two pages is a good first target. Then connect the one or two systems that hold the facts, so the agent stops guessing at what it cannot see.

That is a context layer. It cost you an afternoon and it is worth more to a small business than a knowledge graph over records that never explained themselves.

The catch is that written knowledge rots faster than infrastructure does, so once you have written it, somebody has to own it and it has to carry an expiry date. A file with no name against it is a liability with better formatting.

The vendors will keep raising, and enterprises will keep buying, and both of those things are fine. Just do not read this week as permission to skip the part nobody can do for you.

FAQ

What is an AI context layer for business?

Why do AI agents give confidently wrong answers about my company?

Do I need a knowledge graph for AI agents?

tags: company-brain ● context ● agents ● adoption