You can count it today
Someone already tracks how long the job takes, how many arrive each week or how often it gets redone. Without a starting number you cannot tell whether the AI helped.
Getting started
The best first job for an AI team is one where someone on your staff already reads the result before it goes out. The checking is built in, and you see quickly whether the AI did the job well.
Four tests
A job has to pass all four. If it fails one, pick another job or close the gap first.
Someone already tracks how long the job takes, how many arrive each week or how often it gets redone. Without a starting number you cannot tell whether the AI helped.
The answer lives in documents you can name: a price list, a policy, past quotes, service notes. If nobody can say where the right answer is written down, the AI will guess.
A staff member reads the reply, quote or summary before it reaches a customer. Your control is already in place, and their edits show where the AI is weak.
The AI reads a few named files and writes a draft. It does not change your accounting or customer records. Letting it write into those systems is a second decision, made after the first job works.
Start with a drafting or lookup job that you already count and already check. Answering common customer questions from your own documents is the usual winner. So is sorting incoming email, forms and invoices, or turning meeting notes into a draft quote. Leave anything that decides something about a person for later: hiring, credit, discipline. Skip any job nobody owns.
Examples
Each one passes the four tests in most small businesses, because a person already checks the output.
Scope
Each of these makes a poor first job, for the reason given.
Warning
Not sure whether your idea fits? Book a 30-minute call. We run it against the four tests and tell you.
Next step
On the 30-minute call we test one of your ideas against the four tests and tell you plainly whether it makes a good first job. You keep the notes either way.