The Three-Question Test: what to automate first in a service business

This is the scorecard from the video, with three common workflows already scored and a blank row for your own. It takes about twenty minutes with the person who runs your office.

The three questions

1. Does it repeat every day? Lead intake does, because calls, forms and texts land all day.
2. Can you write the rules down? A dispatch exception can: the double booked tech or the job with no parts gets flagged for your dispatcher.
3. Does missing it cost you? Unbilled work is the clearest case: a finished job that never reaches an invoice. The agent drafts it, and a person sends it.

A job that passes all three is the job to hand over first. A job that fails any one waits.

Why picking is the hard part

Most small companies already have access to AI. The Federal Reserve's 2026 small business report found 46% of small employer firms use AI but only 7% have fully integrated it, and among firms planning to start, finding tools that meet business needs was the top obstacle. The Census Bureau put overall business use at 19.8% as of May 2026. The gap is not the chatbot. It is fitting AI to one specific job in one specific system.

There is a second trap. It is tempting to want one agent that does everything. Anthropic's engineering guidance says to find the simplest solution possible and only increase complexity when needed, and that fixed workflows suit well-defined tasks. If a plain rule does the job, use the rule. The three questions push you toward small, well-defined jobs on purpose.

The scorecard, with three workflows scored

Score each question 0 (no), 1 (partly) or 2 (yes). A total of 5 or 6 is a first pick. The scores below are our reasoning for a typical home service office, not measured results; yours may differ.

Candidate	Repeats daily?	Rules you can write?	Costs money when missed?	Total
Lead intake and first response	2	2	2	6
Dispatch exceptions	2	2	1	5
Unbilled work	2	2	2	6
Your candidate

Lead intake. Calls, forms, texts and ad leads land every day. The rules are writable: reply within a set time, ask the standard questions, filter spam and out-of-area requests, offer a slot. Missing it costs money directly. Invoca's 2026 benchmark found only 52% of calls to home services businesses reach a person. A person still takes anything that commits the company to a price. Our speed to lead page shows the pattern.

Dispatch exceptions. Dispatch software already handles the easy cases. ServiceTitan's playbook recommends letting Dispatch Pro assign about half of jobs automatically with Auto Mode on, based on job requirements, skills, drive time and capacity. The other half is where an agent helps: a double booked tech, a job with no parts, a customer who needs a callback. The rules are easy to write. The cost of missing one is real but harder to put a number on, so it scores a 1 there.

Unbilled work. Every day, jobs close in the field. The rule is plain: a completed job with no invoice after a set time. Missing it is money you earned and never billed. The agent compares completed jobs with invoices, drafts the missing ones, and a person sends them. See our unbilled work page.

How to score your own candidates

1. List ten tasks your office does by hand every week. Use their words, not software names.
2. Ask question one. If it does not happen at least most days, score it 0 or 1 and move on. Rare tasks are where people should stay.
3. Ask question two. Try to write the rule in one sentence a new hire could follow, for example "any job marked complete with no invoice after 24 hours." If you cannot, it is not a first workflow.
4. Ask question three. Name what is lost when it slips: a job, a payment, a customer. If nothing is lost, it can wait.
5. Add the totals and pick the top one or two. Not ten.

Questions to ask whoever builds it

Whether you build it yourself or hire someone, including us, get answers to these first:

• Which system does it run in? It should run inside the software you already use, not a new app.
• What can it do without a person? Drafts and flags first; sending, discounting and spending money stay behind approval. Our approval gates page explains how that works.
• What access does it get? Only the systems that one job needs, read-only first.
• What happens when a vendor changes its connection? Someone has to notice and fix it.
• How will you test it on our real records before it runs?

What to watch out for

• Automating a rare task because it is annoying. Annoying and frequent are different things.
• A rule only one person understands. Write it down before anyone builds anything.
• Skipping the person. The agent drafts; your office sends.
• Three workflows at once. Start with one, run it for a few weeks, then add the next.

How to tell it worked

You have a scored list, one workflow at the top, its rule in one sentence, a named person who approves its output, and a date to review it. If you want someone to walk your office and score the candidates with you, that is what the free AI Operations Audit does. The full background is in our guide to AI workflow automation for service businesses.