AI Automation Roadmap: The Four Steps Before You Let AI Run Anything

An AI automation roadmap is the order you hand work to AI: first you see what you actually do, then you give AI one task at a time, then you test each system until it holds up, and only then do you let some of it run on a schedule. Skip the order and you get a pile of half-working prompts. Follow it and most of your repeat work can come off your desk.

The potential is real. McKinsey estimated in June 2023 that current generative AI, together with other technology, could in theory automate activities that take up 60 to 70 percent of employees' time (McKinsey). Reliability is what this roadmap is for.

This guide was sparked by a walkthrough from automation creator Nick Saraev, who described handing most of his agency's routine work to Claude Code over a week. The steps below are the part any owner can reuse.

AI automation roadmap: four cards reading audit, plan, test, schedule

Your AI automation roadmap: how to automate your business with AI, in four steps

  1. Audit a real week of work.
  2. Plan one system per task.
  3. Test each system before you trust it.
  4. Schedule only what is safe to run alone.

Each step has a finish line. Don't start the next one until you've crossed it.

Step 1: Run an AI task audit

Most people can't list everything they do. Memory skips the small jobs, and the small jobs are where automation pays first. So collect evidence for one normal week.

  • Keep a simple time log: every 30 minutes, note the task, the tool and why you did it.
  • Let an AI assistant ask you a handful of "what are you doing and why" questions during the day. Short answers are fine.
  • If you want an automatic tracker, keep it opt-in, pause it during client calls and banking, and never feed client screens or passwords into a model. Saraev used a screenshot tracker; most small businesses are better served by the log.

Finish line: one master list of every deliverable and process, from lead lists and inbox replies to proposals and reports.

Why the evidence matters: you can tell AI what you do, but you'll leave out context you don't notice you use. Showing it the real week fills those gaps.

Step 2: Plan one system per task

Open a fresh AI session, paste the master list and ask:

Here is everything I do in a week. My goal is to automate as much of my non-client-facing work as I can. Plan a system for each task. If you're missing context on any task, ask me before planning it.

Then answer its questions. Dictating answers is faster than typing; Saraev said his took about an hour. Expect it to ask for examples: your best email, a proposal you're proud of, a clean lead list. Give it real ones.

Finish line: a written plan for each task: inputs, steps, output, and who checks it.

Step 3: Test before you trust

An AI system can nail a task once and miss it the next time with the same prompt. So test it the way you'd test a new hire: many times, on real work, against a standard.

  • Run each task about 10 times.
  • Score each output from 1 to 10 against three things you care about (accuracy, tone, completeness, for example).
  • Average the scores. Saraev's bar was roughly 8 out of 10; set yours higher for anything a client sees.
  • Below the bar? Tell the AI what's wrong, add better examples, and run the 10 again. Bundle three or four fixes per round so you're not re-testing after every tiny change.

When a system passes, save it as a reusable skill or saved workflow so anyone on your team can run it the same way. (Several AI tools now support shareable skills; check your plan's current terms.)

The full method, with a scoring card, is in AI evals for business.

Finish line: every system has an eval card showing 10 runs and a passing average, or it stays manual.

Fix in batches

When a system misses the bar, don't tweak one thing at a time. Collect three or four fixes, change them together, then re-run all ten. If the average goes up, keep the changes; if it drops, roll them back. One batch a day beats a week of single tweaks.

Step 4: Schedule the safe ones, keep a human in the loop for the rest

Ask the three run-alone questions

Passing a test doesn't mean a system should run unattended. Ask three questions of each one:

  1. Does a client or prospect see the output?
  2. Could a mistake cost money or trust?
  3. Can you undo it within a day?
Answers What to do
No client sees it, low cost, reversible Schedule it
A client sees it, but low cost and reversible Schedule it to draft; a person reads it before it goes out
Costly or hard to undo Run it on demand with a person in charge

A daily client update draft is a good scheduled job: it's ready each morning and you skim it before sending. A full campaign or a proposal is not; it needs your judgment every time.

Human in the loop AI: what stays with you

After the roadmap, what's left on your plate should be the work only you can do: talking with clients, spotting the real bottleneck, and deciding what to build next. That's the point. You aren't removing yourself from the business; you're removing yourself from the parts that don't need you.

Free tools

One free, MIT-licensed skill for Claude, Codex and Grok comes with this guide: Eval Card (turns a week of time-log entries into one master task list, internal work first; writes a blank eval card with ten rows and a rubric for one task; scores a filled card against your bar, with the weakest criterion and the worst run; compares cards before and after a batch of fixes so you know whether to keep them; and answers the three run-alone questions for every system that passes). Download the skill (free zip)

FAQ

How do I automate knowledge work without losing quality?

Treat every automated task like a new hire on probation. Write down the standard, run the task about 10 times, score each output and only keep the system once it reaches your bar. Anything client-facing gets a human read before it ships.

What is the best way to automate repetitive tasks with AI?

Start from an audit of a real week, not a list of tools. Repetitive tasks with clear inputs and outputs, such as cleaning lists, drafting status updates or summarizing calls, are the easiest to test and the safest to schedule.

How long does an AI automation roadmap take?

Plan on about a week for the audit, an hour or two to answer the AI's planning questions, and most of your effort on testing. Testing is the slow part because each system needs repeated runs and fixes.

Is it safe to let AI tools record my screen?

Only with care. Screens show client data, passwords and private messages. A manual time log gets most of the value; if you do use a tracker, keep it opt-in, pause it for sensitive work and check where the data is stored.

Should I automate client-facing work?

Let AI draft it, but keep a person on the send button. Use automation for preparation and keep approval human whenever a mistake would cost money or trust.

A worked example: an accountant's first automation

A two-person bookkeeping firm wants AI to take work off the owner's plate.

Run an AI task audit. For one week the owner logs every task. Writing monthly client summary emails takes about five hours; chasing missing receipts takes three.

Plan one system per task. She builds one system for summaries, with its own instructions and a sample report, and a separate one for receipt reminders.

Test before you trust. She runs the summary system on ten real (anonymized) reports and scores each 1 to 10 on accuracy, tone and length. The average is 6.4, below the 8 bar.

Fix in batches. She makes three changes at once: a clearer example, a rule to quote figures exactly, and a word limit. The re-run averages 8.3, so she keeps them.

Ask the three run-alone questions. Clients see the summaries and a wrong figure costs trust, so they stay human-checked. Receipt reminders are internal and easy to undo, so they can run alone.

Schedule the safe ones. Reminders go on a schedule; summaries get a five-minute review before sending. She re-tests both monthly. The lesson: test numbers, not feelings, decide what runs alone.

Why we test before we trust

Here's the reality. I've built, scaled, and sold three companies, generated over $85 million in the last seven years in my own companies. Every system that scaled in those companies was tested before it was trusted, and AI is no different. The upside is real: McKinsey estimates current technology could automate activities that take up 60 to 70% of employees' time. The risk is a system that's right most of the time and wrong in front of a client.

That's why the roadmap puts testing before scheduling, every time.

Get an outside audit of your AI automation roadmap

If you'd rather not run the audit and the testing yourself, an AI automation audit maps your week, picks the tasks worth automating first, and builds and scores the eval cards with you. Nothing runs alone until it passes and you approve it. Why now: every week of manual repeat work is time you don't get back. For which tasks usually pay back first, see what to automate first and our guide to AI business process automation.

Ready to hand AI the right work first?

Book a call and we'll map your week and pick the first task worth automating.

Book a Search Strategy Call