Free workshop

Build your company's context

Stop comparing models: they're converging and they change every three months. What decides the outcome in your company is everything else — what the AI knows about your trade, what it's allowed to do, and what it owes you back. You already have all of it: it lives in people's heads, in spreadsheets and in spoken habits. This workshop is the moment you write it down.

20 min for v1 · then 15 min a week

Free · no sign-up · prompts included

Before you start Set up your AI in 20 minutes

How we do it

  1. Decide where it lives

    Three requirements: any model can read it, your access rights already exist, and change history is kept. A SharePoint or shared Drive does the job. What doesn't: the hard drive of whoever looks after it.

  2. Write the briefing note

    A file the AI reads before touching anything. The test: what a bright intern should know about your company before day one. Who you are, what you sell, to whom, what must never be mixed up, how you write.

  3. Fill in a single domain

    The temptation is to cover everything. Don't. Take the one you know best, or the one costing you the most back-and-forth: product, support, purchasing, finance. Anything still fuzzy goes into a separate file: to be decided.

  4. Test it on a real task

    Not an exercise: a deliverable you'd have produced this week. With one non-negotiable requirement — it cites the file each piece of information came from. What you get is worth more than the deliverable: the list of what it couldn't find. That's the map of the knowledge written down nowhere.

  5. Set the weekly slot

    A context is never finished, it's maintained. With no fixed slot it goes stale in a month. 15 to 30 minutes a week, one owner per domain: what changed, what needs deciding, and the week's mistakes. Every wrong answer becomes a dated rule. That mistake doesn't come back.

The prompts, ready to copy

Prompt 1 · your company briefing note

Don't write it yourself: a hand-written note reads like a brochure, a note pulled out of an interrogation reads like your company.

We're going to write my company's briefing note: the document you'll re-read before every task, so you know whose house you're working in.

Interview me, one question at a time, for 5 minutes, covering:
1. What we do, for whom, and what sets us apart, in one sentence.
2. Our entities, brands or product lines: what must never be mixed up.
3. Our in-house vocabulary: the words we use and what they mean here.
4. How we write: the tone, what we never say.
5. What you never do without my approval.

Push back if my answer is vague, and don't move to the next question before you've understood.

Then write the note: short, dense, structured, ready to drop into the folder. Add at the end a section “Rules for any AI working here” with these three, plus any that come out of my answers:
1. Never invent a figure, a name or a reference. When in doubt, write [to check] and flag it to me.
2. Prepare drafts, send nothing.
3. Delete nothing.

Show me the document before you write it into the folder.

Prompt 2 · your first domain

Fifteen minutes of interview on one domain yields more useful context than any shared folder in your company.

We're going to write the knowledge base for one domain of my company: [product, support, purchasing, finance].

Interview me for 15 minutes, one question at a time, covering:
1. The end-to-end process: who does what, in what order, with what tool.
2. The rules that aren't up for debate, and why they exist.
3. The figures and thresholds we work with: prices, lead times, margins, limits.
4. The domain vocabulary: what each term means here, not in general.
5. What's stuck today, and what people do to work around it.

When my answer is vague, ask me for a real example rather than a generality.

At the end, write the domain document, structured and ready to file. And in a separate file, “to-decide”, list everything that stayed ambiguous, with the exact question to settle and who should answer it. Don't fill those gaps in yourself.

The three mistakes that ruin it

  • Trying to cover everything One domain written properly beats six half-done. The second comes once the first is actually being used.
  • Keeping it on someone's drive The day that person leaves, the context leaves with them. It lives where your access rights already live.
  • Writing it and never returning Without the weekly slot it goes stale in a month: files age, answers drift, the team disengages.

This document concentrates what your company knows: treat it like your accounts. Rights per domain, no personal data about customers or staff inside, and a named owner for each part.

All workshops

Set up your AI in 20 minutes

The first move: give it your context once.

20 min · once · no technical skillsOpen the workshop

1:1s that prepare themselves

Everything gets transcribed, an agent files it, your check-ins prepare themselves.

20 min to set up · then 2 min before each check-inOpen the workshop

Emails written in your voice

It learns your style from your sent mail, and drafts your replies.

20 min for the style · 10 more for the automationOpen the workshop

Would you rather we did it with you?

These workshops are the starting point. On client work we do the same thing at company scale: your company's context written down properly, the processes automated, and your teams trained while we build.

Request your audit

30 minutes · no commitment