What Does Automation Actually Mean?
Forget robots and artificial intelligence. Automation in practice means something much simpler: if something happens the same way every time, a computer can do it for you.
Every day, you perform dozens of tasks that look exactly the same. You copy data from an email into a spreadsheet. You send the same message to a new employee. You pull numbers from three systems and compile them into a report. None of these steps require your expertise - they just require your time.
And that time is exactly what you can get back.
What Can You Automate?
You can automate a surprising amount of things. Here are five categories you’ll encounter most often:
1. Notifications and reminders “Send me an email when something happens.” For example: a new order comes in, a contract is approaching expiration, a customer hasn’t responded in more than 3 days.
2. Data transfer between systems “When a new order comes in, create a row in the spreadsheet.” Instead of copying data manually, it moves on its own - from email to CRM, from a form to a spreadsheet, from an e-shop to accounting.
3. Document creation “Fill in the invoice template with customer data.” The system takes data, plugs it into a prepared template, and saves or sends the result.
4. Approvals “Send for approval, and after approval, continue with the next step.” The manager gets a notification, clicks approve, and the process automatically moves forward.
5. Regular reports “Every Monday morning, send a summary of last week’s numbers.” The system pulls data on its own, compiles it into a clear format, and delivers it to the right email.
What You Shouldn’t Automate (Yet)
Not everything is worth automating. Three situations where it’s better to wait:
- Decisions that require judgment. Whether to accept a non-standard complaint, how to respond to an unhappy VIP client, whether to approve an exception - that needs a human.
- Exceptions and non-standard situations. If the process changes from case to case, automation won’t handle it. Stabilize the process first, then automate.
- Processes you haven’t mapped yet. Automating chaos just means faster chaos. First, you need to know how it’s supposed to work (see previous articles in this series).
A simple rule: only automate what you can describe as a clear, unambiguous procedure.
Tools That Don’t Require Programming
There’s an entire category of tools called “no-code” or “low-code.” They work on a simple principle: you assemble visual building blocks, similar to Lego bricks.
The basic logic is always the same:
Trigger → Action → Result
For example: An email with an invoice arrives (trigger) → Extract the amount and supplier (action) → Write it to a spreadsheet and notify the accountant (result).
Most Common Tools
| Tool | Type | Best for | Advantage | Disadvantage |
|---|---|---|---|---|
| Zapier | Cloud | Complete beginners | Simplest to use | Limited capabilities, more expensive |
| Make (formerly Integromat) | Cloud | Intermediate users | Visual, flexible | Complex workflows require practice |
| n8n | Self-hosted / cloud | Companies with IT staff | Full control, no limits | Requires technical infrastructure |
All three work on the same principle. They differ in how much control you have and how much you pay for it.
3 Practical Scenarios Step by Step
Scenario 1: Invoice Processing
What it looks like manually: An email with an invoice arrives. Someone opens it, reads the amount, supplier, and due date. Manually enters it into the accounting system. Sends an email to the manager for approval.
What it looks like automated:
- An email with an attachment arrives (trigger)
- The system recognizes it’s an invoice and extracts key data
- Creates a record in the accounting system
- Sends the manager a notification for approval
- After approval, moves the invoice to “ready to process” status
Scenario 2: New Employee Onboarding
What it looks like manually: HR creates the employee in the system. Then manually asks IT to create email and access credentials. Sends a welcome email. Assigns training. A week later, has to remember to check how the new hire is doing.
What it looks like automated:
- A new employee appears in the HR system (trigger)
- Company email and access credentials are created automatically
- A welcome email with all necessary information is sent
- Required training is assigned in the learning platform
- After 7 days, the manager receives a reminder: “How is the new colleague doing?”
Scenario 3: Weekly Reporting
What it looks like manually: Every Friday, someone opens three different systems, exports data, copies numbers into a spreadsheet, calculates metrics, and emails the results to management.
What it looks like automated:
- Every Friday at 4:00 PM (trigger)
- The system pulls data from CRM, accounting, and the project management tool
- Calculates key metrics (revenue, number of deals, utilization)
- Creates a clear summary
- Sends it to management via email
How Much Time Will You Save?
| Scenario | Manual time | Automated | Setup effort | Typical tools |
|---|---|---|---|---|
| Invoice processing | 15 min / invoice | 2 min (review) | Medium | Make + accounting system |
| Employee onboarding | 3-4 hours | 15 minutes (review) | Higher | n8n + HR system + email |
| Weekly report | 2-3 hours / week | 0 minutes (runs on its own) | Medium | Make / n8n + data sources |
From Practice: The Agency That Stopped Copying Numbers
A marketing agency with 35 employees prepared weekly reports for 12 clients. One person spent 8 hours per week manually copying data from four platforms (Google Ads, Meta, Analytics, internal CRM) into PowerPoint presentations.
What they did: They set up automation that every Monday morning pulls data from all platforms, calculates key metrics, and populates a shared dashboard. The client report is generated automatically - all that’s needed is a quick review and send.
The result: From 8 hours per week down to 45 minutes (review and occasional comments). Setup took 2 days. Return on investment was realized within 3 weeks.
But the main benefit wasn’t just about time. That person now, instead of copying data, analyzes results and proposes improvements. They’re doing work that actually matters.
When to DIY and When to Call for Help
You can handle it yourself (with a bit of patience):
- Simple automations with 2-3 steps
- Connecting two common tools (Gmail + Google Sheets, Outlook + Teams)
- Basic notifications and reminders
Better to call an expert:
- Complex workflows with 5+ steps and conditions
- Connecting multiple systems that don’t normally communicate with each other
- Automations where reliability matters (invoicing, compliance)
- Situations where you’re not sure if the process is even ready for automation
The good news: even if you get help with the setup, operating a finished automation is simple. You don’t need to understand how it’s built - you just need to know what it does.
What’s Next?
Automation is a powerful tool, but it’s not enough on its own. In the next (and final) article of this series, we’ll look at how to actually implement change - because even the best process or automation is useless if people don’t use it.