Which task should you automate first?

The scorer Rate one task, get a verdict

This is the opportunity-map method from AI for Your Business — Basics → — score ten to fifteen of your team's real tasks the same way and the first bets pick themselves.

How to read it A score is a shortlist, not a green light

The point of the scorer isn't to hand you a decision — it's to stop you automating the loudest task instead of the right one. Owners tend to reach for whatever annoyed them most this week. The score pulls you back to what actually pays: work that eats time each pass, comes around often, and is the kind of work AI is genuinely good at — its fit. Those three, and only those three, make up the score.

Read the verdict as a shortlist position, not a verdict on the whole idea. A strong first bet means "this is a good candidate — worth a real test" — never "switch it on and walk away." A "later" is just as useful: it tells you to leave a task with a person for now and spend your first effort elsewhere.

Value and risk are two different questions

Notice what the fourth input — risk — does, and what it does not do. It does not raise the score. A task that would be expensive to get wrong is not a better automation candidate for being risky — it's a task that needs more care. So risk is a separate gate: at 1 or 2 you go ahead; at 3 you go ahead only with a person checking the work; at 4 or 5 it is not a first bet, however high it scores. You earn the risky jobs later, once you trust the tool. Automating a high-stakes task blindly doesn't remove the risk — it amplifies the very mistake you were worried about, at machine speed.

How the score works

Time, frequency and fit are each rated 1 to 5 and added, for a score out of 15 (at least 3). Then risk decides whether it's a first bet:

• Risk 4 or 5 — not a first bet. Whatever the score. Come back to it later.
• 12 or more — a strong first bet. Time-hungry, frequent, and work AI does well. At risk 3, a person checks the work.
• 9 to 11 — possible. Worth a test once your strongest bets are running. At risk 3, a person checks the work.
• Under 9 — later. Too quick, too rare or too poor a fit to be your first bet.

Why fit matters as much as time

Because fit decides whether AI can do the job at all. Today's AI is at its best on language and data that repeat in the same shape — the same kind of email, the same intake form, the same summary — because that's what it can reproduce reliably. The opposite kind of work, the one-off that turns on hands, judgment, context and reading the room, is the worst automation target there is, no matter how often it comes up or how long it takes. A task can be frequent and slow and still score low on fit — and that's the scorer being honest with you.

Fix the process before you automate it

One warning the score can't give you on its own: automating a broken process just makes it break faster. If the task is messy — inconsistent steps, missing information, a hand-off nobody owns — a tool will scale the mess, not clean it up. Straighten the process out by hand first, until a person can run it the same way every time. Then automate the version that already works. (Tidying the steps usually raises the fit score too — that's the same truth showing up twice.)

A worked example

Take drafting replies to routine customer questions: each one takes a few minutes (time 2), they arrive every single day (frequency 5), and it's language, over and over (fit 5). The score is 2 + 5 + 5 = 12 — and because a clumsy draft is caught before it's sent (risk 2), the verdict is a clean "strong first bet."

Now change one thing. Keep the same time, frequency and fit — so the same score of 12 — but make it processing customer refunds, where a wrong amount costs money and trust (risk 4). The value is identical, but the verdict changes to "not a first bet," because a costly mistake is never where you start. Same score, different answer — that's the whole point of separating value from risk.

Edge cases the scorer handles

• All three at 5 score 15 — the clearest possible first bet, unless risk is 4 or 5, in which case it waits.
• All three at 1 score 3 — "later." Quick, rare and a poor fit: there's nothing to gain.
• Slow but bespoke — a half-day task (time 5) that needs a real judgment call each time (fit 1) can't climb far, and that's the point: length alone isn't a reason to automate.
• Risk 3 — never an unqualified "go." At 9 or more the verdict carries "a person checks the work"; under 9 it is "later" either way.

Common questions

Why doesn't risk raise the score?

Because a costly mistake is a reason for caution, not enthusiasm. Adding risk to the score would make a high-stakes task look like a better automation target — which is backward, and genuinely dangerous: it nudges you to hand your riskiest work to a machine first. So risk is a gate instead.

Does a strong first bet mean I should just switch it on?

No. It means the task is worth a proper test — on live-but-safe work, against a pass line you set before you start, with a person checking the output before anything goes out the door. The score gets you to the starting line; it doesn't run the race.

Is the score a guarantee it'll work?

No. It's a shortlisting tool that reflects the numbers you entered. Whether a build actually pays depends on the tools, your data, and how well you set it up — none of which this box controls. Treat the verdict as a sensible place to start looking, not a promise of a result.

Why score ten to fifteen tasks rather than one?

Because a score only means something next to other scores. Scoring one task tells you it's a 12; scoring fifteen tells you it's your best bet. The free opportunity-map spreadsheet on the AI for Your Business downloads page does exactly that, with the same method.