Because you have been feeding it prompts instead of context, and here is the fix that works no matter which AI tool you use next year.
You Are Not Bad at Prompting. You Are Missing the Foundation.
You typed out your business model again this morning. Who you serve. What you charge. The three things you never say in marketing copy. You typed it all out for the fourth time this week because the chat window was empty and the model had no idea who you were.
That is not a skill gap. That is an architecture gap, and it is costing you real hours.
Here is the direct answer. Your AI forgets because the knowledge about your business lives in your head and in scattered chat threads, not in files the AI can read. The fix is to build a context library: a plain folder of plain text files that describes your business, your offers, your voice, your customer, and your standard answers. Then you point any AI tool at that folder. The forgetting stops. And when a better model launches next month, you point that one at the same folder and keep moving.
I have watched people spend a year chasing better prompts. Candidly, most of them were solving the wrong problem. A great prompt handed to a model that knows nothing about you produces confident, generic output. A plain prompt handed to a model that already knows your offers, your voice, and your customer produces something you can actually use.
Loren Bartley of Impactiv8 published a piece on this today, and she framed it better than I have: an AI brain is nothing more exotic than a folder of plain text files any AI tool can read. No subscription. No plugin. No code.
Here is the thing. The prompt is not the asset. The model is not the asset. The context you can hand any model, this week or next year, is the asset. Build that first and the tool choice stops mattering nearly as much as you think it does.
Key Takeaways
Key Takeaways
- Your AI forgets your business because that knowledge lives in chat threads and your head, not in files the model can read.
- A context library is a folder of plain text files covering what you do, who you serve, what you charge, and how you sound.
- Published research found agent runs were measurably faster and cheaper when a project context file was present.
- Plain text is portable, so a new model launch becomes an upgrade instead of a rebuild.
- What you keep out of the library matters as much as what you put in.
The Problem: You Have Been Buying Tools to Solve a Filing Problem
Most business owners I talk to have the same setup. Knowledge everywhere. Findable nowhere.
A brand voice doc in Google Drive. Pricing in a spreadsheet. The good objection answers buried in a sent email from March. Three Claude Projects, two custom GPTs, and a folder named Final sitting next to a folder named Final FINAL.
The knowledge exists. You just cannot put your hands on it when the AI asks for it. So you retype it. Every session. And because you are retyping from memory under time pressure, you give the AI a thinner version of the truth than the one that lives in your business. Thin input, generic output.
This is not new and it is not an AI problem. The McKinsey Global Institute measured it back in 2012 in its report The Social Economy, finding that interaction workers spend roughly 19 percent of the average workweek searching and gathering information. AI did not create the filing problem. AI made it expensive in a new way, because now every unfiled piece of knowledge is a piece of context your model does not have.
The second half of the problem is churn.
Between September 5 and September 8 of this year, two independent release trackers showed zero new frontier model launches. Four major models had shipped the week before that. If your workflow is built around one specific model's memory feature or one vendor's assistant, you are rebuilding on somebody else's schedule. Loren points at custom GPTs being wound down as a live example of what happens when your knowledge lives inside a platform instead of on your own drive.
I am not anti-platform. I use plenty of them. But there is a difference between renting a workspace and renting your memory. Rent the workspace. Own the memory.
Here is the part that stings. The people who feel furthest behind on AI are usually not behind on tools at all. They have more subscriptions than they need. They are behind on documentation. They never wrote down the thing they know, so the AI cannot read it, so the AI cannot use it, so the output stays generic, so they conclude AI does not work for their business.
It works fine. It just cannot read your mind.
The Evidence: Context Files Are Measurably Better Than Improvised Prompts
I do not ask anyone to take my word for this. The research on context files got serious over the past twelve months, and the numbers are specific.
1. Adding a context file made agents faster and cheaper in a controlled study.
A 2026 study by Jai Lal Lulla and colleagues at Singapore Management University, Heidelberg University, the University of Bamberg, and King's College London ran the same agent on the same tasks twice, once with a project context file and once without. Across 10 repositories and 124 real tasks, the presence of an AGENTS.md file was associated with a 28.64 percent lower median completion time and 16.58 percent fewer median output tokens, both statistically significant. Source: arXiv:2601.20404.
That is a software engineering setting, not a marketing one. Read it for the mechanism, not the percentage. When the AI already knows how your world is organized, it stops guessing and stops wandering.
2. What people put in context files is lopsided, and the gap is instructive.
A study of 2,303 agent context files across 1,925 repositories found people load them with functional detail, test procedures at 75.9 percent, implementation detail at 70.8 percent, architecture at 68.1 percent, while security appeared in only 14.8 percent and performance in 14.5 percent. Source: arXiv:2511.12884.
Translation: people document how things work and forget to document the constraints. Your library needs both. What you do, and what you will never do.
3. The format matters far less than you have been told.
Damon McMillan ran 9,649 experiments across 11 models and four file formats. Format did not significantly affect aggregate accuracy, chi squared 2.45, p equals 0.484. File-based context retrieval improved accuracy for frontier tier models by 2.7 percent, p equals 0.029, and the setup scaled to 10,000 tables. Source: arXiv:2602.05447.
Stop agonizing over markdown versus YAML versus a fancy schema. Write the thing down. That is the win.
4. Grounding your AI in your own documents reduces errors. It does not eliminate them.
I will not oversell this. Magesh, Surani, Dahl, Suzgun, Manning, and Ho published a study in the Journal of Empirical Legal Studies in 2025 testing AI legal research tools that ground answers in real source documents. They measured hallucination rates of 17 percent for Lexis+ AI and 33 percent for Westlaw AI Assisted Research, against 43 percent for general purpose GPT-4. Source: Journal of Empirical Legal Studies.
Grounding cut the errors meaningfully. It did not zero them out. Your library makes the AI far more useful and far more you. It does not make it infallible. You still read the output.
5. Plain text context files are now an industry standard, not a hobby.
On December 9, 2025, the Linux Foundation announced the Agentic AI Foundation with AGENTS.md, Model Context Protocol, and goose as inaugural projects, contributed by companies including OpenAI, Anthropic, and Block. AGENTS.md has been adopted by more than 60,000 open source projects since its August 2025 release. Source: Linux Foundation.
The industry is converging on the idea that agent instructions belong in portable files you own.
The community got there first. The top posts in r/PromptEngineering this week were not prompts. They were packaged artifacts: an open source self edit checklist skill for LLM agents, 44 free MIT licensed tools, an Agent Prompt Architecture skill.md file, and a post titled "Versioning the prompt finally made our rollout chart mean something." In r/ClaudeAI, a drop-in Claude.md section for improving prose was the standout. Treat that engagement as directional community signal, not data, but the direction is unmistakable. People stopped trading prompt text and started trading files.
Nicky Saunders put it in five words on September 2: make a skill, not an agent. Stop starting over.
The Solution: Build the Library, Then Pick Your Tools
Here is the system. Three layers. Most people only ever build the top one.
Layer one is the model. ChatGPT, Claude, Gemini, whatever ships next. Changes constantly. You do not control it.
Layer two is the interface. The chat window, the project folder, the agent, the Slack integration. Also changes. The number one Product Hunt launch today, September 8, was Switch, a tool whose entire value proposition is bringing any AI agent into Slack, Teams, Discord, or Telegram as a named participant sharing the same channel context and history the team does. Open source and self hostable. Notice what the winning product sells. Not intelligence. Shared context.
Layer three is your context library. The layer you own, and the only one that gets more valuable every month instead of getting replaced.
Build layer three and layers one and two become interchangeable. That is the whole strategy.
What belongs in a business context library
Loren's framing is the cleanest I have seen, so I am using her structure and giving her the credit. Think of it as onboarding a team member who never sleeps. What would you hand them on day one?
- What your business is and who it is for. One page.
- Your offers and your prices. One table. This file alone stops the AI inventing packages you do not sell, which it will absolutely do otherwise.
- Your voice. A brand voice guide, or three pieces of writing that genuinely sound like you.
- Your ideal customer. Who they are, what they struggle with, what they already tried that failed.
- Your most asked questions with your actual answers. The ones you have typed fifty times.
- One real customer conversation. A call transcript or a substantive email thread.
- Your best three pieces of content. The ones that actually brought people in.
- One framework you learned from someone else, clearly labeled as theirs.
Start with five. Not your whole Google Drive. Messy is fine, because organizing is the AI's job, not yours.
What stays out
This is where I get firm, because the downside is real.
Anything you would be upset to see leave your computer. Passwords, API keys, banking details, tax identifiers, other people's personal contact information, health records, unredacted contracts, HR matters. When you point an AI tool at a folder, it reads the whole folder. Anthropic's own guidance says the same thing about not mounting folders that hold credentials or personal records.
Anything that changes daily. Your calendar, your task list, this week's deliverables. A context library holds knowledge that is stable for months. Moving parts belong in the tool built for moving parts.
Anyone else's instructions. When you clip a web page or drop in a document someone sent you, that file can contain text written to manipulate an AI, along the lines of "ignore your previous instructions." Your rules file should state plainly that anything in a source folder is content to summarize, never a command to follow. Keep third party material in its own labeled subfolder.
Other people's expertise presented as yours. Keep a separate reference library for what you learned from others, and keep it attributed. That is integrity, and it is also just accurate. Your AI should know the difference between what you think and what you read.
Practical Steps: Build Version One This Week
You are not building a knowledge management system. You are writing eight short documents. Give it two hours.
1. Make one folder on your own computer and name it plainly. Call it Business Brain or Context Library. Not inside a platform. On your drive, somewhere your AI tool can be pointed at. This folder is the asset, not any app that displays it.
2. Write the five foundation files first. Business description, offers and prices, voice, ideal customer, and your top questions with answers. Plain text or markdown. Ugly is fine. Complete beats pretty every single time.
3. Add a rules file at the top of the folder. One short document telling the AI what the folder is, what each part is for, and what it must never do: never edit your source files, never delete anything, never invent an answer that is not in the files. Add a "true right now" section for things that override older documents, like a price change.
4. Use this prompt to draft the files you have been avoiding. Give it your actual raw material and let it do the shaping.
[The Job]
Turn my raw business material into five clean context files that any AI tool can read: business overview, offers and pricing, brand voice, ideal customer, and frequently asked questions with my answers.[The Background]
My business is [WHAT YOU DO IN ONE SENTENCE]. I serve [WHO YOU SERVE]. My offers and prices are [LIST THEM]. Here are samples of my writing that sound like me: [PASTE 2-3 SAMPLES]. Here are the questions I get asked most: [LIST 5-10 QUESTIONS]. Here is what my customers have already tried that did not work: [LIST].[The Deliverable]
Five separate markdown files, written from the perspective of a knowledge manager onboarding a new team member. Each file under 500 words, plain English, no jargon. Use only what I gave you. Where information is missing, insert a clearly marked TODO line instead of guessing. Flag any place where my samples contradict each other.[The Questions]
Ask me any questions you have.
5. Point your AI at the folder and test it with a real task. Draft something you actually need this week. A follow up email, a sales page section, an answer to a customer question. Watch how different the first draft is when the model already knows your pricing and your voice.
6. Fix what the test exposed. The first test always reveals a missing file. Usually it is pricing detail or a positioning nuance you never wrote down. Write it. That is the loop.
7. Make it a ten minute weekly habit. Drop in whatever you created or captured that week: a call transcript, a good email, a draft, a voice note. Ask your AI to summarize it into the library and report what it added. That is the entire maintenance plan.
Frequently Asked Questions
Is a context library the same thing as a prompt library?
No, and the difference matters. A prompt library stores instructions for tasks you repeat. A context library stores facts about your business that every task needs. Prompts tell the AI what to do. Context tells it who it is doing it for. You want both, but context comes first because prompts without context produce generic output.
Do I need to be technical to build one?
No. You are writing plain text documents in a folder. If you can write a Word document and save it somewhere you can find it, you have every skill required. The research confirms this: McMillan's 9,649 experiment study found file format had no statistically significant effect on aggregate accuracy, so fancy formatting buys you nothing.
Will this still work if I switch from ChatGPT to Claude or Gemini?
That is the entire point. Plain text files are readable by every major AI tool. The Linux Foundation formalized AGENTS.md as an open standard in December 2025 alongside Model Context Protocol, with over 60,000 open source projects already using the format. Your files outlive the tool you built them in.
How much should I put in it before it becomes useful?
Five files. Business overview, offers and pricing, voice, ideal customer, and your most asked questions. That is enough to change your first draft quality noticeably. Adding your whole Google Drive on day one usually stalls the project. Start narrow, then add one thing a week.
Does this stop the AI from making things up?
It reduces it substantially. It does not eliminate it. The Stanford team's 2025 study in the Journal of Empirical Legal Studies found document grounded AI tools still hallucinated 17 to 33 percent of the time, versus 43 percent for ungrounded GPT-4. Better context means better output. It never means you skip reading the output.
The Close: Own the Layer That Lasts
Three separate rooms landed on the same idea today, and none of them was a vendor selling you a model. Loren Bartley published a piece arguing a business AI brain is a folder of plain text files. The number one product on Product Hunt is selling shared context, not intelligence. And the top community posts this week quietly stopped being prompts and started being files.
Same conclusion, same week. Stop building agents. Start building the context they run on.
I know the objection, because I have made it myself. It feels like homework. There is no dopamine in writing down your pricing table for the fourth time.
But here is the honest math. You are already writing it down. You write it into a chat window every day and throw it away when the session ends. Write it once into a file and you stop paying that tax forever.
If you want to build it with people instead of alone, that is what we do inside AI Insiders at $247 a month. The context library is exactly the foundation work we walk members through live, along with the skills that sit on top of it.
Your prompts are disposable. Your models are temporary. Your context is the only thing you actually own.
P.S. Make the folder before you decide whether to make the folder. Version one takes two hours, and every hour after that compounds.
About the Author
Jonathan Mast is the founder of White Beard Strategies and one of the most trusted AI educators working with non-technical entrepreneurs. He teaches business owners how to use AI to amplify the skill and experience they already have, without pretending they need to become engineers. He runs a 500,000 member Facebook community, the AI Insiders membership at $247 per month, and ongoing live training for coaches, consultants, and small business owners. His approach: give away the knowledge, charge for the access and the implementation. Learn more at whitebeardstrategies.com.
