AR Digital / Daily AI
AI context sheet: stop re-explaining your business with every request
One page presenting your business, saved once in a Claude project or its equivalent: more accurate answers from the very first request.

Radu UleaFounder of AR Digital

If every team member starts their requests to the AI with three lines explaining who you are, you pay for that time every day, and the answers stay generic. A well-written page, saved once in the right place, solves both problems.
Daily AI. Today’s advice: stop re-explaining your business to the AI with every request. Write a context sheet instead, a single page. Who you are, who you work for, what you sell, your tone, your rules, and one or two texts you consider successful. Save this page once and for all in a Claude project, or in the equivalent space of your assistant. You no longer have to paste it again, and the whole team starts from the same base. Test it on five real questions, and when an answer goes off track, fix the sheet, not the answer. One trap: put in no client data and no passwords. The sheet says how you work, not what your files contain. The detail is just below.
The context sheet is a page that describes your business, your clients, your tone and your rules. Saved in a Claude project or in the equivalent space of your assistant, it saves you from re-explaining your business with every request. Your teams get more accurate answers from the very first request.
The problem: an AI that does not know you
By default, an assistant such as ChatGPT, Claude or Gemini knows nothing about your business at the start of a conversation, apart from what you have already told it. It does not know that you sell to accounting firms rather than to private individuals, that you address your clients formally, that you work in French and German, or that you never promise a deadline without the project manager’s sign-off.
Without this information, it fills the gaps with averages. The result looks like a decent text, but it rings false: too salesy, too casual, or off the mark for your market. The team member corrects, tries again, adds context as they go. Everyone does it in their own way, and two people on the same team get two different tones for the same client.
This is not a flaw in the tool. It is a flaw in the instructions, and it can be fixed once and for all.
The habit: a one-page context sheet
The context sheet fits on one page and answers six questions. Who we are, in two sentences. Who we work for, with the type of client and their level of knowledge. What we sell, and what we do not do. Our tone: formal or informal address, sentence length, words we avoid. Our rules: what we never promise, what goes through human sign-off. And one or two examples of texts we consider successful.
This page is only worth something if it is saved in the right place, where the assistant finds it without you having to paste it again. If your team uses an assistant other than those named here, look in its help for a workspace or standing instructions feature.
- Claude offers projects: a space with its own conversations, a knowledge base where you can drop documents, and instructions that apply to every conversation in the project. According to Claude’s help centre, projects are open to everyone, including on a free account, limited to five projects.
- Gemini is in the middle of a transition: its Gems are giving way to skills, reusable instructions that you call up in a conversation and to which you can attach files. For now, skills are reserved for personal Google accounts of people over 18; on a professional Workspace account, the sheet is still saved in a Gem, which will be converted automatically into a skill. According to Google’s help, the switch happens in November 2026 for personal Google accounts and in March 2027 for professional Workspace accounts.
This space can also be shared with your colleagues, depending on the tool and plan. In Claude, sharing a project is reserved for Team and Enterprise plans, unless the administrator has turned it off, and the help centre describes two levels of rights: view and chat, or edit the instructions and the knowledge base. On the Gemini side, a Gem can be shared on a work account according to the Drive sharing rules set by your Workspace administrator, but Google says sharing of skills will only arrive in the coming weeks. The whole team then starts from the same sheet.
A step-by-step example
Take a fictional accounting firm of twelve people that wants to answer its clients’ email questions faster.
- Write the sheet, without AI. Thirty minutes with the head of client relations. Two sentences about the firm, the client profile (owners of small companies, not at ease with accounting vocabulary), the tone (formal address, short sentences, no unexplained jargon), three firm rules: no tax amount announced, no deadline promised, any complex tax question referred to a meeting.
- Add two real replies that the team considers exemplary, after removing the clients’ names and figures.
- Create the project “Client replies”, paste the sheet into the instructions and drop the two examples into the knowledge base.
- Test on five real questions from last week, anonymised. Each time an answer goes off track, fix the sheet, not the answer. This is the habit that makes the difference: one fix in the sheet serves every later request.
- Share the project with the team, which in Claude requires a Team or Enterprise plan, and name one person who rereads the sheet every quarter.
To copy into your instructions. “You help the team at [firm], an accounting firm in Luxembourg, to reply to emails from its clients, owners of small companies. Always use the formal form of address. Short sentences, no unexplained jargon. Never announce an amount or a deadline. If the question calls for a tax analysis, suggest a meeting. If you are missing some information, ask a question instead of guessing.”
The last sentence of this example matters more than it seems. Allowing the assistant to ask a question limits the risk of invented answers to fill a gap.
The traps to avoid
The classic trap is turning the sheet into a warehouse: the client list, negotiated prices, portal passwords, a CRM export. The sheet describes who you are and how you work. It does not contain your files.
There are two reasons for this. First, your clients’ personal data falls under the GDPR, and where it can go depends on the tool and plan chosen, not on the convenience of the moment. If this concerns you, our article on local AI in business details the options. Second, a sheet that is too long gets diluted: the assistant treats the important rules at the same level as the detail.
Second trap: the sheet locked into a single tool. Features change, as the transition from Gems to skills at Gemini shows. Keep the reference version in a document of your own, then copy its content into the tool of the moment.
Last trap: the frozen sheet. A sheet that still announces the old offer produces wrong answers, with great confidence. Hence the quarterly review, put in someone’s calendar.
Our take
In the teams we support, the gap between the people who really benefit from AI and the others rarely comes down to the choice of tool. It comes down to the quality of the context given. The context sheet is the first exercise we have people do in a workshop, because it forces the team to write down what it knows implicitly. It is often the most useful part of the day, AI or not.
Going further with your team
A sheet written alone at a desk already gives better results. A sheet built as a team, tested on your real cases and adapted by role changes the way the whole company works with AI. It is also a concrete way to contribute to the AI literacy obligation set out in the AI Act, which we detail in this article on training teams.
In Luxembourg, this kind of support can be partly funded: we explain how in our guide on funding AI training through SME Packages.
Frequently asked questions
Does a context sheet need a paid subscription?
No. The sheet itself is just a document. To save it in a workspace, Claude offers projects to all its users, including on a free account with a maximum of five projects. Sharing with colleagues, on the other hand, depends on the plan: in Claude, it is reserved for Team and Enterprise plans.
What if my team works with Gemini?
Gemini is replacing its Gems with skills, reusable instructions to which you can attach files. According to Google’s help, the switch happens in March 2027 for professional Workspace accounts. Until then, on a Workspace account, save the sheet in a Gem: it can be shared under your organisation’s Drive sharing rules, then will be converted automatically. Sharing of skills is not yet available. Keep the sheet in a document: it can be copied from one space to another in a minute.
What information should stay out of the sheet?
Your clients’ personal data, passwords, confidential figures and anything you would not want to see circulating. The sheet describes who you are and how you work, not your files. For sensitive data, the choice of tool and plan comes first.
Who should keep the sheet up to date?
A named person, with a quarterly review date. A sheet that still announces the old price or the old team produces wrong answers with great confidence, which is worse than no sheet at all.
Every working dayAR Digital / Daily AI
Get Daily AI every working day.
One piece of AI news, what it changes for your business and what to do, in your inbox in the morning. Free, no commitment.




