Updated 8 September 2026
What it may say, what it must never say, and the numbers it has to use. This is the part almost nobody writes down, and the part that decides whether the output is yours or generic.
Which files, inboxes and systems it can read, and which it cannot touch. Narrow on purpose: an assistant that can see everything is a risk, not a feature.
Who reads it before it leaves, and what happens when that person is away. If nobody would notice a wrong answer, the job is not ready to hand over.
The seven jobs, and the harness each one needs
Photos and site notes in, a draft quote out in your format. The harness is your price list and your last twenty quotes; without them you get a confident number that is not yours. You still read it before it goes.
Booking questions, availability, whether you come out to their suburb. The harness is your own FAQ and your own prices. That is what stops it inventing a policy you do not have. Drafting is automatic; sending stays a decision.
One finished job turned into a caption, a post and a page section. The harness is your brand rules and what you are actually allowed to claim. Without that you get copy that reads well and says something you cannot back up.
The export you tidy up before you can even read it, turned into the two numbers you check on a Monday. The harness is which file, which columns, and what a normal week looks like, so it flags the odd one instead of describing every one.
Last week's roster plus the rules you keep in your head. The harness is those rules written down once: who cannot work together, who is certified for what, who is on leave. Written down it drafts. Left in your head it guesses.
The recap nobody writes up. The monthly report you rebuild from scratch. The harness is last month's version, because it is the only thing that tells the AI what the way we write it actually means.
How you do things lives in your head, which is why every new hire costs you a fortnight. The harness is the first five things you would say out loud on their first morning. Written down once, it becomes something they can follow without you.
A very good hire still needs to be told how you work
The engine is not the job
You could hire the sharpest graduate in the country and they still could not start on Monday. Not because they are not capable, but because nobody has told them what the business does, which files they may open, what they must never send without asking, and who carries it if it goes wrong. AI is the same. The model is the engine. The harness is the goal, the rules, the access and the sign-off. Without the harness it will chat. With it, it finishes work.
Which is why "which AI is best" is the wrong question
Every few weeks a new model tops a chart and the internet argues about it. For the work in this list, the difference between models is smaller than the difference between having your price list written down and not having it. A cheap fast model with the rules beats an expensive slow one guessing.
And why the thing you keep is not the AI
You rent the model monthly. It gets more expensive, and it goes down on the day you need it. What stays yours is the harness: the written rules, the workflow, the examples of how you actually write, the mistakes you already paid for. That is the asset, and it moves with you to whatever model comes next.
What we would tell you not to hand over
Anything that is judgement
Pricing a job you have never done. Deciding whether to keep a difficult client. If getting it wrong costs more than doing it yourself, it stays with you.
Anything that happens twice a year
The setup cost never comes back. A job has to be frequent before automating it is worth the afternoon it takes to build.
Anything where the mess is the process
If the reason it takes three hours is that nobody agreed who approves it, AI will just produce the confusion faster. Fix the process first, then automate it.
Anything nobody would check
If a wrong answer would go out and no one would notice, do not automate it. The check is not overhead, it is the part that makes the rest safe.
On a diagnosis day, one of the four answers is often to leave it alone. We would rather say so on the day than sell you a build that quietly gets switched off.
The jobs people actually ask us to look at
Not a menu — a starting list. On a diagnosis day we look at what your week actually contains, and one of the answers is often that a job is not worth automating at all.