Start business process automation with the task that repeats often, follows clear rules and costs money or time when it goes wrong. Automation means software handles steps an employee performs today, such as copying an order from a form into a sheet. IBM defines it as a strategy that uses software to run complex and repetitive processes.
You don't need a large system at the start. You need one measured week of work and a table that ranks tasks by numbers instead of impressions. Both are below, with a worked example and five steps for applying it.
When do spreadsheets become a problem?
A spreadsheet is an excellent tool until it becomes the company's system. Trouble starts when several copies of one file exist, a row gets deleted and nobody notices, or work stops because the one person who understands the file is on leave. Look for these signs:
- The same data gets typed by hand in more than one place.
- Nobody can say which copy of the file is correct.
- A weekly report takes someone half a day of copying and pasting.
- A customer request was lost because nobody knew it was theirs to follow up.
You don't have to drop spreadsheets altogether. The practical question is which part has become expensive to keep there.
The ranking table: where to start automating processes
Start with the task that scores highest in this table. Ask each department to log its recurring tasks for a full week, then work out three things for each one:
- Hours lost per month: number of times multiplied by minutes, divided by 60.
- Rule clarity: 3 if it can be written as steps with no personal judgment, 2 if mostly so, 1 if each case needs a human call.
- Cost of error: 3 if a mistake costs money or a customer, 2 if it takes time to correct, 1 if the effect is minor.
Score = hours × clarity × cost of error. These figures are a hypothetical service company, so replace them with your own:
| Task (hypothetical) | Times × minutes | Hours a month | Clarity | Error cost | Score |
|---|---|---|---|---|---|
| Copying orders from the form to the sheet | 200 × 3 | 10 | 3 | 2 | 60 |
| Compiling the weekly sales report | 4 × 120 | 8 | 3 | 2 | 48 |
| Matching bank transfers to invoices | 60 × 5 | 5 | 2 | 3 | 30 |
| Replying to customer complaints | 40 × 15 | 10 | 1 | 3 | 30 |
| Reminding customers about late invoices | 30 × 6 | 3 | 3 | 3 | 27 |
This company starts with order entry, then the weekly report. Look at complaints: ten hours, yet a clarity score of 1. A task with that score doesn't get fully automated. You can automate logging and routing the complaint, while a person writes the reply.
The ranking fits IBM's criteria for good candidates: high volume, repetitive tasks, time sensitivity and several people involved. IBM also advises companies with little experience to start small, with a process that builds momentum.
Cost the current situation before asking for a quote
What the current way costs you is your sensible budget. The five tasks above use 36 hours a month. If we assume an employee hour costs 50 currency units, that's 1,800 units a month and 21,600 a year, before counting mistakes and lost requests. The figure is hypothetical, but the method works for your company: if someone quotes more than you'd save within an acceptable period, shrink the scope.
Five steps for your first automation
- Pick one source of truth. If the information lives in three files, decide which one counts before anything else. Automating on top of conflicting data spreads errors faster.
- Write the process as it really happens. Sit with whoever does the work and record every step, including those done "because that's how we do it." IBM also recommends defining tasks, owners and timelines before automating.
- Delete what serves no purpose. Some reports no longer have a reader. Automating a useless step only makes it faster, and deleting it costs nothing.
- Automate the repeating part and leave exceptions. With five normal cases and twenty exceptions, start with the five and route the rest to a person. Trying to cover every case produces something complicated that breaks often.
- Measure after a month. Return to your first-week numbers and compare hours and errors. If nothing changed, the automation is in the wrong place.
What's the simplest fix for each task?
Choose the smallest fix that removes the pain, then expand when you need to:
| Problem | First fix | When to move to something bigger |
|---|---|---|
| Data arrives in different formats | One form that collects it | When the form needs permissions and approval stages |
| A report compiled by hand | A report generated from one source | When its numbers come from systems that don't connect |
| Follow-ups get forgotten | An alert at a set date or number | When requests have stages and a team working them |
| Moving data between two programs | A ready connector such as Power Automate or Zapier | When exceptions pile up or the need exceeds what the tool allows |
| Every department re-enters the same data | Review the case for a unified system | See when your company needs an ERP |
Ready connectors link apps through automated workflows, but check their current prices, limits and where they store your data before subscribing. To weigh buying a tool against building a system, read how to decide between off-the-shelf and custom software.
Three areas worth measuring first
Begin measuring here, because mistakes in these areas show up quickly in the money:
- Customer requests: logging each request and assigning an owner the moment it arrives. If yours disappear after arrival, the causes are in our article on leads that don't convert into sales.
- Invoices and collection: issuing the invoice and reminding the customer when payment is late.
- Regular reports: the numbers the owner asks for each week. First settle which financial reports help you decide.
Mistakes that spoil an automation project
- Building without asking the users: staff know details that appear in no document, and they'll resist a system that doesn't fit their work.
- Connecting everything on day one: get one process stable before linking the next, so one fault can't stop everything.
- No owner for the automation: name who receives the alert when a connection stops, because a dead connection can go unnoticed for days.
- No fallback: write down what staff do by hand if the tool fails.
Common questions
Does automation mean cutting staff? The nearer goal is moving time from copying and matching to work that needs judgment, such as following up with customers and solving problems. Team size is a separate management decision, so discuss it openly and people won't resist the change out of fear.
How long does a first project take? It depends on the process and how many programs it touches. A form with an alert is far closer than connecting three old systems, so ask for an estimate per process.
Next step
Hand the table to department heads this week, collect the scores by Thursday and pick the top task. If you'd like someone to analyze the process, build the automation and measure its effect with you, take a look at PlanKit's business process automation service.