More than half of UK CEOs say they have seen no measurable return on their AI spend. PwC put the figure at 56 percent in January 2026. Around the same time, Gartner found that nearly a third of generative AI projects were quietly abandoned after the proof-of-concept stage by the end of 2025.
So before you decide to build your own AI context layer over a quiet weekend, it’s worth sitting with that for a second. These are not hobbyists giving up. These are businesses with budgets, engineers, and proper AI initiatives, and most of them are getting nothing measurable back. The building was never the hard part. The making-it-actually-work part is where it falls over.
Which brings us to the question I get asked more than almost any other when the AI context layer comes up: can’t I just do this myself?
It’s a fair question. And in all honesty, the answer is yes. You absolutely could. Let me explain why most people still shouldn’t, and what it tends to cost when they try.
You could build your own website too. WordPress is free.
Here’s the way I frame it.
You could build your own website too. WordPress is free. But you came to a professional because you wanted it done right, done properly, and done in a way that actually works for your business. This is the same principle applied to your AI infrastructure.
Nobody thinks twice about that logic when it comes to a website. WordPress, Wix, and Squarespace have all been free or nearly free for years, and yet web designers are still busy, because there’s a wide gap between something that technically exists and something that actually does its job. A free template gets you a website. It doesn’t get you a website that brings in clients.
An AI context layer is the same. The platform is the easy bit. You can spin up a Notion workspace this afternoon and start typing notes about your business into it. What you’ll have is a folder. What you need is a governed system that every AI tool you use can read from and trust, and that’s a different exercise entirely.
Building it is the easy 20 percent
When I look at the work that goes into a context layer, the actual building of it is roughly a fifth of the value. Maybe less. The architecture behind it is the product of hundreds of hours of real-world testing, the kind of thing AI can’t reproduce from a single clever prompt, because it doesn’t know what breaks until it has watched it break.
The other 80 percent is keeping the thing alive. This is the part nobody factors in when they imagine the DIY route.
A context layer is not a document you write once and file away. Your pricing changes. You launch something. You kill something off. A new competitor turns up. You refine a framework. Every one of those changes has to make its way into the system, or the system slowly starts telling your AI things that used to be true.
And here’s the quiet danger. An ungoverned context layer doesn’t fail with a bang. It degrades gracefully. No error message, no alert, just a slow drift into inaccuracy. Your AI keeps producing confident, polished output, except now it’s quoting a price you retired in March and describing a service you no longer offer. As I tend to put it, your system will lie to you, and you won’t know it’s lying.
That’s the trap with doing it yourself and then leaving it. AI abhors a vacuum. The problem is it doesn’t tell you when it’s filling one.
The bit you can’t Google: your own voice
There’s one part of building a context layer that catches almost everyone out, and it’s not technical at all.
Most founders can’t articulate their own voice without a skilled interviewer drawing it out. You know what sounds like you and what doesn’t, instantly, the moment you read it back. But sitting down and writing the rules for it, the phrases you lean on, the words you’d never use, the rhythm of how you explain things, is genuinely hard to do on your own. It’s the difference between speaking a language fluently and being able to write its grammar textbook.
This is where the analogy I keep coming back to is the guitar one. Anyone can buy a guitar. That doesn’t make them Hendrix. The magic isn’t in the instrument, it’s in knowing what to play, for whom, and why it matters. The tools to build a context layer are sitting there for anyone to pick up. Knowing what to put in it, and how to draw that out of a busy founder’s head, is the actual skill.
So a lot of the value of bringing someone in comes from the extraction rather than the typing. The structured conversations that pull out the stuff you’ve never written down because it lives in muscle memory, and turn it into something an AI can read.
AI output quality is the thing you’re actually buying
Strip all of this back and there’s one measurable difference between a real context layer and a folder of notes: the quality of what your AI produces.
I tested this on myself before I sold it to anyone. I gave the same AI model the same brief twice, once with no context and once with a full context layer loaded. Same model, same prompt, two completely different businesses came out the other end. One sounded anonymous and slightly off. The other sounded like the company. That gap is the whole game.
When I built the layer for my own business first, four specific gaps surfaced that I hadn’t expected, and they’re the same gaps most founders hit when they try. It’s also why this sits inside the wider shift the enterprise world has already named: context engineering. As I covered in why better prompts keep hitting a ceiling, the discipline of giving AI the right context is what separates the businesses getting real value from the ones still rewriting everything by hand.
The numbers back it up at every size of business. McKinsey found that only 1 in 10 companies successfully scale their AI agents. The other nine are running the same models as everyone else and feeding them worse context. For a five-person agency or a thirty-staff accountancy, that shows up in the most ordinary way imaginable: fewer drafts that need a full rewrite, a new hire who can produce on-brand work in week two instead of week six, less of the founder’s evening spent fixing tone. Quiet wins, but they add up fast.
So, should you build it yourself?
Now for the honest answer, because I’d rather give you that than a sales pitch.
If you have the time, the patience, and a real appetite for the governance side, you can build a decent context layer yourself. Some people will, and good luck to them. What I’d say is this: the question worth asking has very little to do with whether you’re capable. What matters is whether this is the best use of the one resource you can’t buy more of, and whether the system will still be accurate in six months when you’ve got a hundred other fires to put out.
For most founders, the maths lands the same way it does with the website. You could, but you came to a professional because you wanted it done right, done properly, and done in a way that keeps working after you’ve stopped thinking about it.
The good news is you don’t have to decide blind. There’s a simple way to see whether your AI output quality is actually where it should be, and whether the gaps are big enough to be worth handing over.
Where to start
I built a short AI Context Layer Risk Quiz that works as a diagnostic. It takes about six minutes and walks through where your voice, your offers, your client stories, and your strategic priorities currently live, then shows you the specific gaps that are dragging down your AI output quality. Take the quiz to see whether your AI output quality is where it should be. You get a personalised score and a short report, no sales call required.
Whether you build it yourself or bring someone in, the same truth holds. The model isn’t your advantage any more, because your competitor can buy the identical one for the price of a couple of lunches. What you give it to work with is the advantage now. Get that right and the output quality looks after itself. Get it wrong and no amount of clever prompting will save you. As always, if you want to talk it through, reach out to me. I’m always happy to help.