Context Layer · per person, each month
The Context Layer keeps
the brain current, so no one
works from old facts.
Every person gets a monthly note and a 1-hour review with us each quarter, and leaves each review with one new skill or scheduled task. Over the year, each person learns to build and run their own workflows. In between, a daily check in each person’s own account flags anything that contradicts the brain.
Every person gets a monthly note and a
1-hour review with us each quarter.
It runs for everyone the Context Install set up, and it’s billed monthly.
What changed in October
Prepared for a senior adviser at a 12-person advice practice. An example.
- What moved
- Client reviews now run as 2 meetings, and the review letter changed with them on 9 October.
- What stalled
- A client’s review pack has waited on the paraplanner since 13 October.
- Unactioned past 30 days
- The accountant’s referral from 18 August still has no reply.
What changed in October
Prepared for a senior adviser at a 12-person advice practice. An example.
- What moved
- Client reviews now run as 2 meetings, and the review letter changed with them on 9 October.
- What stalled
- A client’s review pack has waited on the paraplanner since 13 October.
- Unactioned past 30 days
- The accountant’s referral from 18 August still has no reply.
An example monthly note for one person at the same 12-person advice practice as the homepage. Everything in it is illustrative.
Each person gives a few minutes a week and 1 hour each quarter, and we prepare the rest.
The checks run on a schedule and bring what they find to the person who decides. Nothing that shapes how your team’s Claude answers changes until someone with authority approves it.
On a schedule
- Every day
- A check in each person’s own account, set up at the install, picks up decisions and project changes, and flags anything that contradicts the brain. What it finds waits for that person’s yes.
- Every week
- A tidy-up pass over the shared brain leaves each team’s leader a short report and a few suggestions to clear.
- Every month
- Every person gets a note on what moved, what stalled, what’s waiting on that person and what has gone unactioned past 30 days.
- Every person gets a note on what moved, what stalled, what’s waiting on that person and what has gone unactioned past
30 days. - Every quarter
- Each person has 1 hour with us to clear what’s waiting and fix what drifted. The report card comes out of that review. Each person also leaves with one new skill or scheduled task, using the tools you already have connected.
Who we need
- Each person, for a yes or no on their own suggestions: about 2 minutes, once or twice a week.
- Each team’s leader, to clear their team’s shared suggestions each week. Anything that crosses teams goes up the chain of command.
- Each person, for 1 hour a quarter. They bring what Claude got wrong that they never reported, and what they still find themselves re-explaining.Each person, for 1 hour a quarter. They bring what Claude got wrong that they never reported, and what they still find themselves
re-explaining. - The owner, to go through the report card with us each quarter.
What we do on our side
- Before each review: a drift check across the whole brain.
- Each quarter: the report card, built from your own files.
- At each review: any file corrected 3 times in the quarter rewritten, and every skill and scheduled check confirmed as still running.
- Between reviews: new skills as we release them.
When two people want different things in the same file, the leader over both decides.
The daily check holds both changes, and nothing in the file moves. The leader who manages both people decides. If they sit in different teams, it goes up the chain of command until it reaches someone who manages both. Their decision goes into the file with their name and the date.
Two suggestions, one file
Client reviews run as 2 meetings
Decided 9 October by the practice manager, who manages both
- Suggested by
- Lee, adviser: 2 meetings. Ana, paraplanner: 1 meeting, with the pack sent first.
- Held
- Both changes waited. Nothing in the file moved until the decision.
- Goes to
- The leader who manages both. In different teams, up the chain to the leader over both.
- Written into
- processes/client-review.md, templates/review-letter.md
- Reaches
- 12 people
Two suggestions, one file
Client reviews run as 2 meetings
Decided 9 October by the practice manager, who manages both
- Suggested by
- Lee, adviser: 2 meetings. Ana, paraplanner: 1 meeting, with the pack sent first.
- Held
- Both changes waited. Nothing in the file moved until the decision.
- Goes to
- The leader who manages both. In different teams, up the chain to the leader over both.
- Written into
- processes/client-review.md, templates/review-letter.md
- Reaches
- 12 people
What changed in the brain
The decision, as it landed in the files.
- processes/client-review.mdUpdated 9 October
Updated 9 October
Client reviews run as 2 meetings. Decided by the practice manager.
- templates/review-letter.mdUpdated 9 October
Updated 9 October
The review letter changes with the 2 meetings.
An example from the same 12-person advice practice as the homepage. Names, roles and dates are illustrative.
Every automation without a name on it
is a bill waiting to land.
Every automation without
a name on it is a bill
waiting to land.
Each quarter, the report card checks every person against the target of 5 hours saved a week.
The target is 5 hours saved per person, per week, counted on the tasks written down at the install. The report card shows whether you reached it, with every input beside the result.
Each person’s row shows their status, with the date of their last update beside it. Everyone sees what the card says about them.
Every number comes from your own files or from a figure you confirmed at the review. Suggested moves sit in a panel of their own and change no number.
Northwind Advice, Q3 2026
Quarter to date, 1 Jul to 22 Sep. The business brain and 4 people, measured against the baseline signed on 30 June: 6 named tasks, estimated the same way both times.
- Client
- Northwind Advice
- Period
- Q3 2026, to 22 Sep
- Exported
- 22 Sep 2026
- File
- pulse-NWA-2026-Q3.json
Where each person stands
| Person | Status | Last dated entry | Hours a week |
|---|---|---|---|
| SamPrincipal | Healthy | 1 day ago | 5.5 h |
| LeeAdviser | Healthy | 4 days ago | 5.2 h |
| AnaParaplanner | Watch | Today | 3.4 h |
| RajOffshore admin | Quiet | 26 days ago | 0 h |
What the numbers suggest
Check Raj’s capture before anything else
Last dated entry 27 Aug, 26 days ago, past the 21-day quiet line.
Suggested move: book 15 minutes with Raj. The laptop is personal, so Raj makes the fix with you on the call.
A quarterly report card, shown with sample data. Northwind Advice is fictional. Each quarter adds a card to the series.
Northwind Advice, Q3 2026
Quarter to date, 1 Jul to 22 Sep. The business brain and 4 people, measured against the baseline signed on 30 June: 6 named tasks, estimated the same way both times.
Where each person stands
| Person | StatusLast dated entry | Hours a week |
|---|---|---|
| SamPrincipal | Healthy1 day ago | 5.5 h |
| LeeAdviser | Healthy4 days ago | 5.2 h |
| AnaParaplanner | WatchToday | 3.4 h |
| RajOffshore admin | Quiet26 days ago | 0 h |
What the numbers suggest
Check Raj’s capture before anything else
Last dated entry 27 Aug, 26 days ago, past the 21-day quiet line.
Suggested move: book 15 minutes with Raj. The laptop is personal, so Raj makes the fix with you on the call.
A quarterly report card, shown with sample data. Northwind Advice is fictional. Each quarter adds a card to the series.
You pay per person, each month, and the quarterly review sits inside that fee.
Everyone the Context Install set up is billed monthly for the Context Layer. The install and the other products are each priced on their own. Your quote comes from your headcount, which we work out with you on the call.
- Context Layer
- Per person, per month
- People counted
- Everyone the Context Install set up
- The quarterly review
- Inside the monthly fee
- Billing
- Monthly
Every approved change goes into your own storage, dated, with who said yes.
Each month adds a note for every person, and each quarter adds a report card to the series. Anyone with access can open the brain’s files and see what changed, and when. The notes, report cards and approved changes are yours, like the files the install wrote.
The shared brain, end of October
Each file carries its last approval, with who gave it and when.
- processes/client-review.md
Approved 9 October by the practice manager
- templates/review-letter.md
Approved 9 October by the practice manager
- templates/fee-schedule.md
Approved 14 October by the practice manager
- policies/hard-rules.md
Stamped by the principal at the install
The senior adviser’s notes
A note a month, newest first.
- October 2026What changed in October
What changed in October
- September 2026What changed in September
What changed in September
- August 2026What changed in August
What changed in August
- July 2026What changed in July
What changed in July
The same example practice. File names, roles and dates are illustrative.
Everyone installed counts as one, leader or frontline.
Leaders and managers are priced differently from frontline staff at the install. On the Context Layer everyone counts as one. When someone joins, they’re installed first and joins the Context Layer from there.
Leaders and managers
5 of 12- Principal
- Practice managerClears their team’s suggestions
- Senior adviser × 3
5 notes a month and 5 reviews a quarter
Frontline staff
7 of 12- Paraplanner × 4
- Admin × 3
7 notes a month and 7 reviews a quarter
The same 12-person practice as the homepage: 12 people, so 12 notes a month and 12 reviews a quarter. Roles and counts are illustrative.
Questions owners ask
about the Context Layer
In each person’s own account, on their own computer, where it looks over that day’s Cowork sessions. What it picks up waits in their own suggestion inbox for a yes or no, and we go through anything still waiting with them at their quarterly review. Chats on claude.ai or a phone sit outside it.
Under 15, your team runs it. From 15, we can run the loop with you.
Decision Deployment and the Decision Layer both read the brain the Context Layer keeps current, and neither starts until it’s live.
- 1. Context Install
- Builds the brain and each person’s Claude, and is always the first build.
- 2. Context LayerThis page
- 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 how many people your Context Layer would cover.