Free workshop

Set up your AI in 20 minutes

You open ChatGPT, you ask a question, the answer is flat. It isn't that the AI is stupid: it knows nothing about your company, your rules or your decisions, so it fills the gaps with generic filler. The fix is to give it that context once, in a document it re-reads before every task.

20 min · once · no technical skills

Free · no sign-up · prompts included

How we do it

  1. Open a dedicated space

    A ChatGPT project, a Claude space. The point: a stable place where your context lives, instead of a throwaway conversation.

  2. Have it write your global instructions

    It's the field the AI keeps in mind across every conversation. Don't write it yourself: paste the first prompt, let it interview you for five minutes, and it writes the short version.

  3. One context file per project

    Global instructions say who you are. Each project deserves its own on top: a document with the goal, where it stands, who decides and what is already settled. That's the second prompt.

  4. Connect your tools

    Calendar, email, files. It stops guessing and starts reading what actually happens in your company. Permissions at a minimum: read yes, send only after you approve.

  5. Test by dictating, not typing

    Speaking is roughly three times faster than typing. Give it a real task and see whether it answers in your voice. If it rings false, fix the context, not the answer.

The prompts, ready to copy

Prompt 1 · your global instructions

Paste it into your AI. Answer its questions and copy the result into the instructions field in settings.

You're going to help me fill in my global instructions: the text you keep in mind across all our conversations.

Interview me, one question at a time, for 5 minutes, covering:
1. Who I am: my name, my role, my company, what it does, one sentence each.
2. Who I talk to: my customers, my market, what they expect from me.
3. My writing rules: tone, length, the words I use, the ones I never say.
4. My working preferences: output formats, language, what you must always check before answering.

Ask the questions one by one, and push back if my answer is vague.

At the end, write a SHORT, dense text in the first person, ready to paste: every sentence must earn its place, cut anything decorative. Deliver a finished text, nothing left to touch up.

Prompt 2 · a project's context

Paste it whenever you open a project. The result lives in the project, next to two or three reference documents.

I'm opening a new project: [project name]. Before we start, we're writing its context: what you'll re-read before every task on this project.

Interview me, one question at a time, for 5 minutes, covering:
1. The goal: what must exist at the end, and for whom.
2. Where it stands: what's done, what's blocked, the next step.
3. The people: who decides, who does the work, who must be kept informed.
4. The decisions already made on this project, which we don't reopen.
5. What I call good work here: ask me for a concrete example.

At the end, write a one-page document, structured, in the first person, and list at the bottom the 2 or 3 reference documents I should drop in beside it. Finished document, ready to paste.

The three mistakes that ruin it

  • Vague context “Be professional” tells it nothing. Be specific: “answer in five lines, stay formal, no jargon”.
  • The forty-page dump Too much context drowns it as surely as too little. One dense page beats an unreadable folder.
  • No examples With no model of what you call good work, it invents its own. Paste two or three.

Connecting your tools gives it access to your email, calendar and files. Four habits: a work account approved by your company, connectors kept to the strict minimum, fine-grained permissions (read yes, send only after you approve), and no client names or sensitive figures in the context. What's useful is how you work, not your confidential data.

All workshops

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

Your company context, written down

What the AI needs to know about your company, written once and maintained.

20 min for v1 · then 15 min a weekOpen 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