What to automate in a business first: a checklist for owners

In business, the first thing to automate should not be the "most fashionable" area, but the process that repeats every day, takes employees' time, affects revenue and cash flow, and follows clear rules. Usually that means lead processing, passing leads into the CRM, invoicing, task tracking, customer reminders, or management reporting. The first step is not buying software, but auditing processes: you need to see where the company is losing requests, hours, money, and control.

AI Summary

• Business automation should start with a process audit, not with choosing a CRM, ERP, RPA, or no-code platform.
• The first candidate for automation is a repeatable process with a high volume of operations, clear rules, and measurable financial impact.
• An owner should evaluate processes using five criteria: frequency, cost of error, impact on revenue, data readiness, and implementation risk.
• In most companies, the quickest wins come from leads, CRM discipline, invoices and delivery certificates, customer reminders, task control, and reporting.
• Do not automate chaos: if a process is not documented, has no owner, and changes all the time, it needs to be simplified and standardized first.

Contents

1. Short answer: what to automate first
2. Why the first step is a process audit
3. Process audit checklist for owners
4. Prioritization matrix: how to choose the first process
5. 7 processes that are most often worth automating first
6. What not to automate yet
7. 14-day plan: how to start without a big project
8. How to measure the impact of automation
9. Common owner mistakes
10. FAQ

Short answer: what to automate first

Key takeaways: automate first the process with lots of repeats, manual handoffs, missed deadlines, and errors. If the process directly affects revenue or working capital, it gets higher priority.

For most companies, the first automation area sits at the intersection of sales, documents, and execution control. An owner usually feels the problem this way: leads get lost, managers forget to call back, invoices are issued manually, leadership learns about problems too late, and reporting is assembled in spreadsheets on Fridays.

The right first process should meet five conditions:

• the operation repeats every day or every week;
• the process has a clear input and output;
• employees perform it according to rules, not differently every time depending on the situation;
• the error can be measured in money, time, or lost customers;
• the automation result can be verified in 2-6 weeks.

[Fact]: RPA and similar tools work best on repeatable rule-based processes: when there are rules, digital data, and a standard set of actions. If the rules change every day, automation will be expensive and unstable.

A simple formula for getting started: automate first what repeats often, is expensive to get wrong, and is easy to describe. If the process is rare, creative, or strategic, it should not be the first candidate.

Process	Automate first?	Why
Leads from the website, messengers, and phone calls	Yes	affects response speed and revenue
Invoices, delivery certificates, template contracts	Yes	saves time and reduces errors
Weekly manual reporting	Often yes	gives the owner better control
Creative marketing strategy	No	too much uncertainty and too many expert judgments
An unstable process with no owner	No	first describe and simplify it

Why the first step is a process audit

Key takeaways: a process audit is needed so you do not automate chaos. It shows where money is actually being lost, who owns the process, what data already exists, and which operation can be improved without restructuring the whole company.

The biggest mistake in business automation is starting with the tool. The owner sees ads for CRM, ERP, RPA, BI, or a chatbot and thinks the software will create order on its own. In practice, the tool only speeds up the existing process. If the process is bad, the company just gets a bad result faster.

A process audit answers management questions:

• where the process starts and ends;
• who is responsible for the result;
• which actions are performed manually;
• where delays, duplication, and errors occur;
• what data is needed to do the work;
• how much a delay or error costs;
• what can be removed before automation.

[Fact]: In the BPM approach, process modeling and analysis come before automation. First the company understands the current workflow, then improves it, and only then moves it into a system.

Example. In a company, there is a problem: "sales reps are not handling leads well." You could jump straight to implementing a CRM and bots. But an audit may show that leads come in through five channels, some land in personal WhatsApp accounts, the reps do not have a single SLA, and management only sees end results. In that case, the first project is not a complex CRM automation project, but a unified lead intake, automatic lead creation, assignment of an owner, and control of the first touchpoint.

An audit is especially useful for an owner because departments often see the problem differently. Sales blames marketing, marketing blames lead handling, accounting blames documents, and the warehouse blames late shipments. A process map turns the conversation from opinions into facts.

Process audit checklist for owners

Key takeaways: for the first audit, you do not need a complicated methodology. It is enough to list the key processes, assess manual work, operation frequency, cost of errors, and readiness for implementation.

Start with 10-15 processes that are closest to money and customers. Do not try to document the whole company at once. For the first round, sales, leads, documents, payments, tasks, customer service, and reporting are enough.

Step 1. List the processes

Create a list in a simple table:

• where the lead comes from;
• how it gets to the responsible person;
• how the deal or order is created;
• how the invoice is issued;
• how payment is tracked;
• how the client gets status;
• how the manager sees the result;
• how repeat sales get triggered.

Step 2. Find manual handoffs

A manual handoff is the moment when an employee copies data, writes a message, moves a file, reminds another person, or checks a spreadsheet. This is exactly where inquiries and time are often lost.

Mark all the places where employees:

• copy contacts from a messenger app into the CRM;
• assign an owner manually;
• forward documents by email;
• compile a report from several spreadsheets;
• check payments by hand;
• set reminders in a personal calendar;
• write standard replies to customers.

