From chatbot
to digital worker.
Contents
Seven levels.
01Chat, delegate, build
02Like hiring someone
03The seven levels
04What it costs
05Level 1, talk
06Level 2, what it sees
07Level 2, Projects
08Level 2, the .md files
09Level 2, when it is wrong
10Level 3, Cowork
11Level 3, Dispatch
12Level 3, goals not prompts
13Level 3, the loop
14Level 4, connectors
15Level 4, skills
16Level 5, routines
17Level 6, Code and Design
18Level 7, ARMS
19Build it bottom up
20What should I use?
The mental model
Three ways to work.
Chat
You work with it
You are driving
Delegate
It works for you
You brief it and leave
Build
You build a system
It runs without asking
Start with chat. Graduate to delegation. Build when the task repeats.
The jargon, translated
It is the same as hiring someone.
01An office → the app
02A job description → instructions
03What they know → files and memory
04What they can do → skills
05Logins → connectors
06Weekly duties → routines
07Their manager → still you
The path
Nobody starts at seven.
1Talk
2Think
3Delegate
4Equip
5Systemise
6Build
7Scale
Most small businesses get everything they need from one to five.
Before you start
$33 a month.
Free$0
No Cowork at all
Pro$33 AUD
Everything in this deck
Max$165 AUD
Only if you run out
Billed in US dollars, so it moves with the rate. Add your ABN and the GST comes off.
Level 1Talk
Chat is for thinking together.
What it is
A conversation.
You are driving.
You are driving.
Why it matters
It is where you learn how to ask.
How you use it
Talk to it like a sharp colleague.
Level 2Think
It only knows what you put in front of it.
What it is
Everything it can see right now.
Why it matters
Generic output is missing context, not a weak model.
How you use it
Hand over the folder. Once.
Level 2Think
A Project is where that context lives.
What it is
A named space with your files in it.
Why it matters
You stop explaining yourself every day.
How you use it
One per client or job.
Start here If you do one thing from this deck, do this.
Level 2Think
What are all these .md files?
Instructions
How to work here.
Knowledge
What to know.
Output style
How to answer.
A .md is just a plain text file. Both of you can read it.
Level 2Think
It can be confidently, completely wrong.
What happens
It fills a gap rather than leaving one.
Why it matters
The tone is identical either way.
What to do
Give it the facts. Check every number.
Level 3Delegate
Cowork is where you hand the job over.
What it is
It works on its own, on real things.
Why it matters
You stop being the bottleneck.
How you use it
Describe the finished thing, not the first step.
Level 3Delegate
Dispatch sends work from your phone.
What it is
A job you fire off from anywhere.
Why it matters
Good ideas turn up away from your desk.
The catch
Your computer has to be awake.
Level 3Delegate
Prompting became goal setting.
wasPrompts
Instructions
nowGoals
Loops
nextSystems
Stop saying do this. Start saying here is what winning looks like.
Level 3Delegate
The good results are loops.
01Goal
02Plan
03Do it
04Check against the goal
05Improve, then check again
One pass is a first draft. Nobody writes their best version first time.
Level 4Equip
Connectors give it reach.
What it is
Permission to use one of your systems.
Why it matters
Advice becomes work done.
How you use it
Least access that does the job.
MCP The agreed way tools plug in. You do not need to do anything about it.
Level 4Equip
A skill is a job it knows how to do.
What it is
A text file of your instructions.
Why it matters
Same result in March and on Monday.
How you use it
Customize, then Skills.
name: weekly-posts
description: write a week of posts read the price list first seven posts, one carousel never invent a price
description: write a week of posts read the price list first seven posts, one carousel never invent a price
Level 5Systemise
If you say every Monday, build a routine.
What it is
A saved job on a timer.
Why it matters
The weekly jobs are the ones that slip.
How you use it
Automate the second time, never the first.
Level 6Build
Code builds it.
Design draws it.
onceThat is a chat
monthlyThat is delegation
alwaysThat is building
Most people never need this level. Nobody is failing if they stop at five.
Level 7Scale
ARMS. The four parts of an AI worker.
A
Applications
Where does the work happen?
Chat · Cowork · Code · Design · your phone · your systems
R
Routines
Does it happen again?
Scheduled tasks · the Monday brief · the monthly report
M
Memory
What does it need to know?
Your prices · your voice · your customers · your rules
S
Skills
What must it know how to do?
The jobs, written down once · and the tools to do them
Answer all four and you have described a worker, not a chat.
Level 7Scale
Build it bottom up.
Routinesput it on a timer
Skillsthe jobs it knows
Applicationswhat it can reach
Memorywhat it knows about you
start here
Each one only works if the one under it is done. Almost everybody starts at the top and wonders why it sounds like a robot.
Reference
What should I use?
Think it through → Chat
Get a job done → Cowork
Send it from your phone → Dispatch
Every week → Routine
Build a thing → Code
Make it look right → Design
Reach your systems → Connector
Teach it a job → Skill
Do not ask what
Claude can do.
Ask what you want done. Then decide: chat it, delegate it, or build it.