What business processes should you automate first?

A 25-person firm has more processes worth automating than it can tackle at once. Payroll runs late, invoices go out on memory, new clients wait on a manual onboarding checklist, and every month someone rebuilds the same report by hand. The hard part is rarely finding something to automate. It is deciding which processes to automate first, because the order you pick decides whether the project pays for itself or quietly stalls.

Quick Answer: Automate the process that is repetitive, rule-based, high-volume, and already digital, and that you can measure before and after. In practice that usually means billing follow-up, client intake, or recurring reporting. Rank your candidates by value, effort, and readiness, then start with the one highest-value, low-effort process and prove it before expanding.

Which processes should you automate first?

Start with one process that repeats often, follows clear rules, runs on data already in your systems, and carries a cost you can measure in hours or errors. For most small firms that is billing follow-up, client intake, or recurring reporting. Pick the single process wasting the most predictable time, automate its handoffs, and prove the result before you touch anything else.

The reason to go narrow is that the opportunity is bigger than your capacity to act on it. McKinsey's November 2025 analysis found that demonstrated technology could already automate activities accounting for about 57 percent of US work hours. That is not a to-do list. It is a warning that you can scatter yourself across a dozen half-built automations and finish none of them. Starting with one process turns a vague percentage into a specific hour count you can recover.

The hours are easy to find once you look for them. In Smartsheet's workplace automation survey, more than 40 percent of workers said they spend at least a quarter of their week on manual, repetitive tasks, led by email, data collection, and data entry. Your first target is sitting inside that quarter of the week. If you already know the workflow and want it built, that is what our implementation work covers, but the ordering below comes first.

How do you decide which process to automate first?

Score each candidate process on three things: value, effort, and readiness. Value is the hours saved plus the errors or risk removed. Effort is how many systems must connect and how complex the logic is. Readiness is whether the process is stable and you can write its steps down. The best first project scores high on value, low on effort, and high on readiness.

Run each candidate through this and the shortlist writes itself:

The trap most owners fall into is scoring on gut instead of numbers. The process that annoys you most is not always the one costing you the most. Spend the time to baseline two or three candidates properly. A firm that spends two weeks choosing the right process and eight weeks building it beats one that spends ten weeks building whatever looked impressive in the last software demo. For a fuller catalogue of candidates, see our guide to what to automate in your business.

What are the best business processes to automate first?

The best first automations live in the handoffs between systems, where a person copies information from one place to another. In rough order of how often they pay off for small firms: billing and invoicing, client or lead intake, onboarding, and recurring reporting. Each is high-volume, rule-based, and already sitting in your software.

Here is why they tend to rank in that order:

1. Billing and invoicing. The work is rule-based by design, the volume is steady, and the cost of an error or a late follow-up is real money. Generating invoices from completed work and sending the chase sequence automatically is often the fastest process to prove. Admin-heavy back-office work like this is the core of our operations and admin solutions.
2. Client or lead intake. Capturing a new enquiry, running a qualification or conflict check, and opening the file, instead of a coordinator re-typing details into your CRM or case system. High volume and directly tied to revenue.
3. Onboarding. Turning a signed client or new hire into the full sequence of documents, accounts, and tasks without someone running a checklist from memory.
4. Recurring reporting. Pulling numbers from the tools where they already live into one weekly view, instead of rebuilding the same spreadsheet every Monday.

In the law-firm audits we run, every one has uncovered ten or more automation opportunities. The pattern is that the highest-return ones are rarely the workflows the partners named walking in. That is the argument for scoring candidates rather than trusting the first idea.

What order should you automate your processes in?

Fix the data before you automate the workflow. If the same information lives in several systems that disagree, automating a step on top of that just moves bad data faster. Get one reliable source of truth first, then automate the highest-value handoff, prove it, and use that win to fund the next one.

A workable sequence for the first three months looks like this:

1. Weeks 1 to 2: choose and baseline. Score your candidates on value, effort, and readiness. Write down the current hours, error rate, or turnaround for the winner so you have a before number.
2. Weeks 3 to 4: clean the inputs. Make sure the data the process reads is accurate and lives in one place. This is the step people skip and regret.
3. Weeks 5 to 8: build one process. Automate the single highest-value handoff. Resist adding a second until the first runs on its own.
4. Weeks 9 to 12: measure and expand. Compare against your before number. If it holds, move to the next process on the list.

