How to Make Claude Know Your Business: A Context Vault in Notion
Every new AI chat starts at zero. Here's the five-page Context Vault in Notion that Claude reads before it answers, with an exercise to build your own.

Same question, two answers
I asked Claude the same question twice. In a normal chat, it wrote a polite email with a blank for the name, a blank for the price and a promise the business would never make. Inside a project connected to the business, it used the real package, the real price and the way that business writes.
It's the same model and the same question. The second answer read the business before it answered.
Why Claude forgets your business
Claude has read more than any of us will read in a lifetime, and it knows nothing about your business. Your offers, your prices, your clients and the decision you made last week are not in there.
Every new chat is a brilliant new hire on their first morning. They're smart, fast and eager, and they know nothing about how you work. Hand them a task without onboarding and you get a generic answer. Then you explain the company, and tomorrow you open a new chat and explain it all over again.
Claude can remember some things from past conversations now, and that helps. Memory is what Claude picked up along the way. Context is what you decided it should know. For a business you want the second one, written down in one place and under your control.
Years of notes
I've been working with knowledge, languages and what we now call context for twenty years, and for most of that time I wrote everything down: notes, documents, spreadsheets and whole knowledge bases for the companies I worked with. When AI arrived, years of my own thinking were already written down, and the models became useful to me the day I pointed them at it.
For a business, five pages and a map are enough to start.
Five pages and a map
A Context Vault is a structured library of your business that AI reads before it answers. Mine lives in Notion, and Claude reads it through MCP, a live connection that lets Claude open your Notion pages directly, the way a colleague opens a shared folder.
- Business overview: what you do, who it's for and what makes you different, in plain words.
- Offers and pricing: every offer, what's included, the price and the things you never do.
- Audience: who buys, what they struggle with and the words they use for it.
- Voice: how you write, with two or three of your own emails as examples.
- Decisions: a running list of the choices you made and the reason for each one.
Then the map: one page called Start Here that tells Claude which page to read for which kind of question. It's the table of contents for your business. Without a map Claude has to search, and search is a guess. With a map it knows where to look first, and it tells you when the answer isn't in the vault.
Hands-on with a sample studio
For the video I built a vault for a sample design studio called Northline Studio.
- Connect Notion in Claude's settings, under connectors. You do it once.
- Create a Claude project with one instruction: before answering anything about the business, open Start Here and follow its map, and if the answer isn't in the vault, say so instead of guessing.
- Ask the question. Claude opens Start Here, then Offers and Pricing, then Voice, and writes the follow-up email with the real package name, the price and the sign-off this business uses.
Then I asked whether to offer twenty percent off to close the lead. Claude found the decision logged in the vault, no discounts and the smaller package instead, and explained the reason. Nobody on the team had to remember that decision, because the vault remembered it.
What ships with every system
Every system I build ships with three more things, and they matter as much as the build:
- A guide: one page that says who owns the system, what it may touch and who to call when something breaks.
- A job aid: one page the person keeps next to them, with the three things they do every day.
- A champion: someone on the team who learned it from me and can teach the next person.
A tool people learn from a colleague keeps getting used, and a tool that arrives as a mandate gets forgotten. The measure I use after three months: does the team still use it without being told, and how many hours did it give back?
Two limits
- The vault is only as good as what you write in it. If the pricing page is out of date, Claude will quote the old price with full confidence.
- It needs a minute of care. I add every new decision the day I make it.
In my experience, for someone who uses AI every day, this gives back two to three hours a week of re-explaining, and the answers get more specific as the vault grows.
Your turn
Here's an exercise to build your own setup. Open a blank page and write five headings: what we do, what we sell, who buys, how we sound and what we decided. Under each one, write three to five sentences, the way you'd explain it to a new hire on their first morning.
Add it to a Claude project as project knowledge, or to a Notion page if you use the connector. Then ask the same question twice, once in a normal chat and once inside the project. Look for the sentence in the second answer that sounds like you. That sentence is your proof the vault is working.
The full Context Vault, with the structure I use and the systems that read from it, is at dimagornovskyi.com/projects. Take a look and apply whatever helps.