Context Install · the first thing we build
The Context Install writes
your business down once,
for everyone’s Claude to read.
It interviews each person for 90 minutes and builds your AI Business Brain from what they know. Then it sets up each person’s Claude so every chat starts from the brain.
It interviews each person for 90 minutes
and builds your AI Business Brain from
what they know.
It sits in your files, under your own accounts. The install is the first thing we build, whatever the size of the business.
From 50 people, we usually start with the Decision Discipline Workshop.
It sits in your files, under your own accounts. The install is the first thing we build, whatever the size of the business. From 50 people, we usually start with the Decision Discipline Workshop.
Context Install · 12-person advice practice
7 of 12 people written and tested
The shared brain
- processes/9 files
- policies/4 fileshard-rules.md
Waiting on the principal’s yes - decisions/2 files
- templates/14 files
- skills/2 files
- objections/6 files
People
- PrincipalLeaderWritten and tested
- Practice managerLeaderWritten and tested
- Senior adviserLeaderWritten and tested
- Senior adviserLeaderWritten and tested
- Senior adviserLeaderIn session
- Paraplanner × 3Front-lineWritten and tested
- ParaplannerFront-lineBooked
- Admin × 3Front-lineBooked
Brand-new chat · practice manager’s laptop · 10:42
What do you know about me, and how do I like work delivered?
You’re the practice manager. You own the client review calendar and you approve changes to the practice’s processes and templates. You want the answer first, with one line of reasoning, and anything wrong in a client document flagged to you before it’s changed.
Passed: answered from the files, in the person’s own terms.
Context Install · 12-person advice practice
7 of 12 people written and tested
People
- PrincipalLeaderWritten and tested
- Practice managerLeaderWritten and tested
- Senior adviserLeaderWritten and tested
- Senior adviserLeaderWritten and tested
- Senior adviserLeaderIn session
- Paraplanner × 3Front-lineWritten and tested
- ParaplannerFront-lineBooked
- Admin × 3Front-lineBooked
Brand-new chat · practice manager’s laptop · 10:42
What do you know about me, and how do I like work delivered?
You’re the practice manager. You own the client review calendar and you approve changes to the practice’s processes and templates. You want the answer first, with one line of reasoning, and anything wrong in a client document flagged to you before it’s changed.
Passed: answered from the files, in the person’s own terms.
An example install for a 12-person advice practice. File names, roles, counts and times are illustrative.
Your team gives 90 minutes each. The preparation and checking are ours.
Each session is an interview, one question at a time, and Claude writes the files in the person’s own words.
Their files, writtenin the sessionTheir files, written in the sessionWhat they can
approve aloneWhat they can approve alone
In the session
- 1. How they work
What they do, what gets sent back, what they can approve, and what their Claude must never do.
- 2. Who and what they deal with
The people they deal with most and the work that’s live, with a file for each.
- 3. Reading it back
They hear what was written and correct it in their own words.
- 4. The test
A brand-new chat on their own computer and login has to answer “What do you know about me, and how do I like work delivered?” from the files. A generic answer means something isn’t loading, and we fix it before anyone stands up.
- 5. The habit
They keep a one-page letter and one sentence: “Add that to my context files.” Each correction is written in once, so the mistake doesn’t come back, and their Claude gets more useful every week they use it.
Who we need
- Each person, for their own session, at their own computer.
- The owner and whoever will look after the brain, together, for up to an hour to build the shared part.
- Whoever holds your admin login, or your IT provider, to set folder permissions before the first session.
- Whoever keeps your HR files, for each person’s job description if there is one, so their files start from what the role covers.
- At a licensed practice, whoever carries the licence, to agree in writing what client information may go in.
What we do on our side
- Before the first session: the folder structure built and the permissions tested by us.Before the first session: the folders built and the permissions tested by us.
- After each session: every file checked for anything missing or broken, and the person’s known gaps written down and dated.
- At the end of each day: everyone’s setup checked again, and anything the day left open closed before we leave.
- About 2 weeks later: a check-in with each person, where their setup is tested again and what Claude got wrong in the meantime is written in. The install is complete when that call has run cleanly.
One honest page about your business beats a folder of clever prompts.
Once the install is paid in full, the files are yours and stay when people leave.
The install writes one shared brain for the business and one folder for each person’s Claude, in your own storage. They’re ordinary files for use inside the business, and anyone with access can open one and read it. We keep the rights to the method and templates they’re built from.
The shared brain
Built once per business and read by everyone.
- processes/client-review.md
How the practice does things
- policies/hard-rules.md
The hard rules everyone’s Claude follows
- decisions/brain-maintainer.md
What was decided, with the owner and the date
- templates/review-letter.md
The documents the practice produces again and again
- skills/review-pack.md
Jobs Claude runs on request or on a schedule
- objections/fees.md
What clients push back on, and what you say
One person’s Claude: practice-manager/
Set up once per person and read at the start of every chat.
- CLAUDE.md and about-me/Memory layer
How they work and write, and what their Claude must never do
- people/People
One file for each person they deal with most
- projects/Projects
One file for each piece of live work,
with who owns it and where it’s up to - entities.mdEntities
The business’s entities, and which one invoices
- documents.mdDocuments
Where their documents already live, so Claude reads them in place
- templatesTemplates
Read from the shared brain
The same example practice. File names and roles are illustrative.
Each person’s Claude reaches only what their role allows.
Everyone reads the same brain and works within their own authority. What each person’s Claude can reach follows what they’re responsible for, whatever their title. Each person’s own folder is private to them, plus whoever your business names at the install.
Leaders and managers
In an advice practice, usually the owner, partners, the practice manager and senior advisers.
practice-manager/access.md
Leaders and managers- Can reach
- The shared brain, mail, calendar, the CRM and the ledger.
- Needs me driving
- Payments, and anything signed.
- What I can approve alone
- Changes to the practice’s processes and templates.
Frontline staff
In an advice practice, usually paraplanners and admin.
paraplanner/access.md
Frontline staff- Can reach
- The shared brain, and client files by assignment.
- Needs me driving
- Anything sent to a client, and anything that needs signing.
- What I can approve alone
- My own drafts and file notes.
A leader’s file and a frontline staff member’s file from the example practice. Everything in both files is illustrative.
You pay for the brain once, then for each person by their role.You pay for the brain once,
then for each person
by what it carries.
The brain is built once per business. Each person is priced once, as a leader or manager, or as frontline staff. The Context Layer then runs per person, per month, with a quarterly review for each. We work out who’s included with you on the call, and your quote comes from it.
- The shared brain
- Once per business
- Leaders and managers
- Per person, once
- Frontline staff
- Per person, once
- Context Layer quarterly reviews
- Per person, per month
Questions owners ask
about the install
Your files stay where they are, and the brain points at them in place. If you want a drive reorganised, that’s its own job, quoted separately.
The Context Layer keeps the brain current after the install.
It runs per person, each month. Every person gets a monthly note, and each quarter a report card shows the hours saved and where the brain still has gaps.
- 1. Context InstallThis page
- Builds the brain and each person’s Claude, and is always the first build.
- 2. Context Layer
- Keeps the brain current, and has to be live before Decision Deployment or the Decision Layer can start.
- 3. Decision Discipline Workshop
- An optional add-on at any size, on its own or beside the install.
One room of 5 to 15 people who can fund a decision and kill one. - 4. Decision Deployment or the Decision Layer
- We run the loop with the owner from 15 people, or with the executive team from 50.
The loop that runs on the brain, and what we read while it runs, is set out step by step on How it works.
The loop that runs on the brain, and what we read while it runs, is set out step by step on
How it works.
Book a call with Joel
Joel and the MethodWorks team put AI into the daily work of Australian businesses in financial advice, retail, logistics, education and software. Bring your headcount and the AI tools your team uses today, and you’ll leave the call knowing who your Context Install would cover.