Why Leave
the Fieldand where your work actually lives
You have been riding in an open field, carrying everything the horse needs out to it by hand. There is a building for this, and today we walk up to the door.
By the end of today you will know why the chat window has a ceiling, what a project folder is, and you will have one of your own with real work in it.
Presented by Emile du Toit
brainitconsulting.com
You can follow all of today without them. Here is where we got to.
- The horse is the model. It predicts the next word, knows nothing about your business, and remembers nothing between conversations.
- The saddle is standing instructions — written once, sent with every message.
- The saddlebags are tools: the things that let it read a price list or put a draft somewhere, instead of only talking.
- The loop is look, decide, act, check, repeat — and you set the goal and the stopping point.
All of that has happened in a browser tab so far. Today we find out what that is costing you.
Contents
- Before you startWhat you need from #001 and #002, and nothing to install.
- Fifteen minutes that won't make sense yetWatch first. Understand afterwards.
- The ceiling in the chat windowWhy you are the one doing the carrying.
- Files and folders, plainlyThe least horse-like chapter in the series.
- One folder, one jobThe idea that keeps you safe later.
Then the questions this always raises, the glossary so far, and one small thing to do before next time.
Before you start
- Workshops #001 and #002 done. An account, standing instructions in a project, and one weekly task you wrote down.
- Your own computer — a real one, not a phone. You are going to make folders on it.
- Ten minutes of your actual files. Wherever the work for one job currently lives: email attachments, the desktop, a Documents folder, a shared drive.
Still nothing to install. Today needs File Explorer on Windows, or Finder on a Mac, and the browser tab you already have. The editor arrives in #004; the setup page lists what comes when.
Fifteen minutes that won't make sense yet
See where this is going first. We take it apart afterwards.
We are going to start at the wrong end on purpose. For the next few minutes you are going to read about something being built, and quite a lot of it will not make sense yet. That is fine. It is meant to.
Dale runs the two-truck plumbing company from the last session. He has a rate card, a folder of past estimates, and a stack of inquiry emails. In a moment you will read exactly what an assistant did with all of that, and how it produced a finished estimate — not a draft in a chat window that somebody has to copy out, but a file, sitting in Dale's folder, ready to send.
Nothing to install for this chapter, and nothing to type yet. Read it, and when something makes you think "hang on, how did it know that?" — write the question down. Every one of them gets answered before the end, and you build the thing yourself in workshop #005.
- Nobody pastes anything. No copying the rate card in, no copying the answer out.
- It opens things by itself. It goes and reads the rate card because it decided it needed the rate card.
- The result is a file. Not a message on a screen. A thing on Dale's computer with a name, that is still there tomorrow.
- It asks before it acts. Watch how often it stops and waits for a yes.
All of that happened inside a room you have not been in yet. Not a website, not a chat window — a folder on an ordinary computer, with the tack hanging on the wall. The rest of this session is a tour of that room.
The six steps behind it — nothing up anyone’s sleeve read only
Worth reading for the mechanics rather than the magic. There are six steps and one instruction — and these are the same six steps you run yourself in workshop #005, on your own folder. Nothing is hidden.
- Start from one known folder. Dale's holds a rate card, his notes, one past estimate, and three unopened emails. Nothing else is in it.
- Open that one folder in the editor — File → Open Folder. Nothing else on that laptop is in reach. Installing the editor and opening a folder in it is all of workshop #004.
- Make the text big enough to read comfortably.
- Open the assistant panel down the right-hand side. That is the same conversation you have been having in a browser since #001, now sitting inside Dale's folder.
- Give it one instruction — the one below, pasted in rather than typed.
- Say yes when it asks permission to write a file, and then open what it wrote.
The instruction, in full:
Dale’s folder, file by file — copy these and you can run it yourself
That instruction names six files. Here they all are. Nothing to download — copy each one and save it under the name in its heading.
You cannot run this today, and that is fine. You have no editor until #004 and no assistant in the folder until #005. Keep this page open when you get there. Some people would rather practise on somebody else’s business than their own, and Dale is here for exactly that.
The folder, as it should look
notes.txt
rate-card.txt
inbox/alvarez.txt
inbox/whitfield.txt
inbox/rasmussen.txt
past-estimates/smith-kitchen.txt
This is the one that does the most work. It is not instructions — it is an example, and the assistant copies its shape without being told what the shape is.
Read the three emails against the rules before you read what the assistant made of them. Marisol is straightforward. Ken lands on a Saturday, so the labor goes up and the service call does not. Dee wants gas work, which Dale does not touch — a good answer refuses that line, prices her slow drain, and says so plainly. If you know the right answer before you ask, you can tell whether you got it.
Copy it, click into the assistant's box, and press Ctrl + V on Windows or Cmd + V on a Mac. If the shortcut doesn't take, right-click — that pastes too.
Worth knowing generally: long instructions are normal and expected. Write them somewhere comfortable, then paste them in.
That is everything. No hidden setup and no special version — and the same six steps are how you will do it on your own machine, two workshops from now.
Last time we rode in a field. Today we find out there was a stable all along.
The ceiling in the chat window
Nothing wrong with the field. But out there, you are the courier.
Think about how you actually used a chatbot after the last session. You had something on your screen. You selected it, copied it, went to another tab, pasted it in, typed what you wanted, waited, read the answer, copied that, went back, pasted it where it needed to go. Then the next email arrived and you did it all again.
That works. Thousands of businesses run on exactly that, and if it is saving you an hour a week, keep doing it. But notice who is doing the fetching and carrying. The horse is standing in a field. Every single thing it needs to know, you walk out and hand to it, and every result, you walk back and carry away.
What the field costs you
- It cannot see anything you don't hand it. Your files are invisible to it.
- Nothing lands anywhere. The chat is saved in the list down the left, but the work is stuck inside it. There is no folder, no file, nothing to open on Thursday.
- It works in one direction. It can write you an estimate; it cannot put the estimate anywhere.
- You are the bottleneck. Ten emails means ten rounds of copying. A hundred means you don't bother.
The tack room fixes all four, and it does it in the dullest way imaginable: the horse and the gear end up in the same place, and that place is a folder on your computer.
Lab 1 — Find the ceiling for yourself 10 min
You have been told the chat window has a ceiling. Far better to walk into it once, deliberately, than to hit it in the middle of real work and think you have done something wrong.
Fill the window up
- Open your project from #001 and start a fresh chat.
- Paste in something genuinely long — a full price list, a long email chain, several past quotes. More than you would normally.
- Ask a question that needs a detail from near the beginning of what you pasted.
- Now carry on a conversation for fifteen or twenty more messages about something else entirely.
- Ask that same first question again.
On a long enough conversation the early material stops being reliable. It is not broken and it is not forgetting on purpose — the ride is simply longer than the horse can carry in its head at once.
Now the other ceiling, the one that actually costs you
Close that chat. Open a brand new one and ask it the same question with no context at all. If memory is switched on, it may remember some of what you talked about — but memory keeps details and summaries, not the whole price list you pasted. Tomorrow morning you will paste it all in again.
That is the real cost, and it is the reason for the next ten workshops: you are the one carrying the facts back and forth, by hand, every single day.
Write down the number
Roughly how many things do you re-paste or re-explain in a normal week? Price list, tone, house rules, the same three exceptions? That number is what the rest of this series removes.
Files and folders, plainly
The horse thing gets thin here. So we'll drop it for a page.
A file is a thing with a name and some contents. That is the definition. A photo is a file. A letter is a file. Your rate card is a file. A folder is a box you put files in, and a folder can hold other folders, which is why things end up four boxes deep and nobody can find anything.
You already know this. You have been using files for thirty years. The reason it feels shaky is that most of us stopped looking at where things are — you search for the document by name, it appears, you never think about which box it came out of. That was fine. From here on it matters, because when you tell an assistant to work on something, you are going to have to tell it where.
File. A thing with a name and contents. rate-card.txt is a file. So is truck-photo.jpg.
Folder. A box holding files. Also called a directory, which is the same thing wearing a tie.
Two small habits will save you real trouble later, and they are worth adopting today whether or not you go any further with any of this.
- Name things so you can read them.
dale-rate-card-2026.txtbeatsDocument (3) final FINAL.txt. An assistant reads names to decide what to open, exactly like you do. - Keep one job in one place. Which is the next chapter, and honestly the most important idea in this session.
A file is a thing with a name. A folder is a box. That's it. That's the chapter.
Lab 2 — Make the folder 15 min
Dale has a folder with his rate card, his past estimates and his unopened inquiries in it. You are going to make the same shape for one job in your own business. This folder is the one you use for the rest of the series, so put it somewhere you will find it again.
Windows
- Open File Explorer and go to Documents.
- Right-click in the empty space → New → Folder.
- Name it after the job, all lowercase, no spaces:
estimates,monday-numbers,quotes. NotMy Business Stuff (new). - Open it and make three folders inside:
inbox,reference,finished.
On a Mac
- Open Finder and go to Documents.
- File → New Folder, or Cmd + Shift + N.
- Same naming rule: lowercase, no spaces.
- Same three folders inside.
Now put something real in it
- reference — your price list, your rate card, one past piece of work you were happy with. The things you keep re-pasting.
- inbox — two or three real requests. Save an email as a text file, or just paste the text into a new file.
- finished — leave it empty. The first thing lands there in #005, written by the assistant.
Nothing of your own to put in it? Use Dale’s
Plenty of people get here with nothing to hand — the price list is in somebody else’s head, the inquiries are in a phone. That is normal, and it must not stop you.
Dale’s six files are in chapter one of this page, each with a copy button. Copy them into your folder like this:
Then everything from #005 onwards runs on a real job with real numbers, and you can check the answers because the rate card is right there. Swap in your own material whenever you have it — the folder does not care whose business it is.
You cannot make these files today; there is no editor until #004. Read this now, do it in #004 Lab 2 when you make your first file, and by #005 the folder is loaded.
Why the naming rule is not fussiness
Spaces and apostrophes have to be quoted and escaped once anything automated touches them, and Dale's Estimates (final) becomes a small daily annoyance forever. Lowercase and hyphens cost you nothing today and save you a lot later.
Do not tidy your whole computer. One folder, one job, ten minutes. Tidying everything is how this stops being fun.
One folder, one job
Draw a line around the work. Everything that happens, happens inside it.
Here is the idea that makes everything after this safe. You put one job's worth of stuff in one folder, and that folder is the only place the assistant is allowed to work. People call it a project, which sounds grander than it is. It is a box with a line drawn round it.
Dale's estimate job looks like this:
When you sit an assistant down in that folder, that folder is its world. It can read the rate card because the rate card is in the room. It cannot read your bank statements, because your bank statements are not in the room. You did not have to configure that or trust a promise about it — it follows from where you opened it.
This is the same idea as the girth from the last session, the "never" that keeps a horse honest. Except this one you enforce by geography rather than by asking nicely.
- Make a new folder. Give it the name of the job:
dale-estimates. - Put in the things the job needs — the rate card, a couple of past examples, any notes.
- That's it. That's a project.
Lab 3 — Where does that job actually live? 10 min
Before the next workshop puts an assistant inside that folder, it is worth knowing what is scattered where. Almost everybody is surprised.
Track one job
Take the weekly task you wrote down in #002 and list every place a piece of it currently lives:
- Email attachments you keep having to search for
- The desktop
- Downloads
- A shared drive, Dropbox, Google Drive
- A phone camera roll
- Paper
- Somebody else’s computer
Then move the ones that matter
Copy — do not move, copy — the two or three files you would need to do that job today into the reference folder you just made. Leave the originals where they are. Nothing gets deleted in this series.
The rule you now understand
An assistant working in a folder can read what is in that folder. That is the entire reach it has, and it is why one folder, one job matters: it is simultaneously how it gets what it needs, and how it is kept away from everything else.
Your bank statements are safe because they are not in the room. Not because anything is guarding them.
Questions people actually ask
The ones that come up as soon as folders appear.
Why can't it just work with the files I already have, where they are?
Because a horse loose in the house is a different animal to a horse in a stall.
It can, and that is exactly the thing to avoid at the start. Pointing an assistant at everything you own means everything you own is in reach of a mistake. The one-folder rule costs you a minute of copying and buys you a boundary you can see. Widen it later, deliberately, once you have watched it work for a while.
Is my stuff being uploaded somewhere?
The stable is yours. The horse still lives down the road.
The folder is on your computer. The model is not — it runs on the company's machines, so anything the assistant reads in order to answer you does travel to them, the same as when you pasted into the chat window. The honest difference from last session is that it can now decide what to read. So the rule from #001 stands and matters more: don't put anything in that folder you would not put in an email.
Do I have to learn to code now?
You are learning where the tack room is, not how to make saddles.
No. You will type sentences in English, the same as last session. What changes is where those sentences land — in a room where the assistant can reach your actual files instead of waiting for you to carry them in. The editor is called a code editor for historical reasons, in the same way a glovebox is called a glovebox.
Plain words
Everything the series has named so far. Today's are marked.
This list grows every session and always shows the lot, so you never need last week's notes to read this week's.
- Large language model (LLM) 001
- The engine that predicts the next word. The horse.
- GPT 001
- Generative — it makes new text rather than looking up a stored answer. Pre-trained — all its learning happened in advance. Transformer — the design of the machinery underneath. A breed name, not a job title.
- Knowledge cutoff 001
- The date its training stopped. It knows nothing after it, and doesn't know that it doesn't. The last day the horse was out in the world.
- Prompt 001
- What you type. A pull on the reins.
- Chatbot 001
- A model you can talk to, turn by turn. Horse plus bridle.
- System prompt / instructions 001
- Standing orders sent with every message, whether you type them or not. The saddle.
- Context window 001
- How much of the conversation it can hold at once. How far it can see on this ride.
- Token 001
- A chunk of a word — how length is counted, and how you're billed. Sugar cubes.
- Hallucination 001
- Making something up and sounding certain. Shying at a shed snakeskin.
- Tool 002
- A specific action it's allowed to take in the real world. A saddlebag.
- MCP 002
- An agreed standard for plugging tools into a model. Standard-size buckles.
- Agent 002
- A model given a goal, tools, and permission to keep going. A working horse, not a show pony.
- Agentic loop 002
- Look, decide, act, check, repeat. The ride itself.
- Human in the loop 002
- A person approves before something real happens. A hand on the reins.
- Automation 002
- The same work happening without you starting it each time. The horse knows the route.
- File 003
- A thing with a name and contents. A single piece of gear.
- Folder (directory) 003
- A box holding files, and sometimes other folders. A shelf.
- Project 003
- One folder holding one job's worth of everything. The room, with the door shut.
- Path 003
- The written address of a file — which boxes it sits inside. Directions to the shelf.
Everything on one page
Photograph this before you go.
1 · The field
A chat window. You carry every fact out and every answer back.
2 · One folder, one job
Draw a line around the work. Everything happens inside it.
3 · The tack room
The editor: files on the left, work in the middle, the assistant beside it.
4 · The working horse
It comes into the room and starts opening gates.
Nothing to install today. One folder, on your own machine, with real work in it. That is all the homework there is.
#004 — The Tack Room
Today was the argument for leaving the chat window. Next time we go inside the building and fit it out — the editor, the three parts of the screen worth knowing, and the black panel that turns out to be a door rather than a test. Hands on from here on.
Before you start it: make one folder, name it after a real job, and put a copy of something real in it.
I do this for a living, and love to help people.
Thirty-plus years in enterprise software and a computer science degree — which mostly means I have watched a great many horses bolt, and I can usually tell you which ones are worth saddling before you spend money on the saddle.
In person
Your team, your room, your actual work on the whiteboard instead of somebody else's examples.
Over video
The same session, at your desks, with fewer chairs to stack afterwards.
Built for real
When the idea survives the workshop and somebody has to go and build the thing — that part I do too.
Fun fact — I rode to school on horseback as a kid in South Africa. So the metaphor isn't borrowed. I've done the falling off in person.
Emile du Toit brainitconsulting.com
Workshop #003 · Why Leave the Field
© 2026 Emile du Toit, BrainIT Consulting · Print it, share it, leave my name on it.