The short answer
Most firms do not want an AI tool to look after. They want one piece of repetitive work to stop landing on their people. So I offer it that way. You name one job, for example typing emailed orders into your system or checking timesheets before the payroll run. I build the system that does it, run it every month for a fixed fee, and send anything unclear to a named person on your team.
You do not log in to anything new and you do not replace the system you already use. The work keeps arriving where it arrives today, and the result appears where your team already looks.
1. Check the task
Answer five questions about the job. You get a plain answer on whether it is worth automating. If the honest answer is no, that is where it ends, and it has cost you two minutes.
2. A private plan and a call
If it is worth doing, you get a private page with the plan for that job, which you can share with finance or IT. Then we talk for half an hour. I ask for no documents before that call.
3. A look at real examples
After the call I look at a small set of real examples of the work, with anything sensitive removed. That shows how often the unclear cases come up, which is what sets the fee.
4. One fixed monthly fee, in writing
You get one offer. It says what the system does, what stays with your team, how unclear cases reach a person, and the fixed monthly fee. You see all of it before any work starts.
5. A trial beside your team
The system first runs beside the people doing the job, and its results are compared with theirs. It goes live when the comparison says it is ready.
6. Run and kept current
After that I run it. When a customer changes a form, a price list moves or a rule changes, keeping the system right is part of the service.
What you get each month
The job done, every working day, without anyone on your team starting it.
A short note with the counts. How many items came in, how many went straight through, how many went to a person and why.
One person to write to, me. I built it, so I can answer for it.
What stays with your team
Decisions stay with people. The system does the reading, the matching and the checking, and it is built to stop when it is unsure. Your team sees each unclear case with the reason attached, and decides.
Nobody is asked to learn a new screen. Unclear cases arrive by email or in the system your team already uses.
When this is the wrong fit
If the job takes under two hours a week, it is too small to be worth a monthly fee. The five questions will tell you so.
If the rules for the job live in one person's head and change every week, they need writing down first. I can help with that, but it is a different piece of work.
If you want to own and run the software yourselves, a one off build with a handover suits you better. Say so and we will talk about that instead.
Jobs I run this way
| The job | What arrives | What you get back |
|---|---|---|
| Customer orders | Emails, PDFs and spreadsheets from customers | Orders prepared for your system, with unclear lines sent to a person |
| Quotes | Enquiries in the sales inbox | A draft quote that shows where each price came from |
| Timesheets | Scans, photos and spreadsheets from sites | Hours checked against your rules, ready for the payroll run |
| Daily reports | Notes, forms and exports from each site | One report with every number traceable to its source |
Where to start
Start with the five questions on the one job that costs your team the most time. It takes two minutes, and you see the answer without giving an email address.