AI that does the ordinary work
and cannot make things up

You probably said one of these this month

• “My staff keeps doing it a different way every time.”
• “I can't take a week off without everything stopping.”
• “Training someone new takes three weeks, and I do it three times a year.”
• “When Dave leaves, half of how this place works leaves with him.”

None of those are AI problems. They are the same problem: how your business works lives in a few people's heads, and nowhere else.

Writing it all down is the fix, and it never happens, because writing it all down is a month of work nobody has. That is the part I have solved. I interview you, and the system I built turns what you say into finished procedures — each one with the steps in order, the screenshots where they are needed, and how to tell it actually worked.

A procedure you cannot tell has failed is not a procedure. That section is in every one I write.

Why this one doesn't make things up

Most “AI for business” is a chat box with your logo on it. It will invent a step, tell you it did something it did not do, and quietly send your customer list to somebody else's server. Those are not edge cases; they are Tuesday.

I built the system I use for this myself, over years, and every one of these is enforced in the code rather than promised in the marketing:

What you actually end up with

Not a strategy deck. Not a workshop. Three things you own outright, in plain files you can read without me:

• Your procedures, written down. One per job that matters — opening, closing, quoting, onboarding, the monthly invoice run. In your words, from your answers, not a template with your logo on it.
• A system that runs them. The recurring ones turn up on the day they are due, with the steps already in front of whoever is doing them.
• A record of every change. Who did what, when, kept permanently. Nothing is quietly rewritten and nothing is deleted.

What one procedure looks like

Every one has the same five parts, because a procedure missing any of them is the reason people stop following it:

• What it is for — so the right person picks it up.
• What you need first — access, tools, who to tell.
• The steps, in order — specific enough to follow without asking.
• How to tell it worked — a procedure you cannot verify is not one.
• What to do when it fails — the part every wiki leaves out.

You do not have to take my word for the shape of it. Here are two of my own, published in full:

• Restart, verify and diagnose a server — the one I reach for when something is down at 6am.
• A working contact form — written the day I fixed one that had been silently dropping messages.

What it costs

Fixed prices, published, because you should not have to sit through a sales call to find out whether you can afford something.

Who this is not for

I would rather say this here than on a call we both paid for with an hour. Do not hire me if:

• You are a one-person business with nobody to hand work to. Documented operations pay for themselves when somebody else has to do the job. On your own, a notebook and a calendar will get you most of this for nothing.
• You want a chatbot on your website. That is a different product and there are cheaper people selling it.
• You want something that decides on its own. This one deliberately does not. It moves work, drafts, files and reminds; a person still approves anything that matters, and if that sounds like a limitation rather than the point, we want different things.
• You need it live next week. The audit alone takes about a week, and rushing the part where I learn how you work is how you get procedures nobody follows.

It fits best if you have two to about thirty people, the same handful of jobs come round every week, and at least one of them lives entirely in one person's head — and that has already cost you something, at least once.

Where your data lives

This is the second question everybody asks, so here is the answer in writing before you have to ask it.

By default, I host it

Your own instance on my server, with per-client backups and a restore procedure I have actually tested rather than merely configured. Included in the monthly.

Or it runs entirely on your hardware — +$1,500

Your server, your building, your network. Nothing leaves except the specific requests you make to an AI provider, and you can see every one of those before it is sent. For anyone whose answer to “where is our data” has to be “here”, this is the option.

Either way, you can leave

Everything is stored as ordinary text files. Export the lot at any time and it opens in any text editor on earth, with or without me. No format you need my permission to read.

How I know it works

I did not build this to sell it. I built it because I needed it, and I have used it every working day since. Everything I sell you is something I run my own business on.

The Developer's Notebook is where I write up how it is built and what broke along the way — including the mistakes. If you want to know how somebody thinks before you hire them, that is the honest version.

And if you want to work out what any of this is worth to you before talking to anybody, the notebook carries a free course on learning AI — the foundations, then a track for whatever you actually do. No sign-up.

You can also just look at it: AIOS is the system itself.

Questions people actually ask

We already use [scheduling tool / CRM / spreadsheet]. Do I have to stop?

No, and you should not. This reads from the systems you already use so it knows what is going on. It does not write back into them — deliberately. I am never going to be the reason a record in your booking system changed.

Do I have to change how I work?

No. You write the way you would on paper and the system reads it. There is no syntax to learn and no format to get right. If a plain English sentence is not understood, that is a bug in my software and I fix it — that is how it has been built from the start.

Who owns the procedures once they are written?

You do, completely. They are your words, in plain text files, in your account. Nothing about them is licensed to me.

What happens if I stop paying, or you get hit by a bus?

You export everything and it still opens. That is why it is plain text and not a database only my software can read. If I disappear, you lose my time; you do not lose your business's documentation.

Can it run on our own server?

Yes — $1,500 on top of the deployment, and then it is entirely yours. Most clients take the hosted version; the option exists because for some businesses it is the only acceptable answer.

How long before I see something useful?

The audit produces a document in a week. The first working procedures exist inside two weeks of starting the main engagement — you are not waiting until the end to see anything.