How I work

The firm owns its accounts, files, methods and records. AI tools sit on top and can be replaced without losing any of it.

01 · three layers

What gets set up

The foundation comes first. Everything above it depends on getting identity and permissions right.

The firm owns the middle layer. Tools above and below can be replaced.

02 · adding structure

Most useful AI work starts as one person's prompt. It moves up a step when it repeats, has clear value, and needs more control.

01
Personal
One person's instructions for their own work.
02
Shared skill
A tested version the team uses, with stated sources and a review step.
03
Firm workflow
Repeatable work with a named owner, records and handoffs.
04
Agent
A defined job with limited data, limited tools and a person who approves its output.

03 · build rules

A person approves
Anything that leaves the firm or changes a record waits for a named person to approve it.
1 · Evidence · Client-success build
Nothing is saved to the record until the user says so, and only the draft they were shown is saved.
Nothing is sent automatically
The first release of every workflow writes drafts. People decide what gets sent.
2 · Evidence · Client-success build
Follow-ups are drafts the user sends from their own email. The tools can't send.
Sources are named
Each output says where its facts came from, so a reviewer can check them.
3 · Evidence · Client-success build
Each fact in an answer says where it came from, such as "from your call notes".
Read-only first
New workflows start by reading. Write access comes after a test shows it is safe.
4 · Method · Engagement method
New workflows start by reading. Write access is added only after a test with the people who own the data shows it is safe.
Numbers come from code
Dates, totals and ratings are worked out by tested rules. The AI does not do the arithmetic.
5 · Evidence · Client-success build
Health ratings and business-day counts come from tested rules. The AI shows the result and never works it out.
Tested before release
Each workflow has written test cases, agreed with the person who owns the work.
6 · Evidence · Client-success build
Each skill ships with written test cases, including one where a pasted note tries to get the AI to send something.

04 · the first 90 days

01
Assess
How your firm works today, who does what, which systems hold what, and where AI could help most.
weeks 1 to 3
02
Set up
Accounts, permissions, file structure, security and records settings in the tools you already use.
weeks 2 to 8
03
Enable
Shared skills for meeting prep, follow-up, planning and documents in your own templates, with training for the people who use them.
weeks 3 to 12
04
First workflow
One priority workflow, read-only at first, checked by the person who owns the work.
weeks 4 to 12
05
Operate
Monthly support, improvements and a decision on what to build next.
after day 90

05 · your side