Step 3. Assess the cost of an error

Not all manual tasks are equally important. A mistake in the color of an internal task is annoying, but an error in an invoice, request, or agreement with a client can cost money.

Use the scale:

Score	What it means
1	the error has almost no impact on money
2	the error creates rework within the team
3	the error delays the client or payment
4	the error affects the deal, timeline, or margin
5	the error leads to losing a customer, a penalty, or a cash flow gap

Step 4. Check data readiness

Automation requires data: contacts, statuses, amounts, dates, owners, templates, rules. If the data lives in private chats and in employees' heads, the project will have to start with getting things in order.

Assign each process one of three ratings:

• ready: the data is already in the CRM, accounting system, or spreadsheet;
• partially ready: the data exists, but it's incomplete or scattered;
• not ready: the rules and data are not formalized.

Step 5. Assign a process owner

A process should have one person responsible for the result. Not for "building the button," but for the business metric: response time, share of lost inquiries, invoice issuance time, task backlog, report accuracy.

If there is no owner, automation often turns into a dispute between departments. The system is implemented, but no one is responsible for making sure people use it.

Prioritization matrix: how to choose the first process

Key takeaways: choose the first process not by how loud the complaints are, but by the scores. A good candidate gets a high score for frequency, financial impact, and simplicity of rules, but does not create critical risk for the business during the pilot.

Rate each process on five criteria from 1 to 5:

Criterion	Question	High score means
Frequency	How often does the process repeat?	every day, many transactions
Financial impact	Is the process tied to revenue, payments, or margin?	direct impact
Cost of an error	What happens if it fails?	loss of customer, money, or time
Simplicity of rules	Can the logic be described?	clear conditions exist
Data readiness	Is the data available in digital form?	the data is already available

Add up the scores. Processes with 18-25 points are candidates for the first project. Processes with 12-17 points can be prepared. Below 12, it is usually too early to automate.

Process	Frequency	Money	Error	Rules	Data	Total
Creating leads from inquiries	5	5	5	4	4	23
Invoicing	4	5	4	5	4	22
Weekly Sales Report	3	4	3	4	4	18
Recruiting	2	3	3	2	2	12
Developing a New Strategy	1	5	3	1	1	11

[Fact]: process mining is used to find the real routes a process takes in system logs, rather than the way employees describe the work in meetings. In a small business, the equivalent might be exports from a CRM, phone system, website, task tracker, and accounting software.

7 processes that are usually worth automating first

Key takeaways: There is no one-size-fits-all list, but in most companies the first candidates are the same: inquiries, CRM, documents, payments, tasks, notifications, and reporting.

1. Intake and routing of inquiries

If inquiries come in through the website, email, WhatsApp, Telegram, phone, and managers’ direct messages, the owner has no control over the inbound flow. The first project can be simple: all inquiries go into one system, a lead is created automatically, the source is recorded, an owner is assigned, and a deadline is set for the first touchpoint.

What to automate:

• creating a lead from a website form;
• routing inquiries from messaging apps;
• assigning a manager based on rules;
• notifications about a new inquiry;
• tracking first-response SLA.

2. CRM discipline and deal tracking

CRM should not just be an "address book." Automation helps ensure that every deal has a stage, next step, amount, owner, and contact date.

What to automate:

• required fields at key stages;
• tasks after a call or meeting;
• reminders for overdue deals;
• notifications to a manager about stalled deals;
• reports on conversion between stages.

Invoices, service completion certificates, contracts, and proposals

Documents often deliver quick wins because the rules are clear, templates repeat, and mistakes are visible to the customer. If a manager manually copies company details and amounts, automation reduces the risk of typos and speeds up payment.

What to automate:

• generating sales proposals;
• creating invoices from a deal;
• filling out contracts from a template;
• sending documents to the customer;
• payment reminders.

4. Task and approval control

When tasks live in chats, the owner only sees the problem after a deadline is missed. Automating approvals and tasks helps eliminate manual reminders.

What to automate:

• creating standard tasks based on an event;
• approval workflows;
• overdue notifications;
• escalation to management;
• completion statuses.

5. Customer notifications and service

Some communication does not require a manager: inquiry confirmation, order status, appointment reminder, request to send documents, payment notification, or delivery update.

What to automate:

• confirmation of the inquiry;
• meeting or appointment reminders;
• order status updates;
• feedback requests;
• follow-up touches after purchase.

6. Repeat sales and retention

Many companies look for new customers but forget to bring back existing ones. Automating repeat sales is often cheaper than acquisition: the system reminds the manager, or sends the message automatically at the right time.

What to automate:

• segmenting customers by how long ago they purchased;
• reminders for repeat orders;
• triggered emails and messages;
• tasks for a manager assigned to VIP customers;
• offers after the service is completed.

7. Management reporting

If a manager waits every week for a spreadsheet from the team, they are managing the past. Automated reporting helps track inquiries, sales, payments, overdue items, and margin closer to real time.

What to automate:

• data collection from CRM and accounting;
• daily reports on key metrics;
• lead and sales dashboard;
• payment and accounts receivable tracking;
• alerts for sudden deviations.