We built a single source-of-truth data layer for a 500-employee New York real estate company for exactly this reason. The first real problem was not a clever feature. It was that the same records lived in five places and never matched, so anything automated on top of them would have scaled the disagreement. Before your first build, it is worth checking whether your business is ready for AI at all.

Where does automating in the wrong order go wrong?

Three failure modes show up again and again: automating a broken process so it breaks faster, chasing the exciting idea instead of the profitable one, and building on messy data. Each one turns a project that should have paid for itself into one that gets quietly shelved.

The abandonment is common enough to have a number. S&P Global found that the share of companies scrapping most of their AI initiatives climbed to 42 percent in 2025, up from 17 percent the year before. Reporting on that survey pointed to a clear split: the firms that avoided the scrap heap were the ones that prioritized their use cases rather than chasing every idea. Picking the wrong process first is how a promising project becomes part of that 42 percent.

Two honest "not yet" cases are worth naming:

• Do not automate a process you are about to redesign. If the workflow does not make business sense today, automating it just makes a bad process run faster and harder to change later. Fix the process, then automate it.
• Do not make judgment-heavy, client-facing work your first project. A lawyer's advice, a pricing call, a hiring decision. These need a human on every case, and they are the wrong place to learn what automation can and cannot do. Prove the method on a rule-based back-office process first.

What should you not automate first?

Leave three kinds of process for later: anything that needs human judgment on every case, anything that happens too rarely to repay the setup, and anything still visibly broken. These look automatable in a demo and turn into maintenance work in real life. Park them, and start somewhere with clear rules and steady volume.

Quick filter for what to skip on the first pass:

• Judgment every time. If two experienced staff would handle the same case differently, it is not ready.
• Rare events. A process that runs once a quarter rarely earns back the build time.
• Known to be broken. Redesign it as a manual process first, then automate the version that works.

Start where the rules are clear. The exciting work gets easier once the boring work already runs on its own.

---

Not sure which of your processes to automate first? That is the exact question our AI assessment answers. Six questions, a couple of minutes, and you get a personalized preview of where automation would pay off in your business, before you spend anything on an audit or a build. Start assessment. You can also browse more practical guides on the Eleventh AI blog, including what an AI automation audit includes when you are ready to go deeper than a single process.

Frequently asked questions

Which business process should a small business automate first?

Most small businesses should automate billing and invoicing first. The work follows clear rules, the volume is steady month to month, and the cost of a late follow-up or a data-entry error is real money you can measure. Generating invoices from completed work and sending the chase sequence automatically is usually the fastest process to prove, which matters because your first win funds the next one. If billing already runs well, client intake and recurring reporting are the next strongest candidates for the same reasons.

How do I know if a process is ready to automate?

A process is ready when you can write its steps down and they hold true every time, the data it needs already lives in your software, and it happens often enough that the time saved is worth the setup. Test it by describing the process to a new hire on paper. If the instructions cover every case without a judgment call, it is a strong candidate. If you keep writing "it depends," the process needs clearer rules or a redesign before automation will help.

Should I automate the process that annoys me most?

Not automatically. The process that annoys you is not always the one costing you the most hours or money. Annoyance is a poor proxy for value. Before committing, baseline two or three candidates properly: count the hours, the error rate, or the turnaround time each one costs every month. Score them on value, effort, and readiness, then compare. Often the highest-return process is a quiet, repetitive one nobody complains about, while the loud problem turns out to need a redesign rather than automation.

How many processes should I automate at once?

One. Automating several processes in parallel is the fastest way to finish none of them, and it is a common reason projects get abandoned. Build one process, get it running on its own, measure it against a before number, and only then move to the next. This keeps the scope small enough to prove, gives you a clear win to point to, and lets each success fund the next build. Speed comes from finishing one thing, not starting five.

Is it better to automate finance, sales, or operations first?

For most small firms, finance and back-office operations are the strongest starting point. The work is rule-based, the volume is steady, and errors carry a clear cost, so the return is easy to measure. Sales processes like lead capture and follow-up are good second candidates because they tie directly to revenue. The honest answer is that the right department is wherever your highest-value, lowest-effort, most rule-based process sits. Score the candidates rather than defaulting to whichever team is loudest about wanting help.

Do I need new software to automate my first process?

Usually not at the start. The best first automations connect the tools you already run, moving information between them so a person no longer copies it by hand. Buying new software before you understand the process is backwards: you end up paying for a tool and then reverse-engineering a problem to justify it. Map the process first, fix the data it depends on, and only add software if the existing systems genuinely cannot do the job. The process, not the tool, decides what you need.