Saddlebags
and the Ridewhen a chatbot starts doing a job

Up to now everything the model produces is words on a screen. You still copy them somewhere. Tools change that. A tool is a specific thing the model is allowed to reach for — like handing your rider a set of keys, a price list and the mail.

Typical saddlebags for a small business:

That split matters more than it looks. The model doesn't secretly reach into your bank. It says, in effect, "I would like to use the send-email tool, addressed to this person, with this text." Software you control then decides whether that happens — straight away, or only after you press approve.

Ask a question, get an answer, done — that is a horse doing one trick. Watch a working horse cut a calf out of a herd and you see something else entirely: it looks, it moves, it checks what happened, it adjusts, and it keeps going until the job is finished.

That is the agentic loop, and that is what people mean by an AI agent. Not a robot. A loop.

The same loop, in a real yard

Goal: "Follow up on every invoice more than 14 days past due."

1. Look. Opens the accounts tool. Finds eleven overdue invoices.
2. Decide. Notices two are from the same customer — those should be one letter, not two.
3. Act. Drafts ten reminders, each with the right amount, date and job reference.
4. Check. One customer has no email address on file. It can't send that one.
5. Round again. Puts that one on a short list for you, marked "needs a phone call", and finishes the other nine.
6. Stop. Leaves nine drafts in your outbox for approval, and a note about the tenth.

Nothing in there is clever. It is what a good office assistant does. The difference is that it happens at seven in the morning and takes forty seconds.

The whole rig

Last session covered the ways a talking horse goes wrong: it makes things up, it goes where it thinks you meant, and it has no idea what today is. All of those are still true and none of them have got worse. But giving it saddlebags adds one more, and it is the one worth taking seriously.

It does the wrong thing quickly, and repeatedly. A loop with tools attached amplifies whatever you gave it. When it could only talk, a bad instruction produced one bad paragraph that you read and threw away. When it can act, the same bad instruction produces two hundred emails, and you find out afterwards.

Nothing about the horse has changed. What has changed is that a mistake now leaves the yard.

Those five are not a beginner's training wheels to be discarded later. Businesses running this properly still work that way, because the rules cost almost nothing and the alternative costs a customer.

The question is never "can I trust it?" It is "what happens if it's wrong here, and can I undo that?"

The pattern never changes. Something arrives or some hour comes round; standing instructions say what to make of it; tools fetch what's needed and put the result somewhere; a person checks the end of it. Read the table across, one row at a time.

Where it earns its oats

• Work that is repetitive, written, and low-stakes on its own — but adds up to hours.
• Reading long things and pulling out the three lines that matter.
• First drafts. Always first drafts. Blank pages are expensive.
• Sorting: which of these forty emails is actually a new customer?

What not to hand it first

• Anything where being wrong is expensive, legally binding, or hard to spot.
• Work you don't already understand yourself. You can't check what you can't judge.
• The one job that's messy because your process is messy. Fix the process; then automate it.

You do not need to buy anything, hire anyone, or understand a single acronym to start. Here is the order that works.

1. Pick one task you do every week that is mostly reading and writing, and that annoys you.
2. Write down how you do it now — in steps, the way you'd teach a new employee on their first morning.
3. Do it by hand in a chat window, three times. No automation. Paste in a real example, ask for the result, correct it. Notice what you keep having to explain.
4. Turn what you kept explaining into a saddle. Write those standing instructions down in a note, then save them somewhere the chatbot reads automatically, so you stop retyping them. Session one showed you where that setting lives.
5. Use it manually for two weeks. If it isn't saving you time as a copy-and-paste job, tools won't save it either.
6. Only now ask what tools it needs. Usually one or two. This is the point to bring in someone technical, and you'll brief them well because you did steps 1–5.
7. Keep a person on the last step for the first month. Approve, don't automate.
8. Then take the second task. Not before.

And the rider stays on. You set the goal, you set the boundary, you check the end of it. That doesn't get automated — it's the part that was always yours.