What not to automate yet

Key takeaways: a poor candidate for a first project is a rare, unstable, politically sensitive, or creative process. It should first be simplified, documented, and tested manually.

Do not start automating a process if:

• employees cannot describe it the same way;
• there is no owner of the result;
• the rules change every week;
• the data is stored only in messages and chats;
• the process first needs organizational simplification;
• an automation error could stop sales or accounting;
• the impact cannot be measured.

A typical example is trying to automate the entire sales department all at once. That is too broad a target. It is better to choose one flow: website leads, overdue deal tracking, or automatic invoice creation. A small successful project changes team behavior faster than a large project that is discussed for six months and never launched.

A 14-day plan: how to start without a big project

Key takeaways: for the first step, two weeks is enough: choose 5-7 processes, score them using the matrix, document one flow, launch a pilot, and assign a success metric.

Days 1-2. Build a process map

List the processes closest to revenue: leads, sales, documents, payments, tasks, service, reporting. Do not go into endless detail. The goal is to identify candidates, not draw a perfect diagram.

Days 3-4. Count manual operations

Ask employees to track repetitive actions for one or two days: copying data, moving it into a spreadsheet, manual notifications, reconciliations, reminders. This quickly shows where automation will reduce workload.

Days 5-6. Score processes using the matrix

Assign points for frequency, revenue, cost of error, simplicity of rules, and data readiness. Choose 1-2 processes with the highest total score.

Days 7-8. Document the current process

For the selected process, record:

• the trigger;
• input data;
• the owner;
• execution steps;
• exceptions;
• the result;
• the success metric.

Days 9-10. Simplify for automation

Remove unnecessary approvals, duplicate spreadsheets, unnecessary statuses, and manual handoffs. Automate the simplified process, not the historically accumulated set of habits.

Days 11-14. Launch the pilot

Do not roll it out across the whole company right away. Launch the pilot on one channel, one group of managers, or one document type. After 2-4 weeks, compare the metric: response time, share of lost leads, invoice issuance time, number of overdue items, report accuracy.

How to calculate the impact of automation

Key takeaways: the impact of automation comes from time savings, fewer errors, faster cash flow, and higher conversion. For a first project, a simple ROI model is enough.

Basic formula:

Monthly impact = hours saved x hourly rate + reduced losses + additional margin

Example. Managers spend 40 hours a month manually creating invoices and documents. The fully loaded hourly rate is 800 rubles. Errors in documents delay payments by about 60,000 rubles a month in turnover, and the actual cost of those delays to the business is estimated at 10,000 rubles.

Calculation:

• time savings: 40 x 800 = 32,000 rubles;
• reduced losses and delays: 10,000 rubles;
• monthly impact: 42,000 rubles.

If implementation costs 120,000 rubles, the simple payback period is about three months. This is a rough model, but it is enough for a business owner's first decision.

It is important to count more than just payroll hours. Sometimes the main benefit is not savings, but faster response time. If lead automation cuts the first response from 3 hours to 10 minutes, the effect will show up in conversion and fewer lost leads.

Common mistakes made by business owners

Key takeaways: automation fails not because of bad software, but because of poor preparation: no owner, no metric, no process standard, the project is too broad, or the team sabotages the new system.

Mistake 1. Buying a tool before the audit

CRM, BPM, RPA, and no-code platforms are useful, but they do not replace a management decision. First define the process and the metric, then choose the tool.

Mistake 2. Automating everything at once

A big project looks solid, but it is harder to launch. The first win should be quick and measurable.

Mistake 3. Failing to assign an owner

An IT specialist can configure the system, but they do not own sales, documents, or service. A business owner for the process is mandatory.

Mistake 4. Not involving employees

If automation looks like control for the sake of punishment, the team will work around the system. Explain which manual operations will disappear and how the work will change.

Mistake 5. Not measuring the result

Without a metric, the project turns into a feeling: "it got easier" or "it did not stick." Before launch, record the baseline and the target KPI.

FAQ

Where should you start with business automation?

Start with a process audit. List the key processes, find the manual operations, assess frequency, cost of errors, impact on revenue, and data readiness. Then choose one process for a pilot.

What should be automated in a business first?

First automate a repetitive process that affects revenue and follows clear rules: leads, CRM tasks, invoices, documents, customer reminders, or reporting.

Do you need to implement CRM first?

Not always. If the main problem is leads and sales, CRM often becomes the first tool. But if the bottleneck is in documents, reporting, or approvals, the first solution may be integration, document management, BI, or a no-code workflow.

Can you automate a process if it is not documented?

Technically yes, but it is risky. It is better to first document the process, remove unnecessary steps, assign an owner, and define a metric. Otherwise, the system will lock in the chaos.

How do you know a process is ready for automation?

A process is ready if it repeats, has clear rules, digital data, a responsible owner, and a measurable outcome. If everything depends on personal arrangements, governance comes first.

What first project should a small business choose?

Most often, a small business should start with lead handling, CRM discipline, automatic document creation, customer reminders, or simple management reporting.