Decision Deployment · for businesses of 15 to 49 people
Every month we bring you what moved and what stalled, and you make the calls.
Each month we bring you a Deployment Brief and work through it with you in a 60 to 90 minute decision session. Whatever you approve is written back into the brain everyone reads.
It runs on the Context Install and the Context Layer, which have to be live first. From 50 people, the Decision Layer runs it with your executive team, department by department.
What changed in September
Prepared for the owner of a 24-person advice practice. An example.
- What moved
- Fee consent forms now go out 30 days before they fall due for 9 of 14 advisers.
- What stalled
- The switch to new planning software has waited on the licensee’s sign-off for 3 weeks.
- Pulling against each other
- 2 advisers book the same paraplanner every Thursday morning.
- Unactioned past 30 days
- A client asked on 20 August for a review of their partner’s super and has had no reply.
- Changed financially
- 41 reviews invoiced in September, up from 33 in August.
- Aug33Sep41
- What competitors actually did
- A practice nearby started offering evening appointments.
- Source: their website, 16 September.
An example Deployment Brief for a 24-person advice practice. Each month the owner works through it in a 60 to 90 minute decision session. The practice, roles, numbers and dates are illustrative.
Decision Deployment reads the business as one unit, with the owner in the room.
Decision Deployment and the Decision Layer both run on the brain. What changes between them is who sits in the room and how far into the business each one reads.
Decision Deployment
This page- Who’s in the loop
- The owner and a handful of seniors.
- Rhythm
- A monthly brief and decision session, with a quarterly review.
- What’s observed
- The business as one unit.
Decision Layer
- Who’s in the loop
- The executive team, department by department.
- Rhythm
- Weekly signals, with a monthly pack and a quarterly board review for the executive team.
- What’s observed
- Each department, with its own owner and metrics.
You give a half day in month 1, then 60 to 90 minutes each month.
Decision Deployment opens with a half-day priority session and a written baseline in month 1. After that, each month has one decision session, and the preparation and the write-back sit with us.
One year of Decision Deployment, from July to June. Dates are illustrative.
The rhythm
- 1. Month 1, the priority session
A half day with you and up to 5 of your seniors on what the business is moving, which decisions matter, who owns what, what success looks like and what would make you stop.
- 2. Month 1, the baseline
The 3 to 5 numbers the year is measured against, written down and dated.
- 3. Every month, the brief
We read the brain and your systems, read-only, and bring you what moved, what stalled, where two people are pulling against each other, what’s waiting on you, what has gone unactioned past 30 days, what changed financially and what competitors actually did.
- 4. Every month, the decision session
60 to 90 minutes with you. You make the calls on the brief, and each one gets an owner and a date.
- 5. When a call is approved
We write it into the brain as updated context, workflows, instructions and skills, and the record names who approved it and when.
Who we need
- You, for the half day in month 1 and every session after it. Up to 5 of your seniors join you for the half day.
- Whoever holds admin access to your systems, to connect them read-only in month 1.
What we do on our side
- In month 1: read-only connections to your calendar, CRM, ledger, project tool and shared inboxes, and to your own inbox if you say yes. The baseline is written down and dated.
- Before each session: the brief, prepared from the brain and your systems.
- After each session: every approved call written into the brain, with its owner and date.
- Before each quarterly review: the funded list set against the baseline, in a pack you can hand to your accountant or your board.
Approved calls land in the files everyone reads, with who said yes and when.
The decision record and the files it changed sit in the brain everyone reads, in your own storage. Nothing that shapes how your team’s Claude answers changes until someone with authority approves it.
Decision record
Paraplanner time is booked through one shared calendar
Approved 13 October by the principal
- From
- October decision session
- Owner
- Practice manager, by 30 October
- Written into
- processes/paraplanner-bookings.md, templates/booking-request.md
- Reaches
- 24 people
Decision record
Paraplanner time is booked through one shared calendar
Approved 13 October by the principal
- From
- October decision session
- Owner
- Practice manager, by 30 October
- Written into
- processes/paraplanner-bookings.md, templates/booking-request.md
- Reaches
- 24 people
What changed in the brain
The same call, as it landed in the files.
- processes/paraplanner-bookings.mdUpdated 13 October
Updated 13 October
Bookings move from direct requests to one shared calendar
- templates/booking-request.mdUpdated 13 October
Updated 13 October
A new request form for paraplanner time
Each month’s brief and each quarter’s pack come to you as well.
The same example practice. File names, roles, dates and counts are illustrative.
Each quarter, every initiative is marked fix, fund, scale or stop.
We set the funded list against the baseline written in month 1. The pack shows each initiative’s mark beside its owner, ready to hand to your accountant or your board.
The numbers stay the ones written down in month 1, so each quarter is judged on the same terms as the first.
The first quarter against the baseline
Reviewed on 13 October with the principal of a 24-person advice practice. An example.
Baseline, written 14 July
| At the start | Now | |
|---|---|---|
| Reviews invoiced a month | 31 | 41 |
| Fee consent forms sent before they fall due | 6 in 10 | 9 in 10 |
| Days from first meeting to advice presented | 34 | 29 |
Initiatives
- Fee consent forms sent 30 days earlyPractice managerScale
- New planning softwarePrincipalFix
- One shared paraplanner calendarPractice managerFund
- Client newsletter drafted in ClaudeSenior adviserStop
An example quarterly pack from the same practice. Numbers, roles and dates are illustrative.
The first quarter against the baseline
Reviewed on 13 October with the principal of a 24-person advice practice. An example.
Baseline, written 14 July
| At the start | Now | |
|---|---|---|
| Reviews invoiced a month | 31 | 41 |
| Fee consent forms sent before they fall due | 6 in 10 | 9 in 10 |
| Days from first meeting to advice presented | 34 | 29 |
Initiatives
- Fee consent forms sent 30 days earlyPractice managerScale
- New planning softwarePrincipalFix
- One shared paraplanner calendarPractice managerFund
- Client newsletter drafted in ClaudeSenior adviserStop
An example quarterly pack from the same practice. Numbers, roles and dates are illustrative.
AI is real when it’s live in a workflow with an owner and a measure.
Decision Deployment needs the install and the Context Layer live first.
The brief reads the brain alongside your systems, and every approved call is written back into it. If you take the Decision Discipline Workshop first, its calls run in months 1 to 3, and Decision Deployment starts in month 4 without the priority session.
- 1. Context Install
- 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 LayerThis page
- 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.
The fee is per business, per month, for 12 months.
Decision Deployment sits on top of the Context Install and the Context Layer, and each keeps its own price. You get your number on the call.
- Decision Deployment
- Per business, per month
- Term
- 12 months
- Context Layer
- Per person, per month
- Context Install, shared brain
- Once per business
- Context Install, each person’s setup
- Per person by role, once
Automations beyond the write-back, and a connector for any system that has none, are quoted separately.
Questions owners ask about Decision Deployment
You give a half day in month 1, with up to 5 of your seniors. After that, it’s a 60 to 90 minute decision session each month and the quarterly review, and the brief and the write-back sit with us.
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 what would need to be in place before Decision Deployment could start.