Business process automation should start with the process that repeats most often, touches the most people, and costs the most when it goes wrong. Score three to five candidates on those three measures from 1 to 5, pick the highest, and narrow it to a single step. The first pilot should produce a measurable result in two weeks, not six months.
Most growing companies have a process everyone agrees should be automated. It comes up in leadership meetings, people complain about it by the coffee machine, and yet it's the same process it was a year ago.
The reason is rarely laziness or a lack of skill. Getting started requires someone to stop and make a choice, while everything else on the calendar is shouting for more urgent attention.
Why Does Getting Started Feel Hard When Everything Is Urgent?
The most common reason automation gets delayed isn't doubt about its value. It's that there are too many candidate processes and too little time to choose between them. When any process could be the next target, the easiest option is to avoid choosing at all.
A week in a growing company fills up fast. The sales team needs support, customers expect answers, and the weekly report has to be on the leadership team's desk by Friday. A single automation project loses this competition for attention because its payoff shows up weeks later, while today's problems demand a fix today.
The result is familiar: a process that would take minutes if automated keeps taking hours every week, year after year. Nobody stops to calculate the cost. Three hours a week is 150 hours a year, close to a full month of working time in one single step.
How Do You Identify the Right Process to Automate First?
A good first target comes out of three questions. Score each candidate from 1 to 5 and add them up.
- How often does the process repeat? A task that runs daily or weekly delivers a visible payoff much sooner than one that happens once a quarter.
- How many people does it touch? The more people who handle the same task, the larger the combined time savings.
- What does an error cost? If a manual mistake shows up in billing, reporting, or the customer experience, the value grows fast, often beyond the time saved alone.
Here's what the scoring looks like with three typical candidates side by side:
| Process | Frequency | Reach | Cost of error | Total |
|---|---|---|---|---|
| Compiling the weekly report | 5 | 4 | 4 | 13 |
| Moving billing data out of the CRM | 4 | 2 | 5 | 11 |
| Quarterly budget round | 1 | 5 | 3 | 9 |
The winner isn't the one that sounds the most technically interesting, it's the one with the most points. The budget round touches the most people, but it happens four times a year, so the savings accumulate slowly.
Check a fourth question at the end: is the process stable? If the rules keep changing, aim the first automation at something steadier and leave the moving targets for a later phase.
Workflow Automation or AI-Assisted Automation: Which One Do You Need?
Pick the simplest technology that solves the problem. Rule-based workflow automation handles more cases than leadership teams usually expect, and it's faster and cheaper to set up than an AI-based system. The dividing line is whether the task requires judgment.
| Workflow automation | AI-assisted automation | |
|---|---|---|
| Fits when | Information moves the same way every time | The task requires judgment or reasoning |
| Exceptions | Each case is coded separately | Adapts without a new rule for every case |
| Data format | Structured, predictable | Variable: text, attachments, free-form fields |
| Time to deploy | Days to weeks | Weeks, and it needs test data |
| Maintenance | Grows with each special case | Stays steadier, needs monitoring |
| Typical example | Order from CRM into billing | Classifying incoming invoices or messages |
Rule-based automation hits its limit without anyone noticing: every new exception adds one more rule, until maintaining it costs as much time as the manual work did. That's the point to switch technology. We covered the distinction in more depth in our guide on autonomous AI agents and how they differ from traditional automation.
Once the level of technology is clear, the next choice is how to acquire it. We cover when an off-the-shelf AI tool is enough and when a custom build pays off in a separate article.
What Does Automating One Process in Two Weeks Look Like?
A narrow target doesn't need a big project. Two weeks is enough when the first week goes to mapping and the second to a pilot.
The starting point: the sales team logs closed deals in the CRM, but billing details are copied into the invoicing system by hand once a week. The task takes the controller about three hours a week and regularly produces small data entry errors that aren't caught until the following month. This is a textbook example of the hidden cost of manual sales operations.
Week 1: map it out. Pin down exactly what data moves, where it comes from, and in what format. Check whether both systems support an API, or whether a simple integration tool needs to sit in between.
Week 2: pilot it. Build the automation that moves the data directly, and run it alongside the manual process for one week. Compare results: do the numbers match, and how much time is actually saved?
Once the pilot works, the manual step disappears and the controller's three hours a week go toward other work. Running both in parallel is the single most important step: it proves with numbers that the automation produces the same result, so adoption doesn't stall on doubt.
What Should You Do Tomorrow?
If you recognize your own organization in this article, these five steps move things forward without a separate project:
- List the three processes that took up the most manual time last week.
- Score them by frequency, reach, and error risk.
- Pick one and narrow it tightly. Not the whole process, just one clear step in it.
- Set a two-week checkpoint to confirm the first version works.
- Measure the time saved and use it to decide what to automate next.
The same principle applies more broadly, which we covered in 5 signs your company is ready for data-driven decision-making: a small measurable first step matters more than a perfect starting moment.
If the list won't fall into order on its own, a fixed-price Automation Assessment walks through your processes and tells you which targets to take first and what they're worth in euros. Implementations are built on Microsoft Azure, and we're a Claude Partner Network member, so where data is processed and who can access it is known from the start.
Automation doesn't need a perfect moment or a big project. It needs one narrow process, a simple way to score and pick it, and two weeks to see a result.
Frequently Asked Questions
Where should business process automation start?
Start by scoring three to five candidate processes on three measures: how often the process repeats, how many people it touches, and what an error in it costs. Give each 1 to 5 points and pick the highest total. Then narrow that process to one clear step as your first target rather than automating the whole thing at once.
Which processes should be automated first?
The best first targets are repetitive, rule-based, error-prone steps where information moves between systems by hand. Typical examples include compiling a weekly report from several sources, moving billing details from a CRM into an invoicing system, and entering the same data into two systems. Infrequent processes are better left for later, even when they touch a lot of people.
What is the difference between workflow automation and AI-assisted automation?
Workflow automation follows a fixed rule in the form of "when X happens, do Y" and suits processes where information moves the same way every time. AI-assisted automation can interpret context and adapt to exceptions, so it suits tasks where the data varies in format or requires reasoning. The rule of thumb is to pick the simplest technology that solves the problem, because workflow automation is faster and cheaper to deploy.
How long does the first automation take to build?
A narrow first target typically takes two weeks: the first week goes to mapping (what data moves, from where, in what format) and the second to a pilot run alongside the existing manual process. That parallel run proves with numbers that the automation produces the same result before the manual step is removed.
Can you tell which processes to automate first?
The Automation Assessment is a fixed-price analysis that reviews your processes and gives you a prioritized plan: where automation is worth starting and how much it delivers.
Book an Automation AssessmentEmpirica helps growth companies remove operational bottlenecks with automation and operational AI. The Automation Assessment is a fixed-price way to find out where to start.
