Free toolkit

Your team briefs AI from zero every single time.

The Organisational Brain Toolkit is a folder structure, eight file templates and a capture method, so the context your business runs on is written down once and used by everyone. Not a database project. About an hour to start.

Get the toolkit → See what is inside

8 file templates 1 hour to a working set 65 minutes to capture an expert Claude and Copilot checklists

The idea

Every new chat starts from zero.

The fix is not a data project and it is not a new tool. It is about eight plain documents, written once, pointed at the AI your team already has. The prompt lives for one message. The conversation dies with the tab. What survives is the knowledge layer underneath, and almost nobody is building it.

That is the difference between AI being useful to whoever writes the best prompt, and AI being useful to your whole team.

LAYER 1

The prompt.

Lives one message. Gone the moment you send the next one.

LAYER 2

The conversation.

Dies with the tab. Nobody else in the business ever sees it.

LAYER 3

Project knowledge.

Every chat starts briefed. This is where the value is, and where the work goes.

LAYER 4

Grounded org knowledge.

Live sources, cited answers, permissions apply.

What is inside

Three kits, one download.

Everything from the session, in the form you would actually use it.

The Starter Memory Pack.

Eight templates covering the minimum context an AI tool needs to be useful to the whole team.

Company profile
Tone and voice
Offers and pricing
Clients and ideal client profile
Standards and definition of done
Glossary and naming
Project instructions
Knowledge base rules

The Expert Capture Kit.

The 65 minute method for getting a process out of somebody's head and into a document a new starter could follow.

The capture method, start to finish
The transcript to SOP prompts
The four questions to ask at each decision point

Setup Checklists.

Standing it up in the tools you already pay for, with the limits that actually bite.

Claude Projects
Copilot notebooks with SharePoint
File size and retrieval thresholds

The method

Seven rules, and your first hour.

Seven rules for every file.

One topic per file. If the title needs an "and", split it.
One to three pages. Tight beats long.
Headings that describe content, because retrieval splits on heading structure.
Plain text, Markdown or clean Word. No decorative tables.
No scans, and no screenshots carrying meaning. An agent cannot read them.
A header block on every file: owner, last reviewed, review by, status.
Consistent naming. Dates and versions live in the header, not the filename.

Your first hour.

Time	File
10 min	Company profile
10 min	Tone and voice
10 min	Offers and pricing
10 min	Clients and ideal client profile
5 min	Standards and definition of done
5 min	Glossary and naming
5 min	Project instructions
5 min	Knowledge base rules

Dictate for two minutes each and let AI structure it. You are editing, not authoring.

Before you start

The five ways this fails.

Boiling the ocean instead of writing eight files this week.

Dumping the whole shared drive in, which buries the good material.

No owner and no review date, so it quietly rots.

Grounding an agent on a site nobody has run a permissions review over.

Treating it as an IT project when the knowledge owners should write it.

Get the toolkit

Send it to me.

Tell us where to send it and the download starts on the next page. The templates are yours to edit, rename and put to work.