The most common answer to "where do I start with AI in my business?" is a list of tools. This guide does not give you one, because it does not work: most businesses that start by picking a tool set it up, cannot work out what to give it, and drop it. The right starting point is not a tool but a job. Below you will find how to choose that job, how to spend the first seven days, day by day, and what to measure.
Before you start: which question is the right one?
The wrong question is "which AI tool should I buy?". It leads to comparison tables, trial accounts and, eventually, a subscription nobody uses.
The right question is this: "Which job in my business repeats every week, is nobody's favourite, and can be corrected cheaply when it goes wrong?" The answer to that question also tells you where to start with AI, because a digital worker is not a general ability; it is the owner of a specific job. You cannot choose the worker before you choose the job, just as you cannot recruit before you have written the vacancy.
That is why day one needs paper, not a computer.
Which job should you start with?
The first job has to meet four conditions at once:
- It runs often. A monthly job does not accumulate enough time to be worth automating. Jobs that happen several times a week, or daily, are candidates.
- It is boring and defined. The person doing it could recite the steps in their sleep. The input is known, the output is known.
- Its output is cheap to check. You can look at the result and say "right" or "wrong" at a glance.
- Its mistakes are cheap to undo. An error can be caught before it turns into a customer, a payment or a promise; the job lives inside a system you control.
Typical first jobs that meet all four: pulling the weekly sales report channel by channel, reconciling marketplace orders with the accounting record, matching an incoming invoice to its record, triaging the inbox (a reply is drafted, you send it), appointment reminders, entering data from a document into a system.
The first jobs to avoid are the ones everybody thinks of first: unsupervised negotiation with customers, quoting prices, resolving complaints, autonomous flows that make decisions. These need judgment and are expensive to undo. Even when they work perfectly they save little time, and when they go wrong they cost a lot. We laid out the full selection logic as a two-axis scorecard in which tasks to delegate.
The first seven days, day by day
The plan below is not a software project. Each day takes less than an hour, and at the end of day seven you have a working, measured first job.
| Day | What you do | Output |
|---|---|---|
| 1 | Write the job in one sentence: input, action, output. If you cannot, the job is not yet defined enough to delegate; pick another. | One sentence |
| 2 | Describe the role: who the worker is, what it is responsible for, how it speaks, what it never does. | A job description |
| 3 | Connect the tools: switch on the skill for whichever system the job lives in. Your own spreadsheet, your own CRM, your own messaging channel. | A connected worker |
| 4 | First runs in draft mode: the worker finishes the job but leaves the last step (sending, saving) to you. Read every output. | 5-10 checked outputs |
| 5 | Continue in the same mode, but this time read the outputs as fast as you will in month three, not carefully. Note the mistakes. | A list of errors |
| 6 | Fix the job description and the instructions against that list. The fix is usually in the shape of the output: "write the difference figure" instead of "write a summary". | An updated job description |
| 7 | Open completion rights on the parts that are cheap to undo. Keep the rest in draft mode. Record the three numbers (below). | An authorised worker plus a first measurement |
Days four and five are the heart of the plan. You would not put a new person on the riskiest job on day one either; they do a few jobs, you look, then you trust. A digital worker walks the same path. The "read fast" rule on day five is deliberate: on day one everyone checks carefully, in month three nobody does. Scoring the job with month-three attention is the only way to avoid a surprise later.
Who should do this?
Two people are enough: an owner and a checker. The owner is the person who already does the job, or knows it closely; they write the job description because they know the steps. The checker is the person who reads the outputs on days four and five; it should not be the owner, because the person who checks their own description does not see its mistakes.
What you should not set up is an "AI committee". Meetings, strategy decks and tool comparisons delay the first job, and without a first job no strategy rests on real data. Seven days first, strategy afterwards.
In a small business the two people may be the same person; if so, leave day five's check until the following day and look at the outputs with a different day's eyes.
What should you measure?
Three numbers are enough, and all three are kept weekly from day seven onwards:
- Run count. How many times the worker did the job this week. If this number is not growing, the job is not frequent enough.
- Check time. How many minutes it takes on average to check one output. If it is more than a third of the job itself, change the shape of the output.
- Undone results. How many outputs were corrected or reversed this week. It does not have to be zero; it must not be rising.
The savings calculation falls out of these three: run count times the job's old duration, minus run count times check time. If you know this figure from the first week, choosing the second job is easy; if you do not, the second job gets chosen on feel, and that is usually where pilots stop.
The three common mistakes
Starting with the most impressive job. The job that talks to customers, makes decisions and "looks like AI" is not the first job. The first job is boring, and that is a good thing; we looked at why a pilot stalls when the process was never defined in a separate article.
Granting every permission on day one. Permissions open together with trust. Draft mode exists not because it feels safe but because it lets you see the output before any obligation is created. We described which actions should run freely and which should stop for approval as a matrix in approval gates.
Scaling before measuring. Adding a second job before the three numbers are kept means spending budget without knowing which job actually pays.
What happens after day seven?
The second job is chosen by the same criteria as the first, and is usually given to the same worker: a worker owns a role, and jobs that fit the role are added to it. If the role changes (giving customer messages to the worker that does reporting, say), a second worker is hired. That way what you build as the work grows is not a pile of tools but a small team with clear roles.
That is the most honest description of starting: one boring job, seven days, three numbers. The rest follows what those three numbers say.
Frequently asked questions
I have no technical background. Can I still start?
Yes. No step of the seven-day plan involves programming: writing one sentence, describing a role, connecting your own tool and reading outputs. The only thing that needs any technical knowledge is knowing which system holds which data, and the person who already does the job knows that.
Which tool should I pick first?
Pick the job first. Once the job is known, the tool question shrinks: the worker has to be able to connect to whichever system the job lives in, and the rest is detail.
What if my team resists?
Resistance usually comes from the fear of "it will take my job". Choosing a routine nobody enjoys as the first job, and having the person who does it write the job description, dissolves most of that fear; the worker becomes their tool, not their rival.
How soon will I see results?
You will have the first measurement on day seven. For a meaningful savings figure, wait four weeks; by then your checking habit has settled to its real level and the figure is honest.
Is the plan the same for a small business?
The same plan, and it runs faster. In a small business the job already sits with one person, so the description is written quickly; the real difference is that the owner and the checker are the same person. If so, leave the check until the next day.