What is process automation — and why it's not just for corporations
The word "automation" instantly conjures up a car factory: robots on the assembly line, multi-million-dollar investments, hundreds of engineers. Or Amazon, rolling out AI across every area of the business. No surprise there — those are the examples that dominate the media.
But automation doesn't start with robots. It starts with a well-described process — a sequence of actions that follow one another and lead to a defined outcome.
A similar story played out with InPost parcel lockers. Sending a package used to mean queueing at the post office, printing a label, paying by hand. Today you drop the package into a machine next to your local Biedronka. The process always existed — automation made it shorter and simpler.
Where to start — the cloud as the foundation
Running a service business — plumber, technician, recruitment agency — you might think automation isn't your world. But look at a simple situation: a few technicians, each keeping their own notebook of appointments. Someone goes on holiday — and the classic "information exchange" kicks in: who knew what, in which notebook, written with what pen.
Electronic document workflow — even something as simple as Google Sheets or files in Office 365 — is the first step toward automation. Sounds trivial, but for many companies it's a breakthrough:
- Access to the same files from your computer, phone, and tablet — no more USB sticks.
- Always up-to-date document version — no more "which version do you have?".
- A foundation for further automation — without data in the cloud there's no integration.
When should you start automating processes?
If you're just starting out in business and still learning how to serve customers — hold off on automation. Not because it's bad. It's just that you can't automate something you don't yet fully understand.
The signals it's time are the tasks you do every day that feel like pulling teeth and clearly waste your time. That's where the gold is.
Can I automate it myself? Yes — and here's where to start
With your process mapped out step by step, you can start your first attempts. You'll handle plenty of automations without writing a single line of code.
- 1
Features built into tools you already use
Gmail has filters and labels, Google Sheets has macros and notifications. Microsoft 365 has basic Power Automate. It's astonishing how much automation already waits inside the tools you use every day.
- 2
Zapier and Make.com — no-code integration
When you want to connect two apps (invoice from email → Dropbox + Slack notification), reach for Zapier (intuitive) or Make.com (more capable, cheaper at scale). For starters I recommend Zapier — faster results.
- 3
AI as your build assistant
ChatGPT, Claude, Gemini will help you design automation logic, write Sheets formulas, draft Apps Script — you describe the problem in natural language and get a solution.
How much does process automation cost?
As long as you stick to features built into Gmail or Sheets, the cost is zero (aside from your Google Workspace subscription, which you probably already have). Once you start connecting apps, tool costs come into play.
| Tool | Free plan | Paid plan | Who it's for |
|---|---|---|---|
| Zapier | 100 tasks/month | from ~$20/month | Beginners, simple integrations |
| Make.com | 1,000 operations/month | from ~$9/month | Medium and complex scenarios |
| n8n (self-hosted) | Free on your own server | Server ~$5–20/month | Companies operating at scale |
| Google Apps Script | Free | — | Inside the Google ecosystem |
What drives the cost?
- The number of apps you're connecting together
- The number of operations per month — the more often the automation runs, the more it costs
- The size and number of files being processed
- Logic complexity — filters, routers, conditions, transformations
- The need to integrate without a ready-made module (via HTTP API)
Your own low-code system vs. an off-the-shelf CRM/ERP — which to pick?
Just a few years ago, the idea of a custom CRM/ERP for a small business sounded absurd. A Comarch license, months of implementation, hands trembling at the integrator's invoice. Today the rules of the game have changed — radically.
AI augmenting developers' work means one engineer now does the job three used to. Frontend, backend, infrastructure — the lines are blurring. The cost of building a custom tool has dropped several-fold.
Off-the-shelf CRM / ERP — the pitfalls
- ✕High implementation and license costs from day 1
- ✕Long rollout time — months
- ✕Tons of features you'll never use
- ✕Either no customisation or astronomical prices
- ✕Data migration if you leave — impossible
- ✕Wishlist: "we've raised a ticket with the technical team…"
Your own low-code — the upsides
- ✓First features in weeks, not months
- ✓Quick experiments — 2–3 prototypes in a single meeting
- ✓Easy hook-up to your existing Excels
- ✓Separate database — switching tools = no data loss
- ✓Tailored to your team, not the other way around
- ✓Developer + AI = faster and cheaper than ever before
Low-code platforms worth knowing: Retool (internal dashboards), Bubble (web apps), AppSheet (Google Sheets as a database), Glide (mobile from spreadsheets).
Can you test low-code apps?
Testing is a topic that, in conversations with business, always sounds like a "luxury." "We don't have the budget for that. We need to ship new features." A common stance — and one that ends in disaster 90% of the time.
Good low-code tools (like Retool) let you write unit tests for business-logic scripts. AI has dramatically sped up test writing — what used to take hours, you now do in minutes. The more important a feature is to the business, the more urgently it needs an automated test.
When is it worth bringing in an expert?
Rolling out automation, low-code, or integrations has no chance of succeeding without deep understanding of the business and its processes. Both the official ones and the informal ones.
- 1
Interview a range of people
Not just the owner, but also the employees who run the process day to day. Each perspective reveals a different slice of reality.
- 2
Process mapping
Agree together on the start and end, then sticky notes on the wall — every step matters. Points of disagreement are hot-spots — that's most often where the real problem lives.
- 3
Edge cases
What does the process look like when something goes wrong? When the client doesn't reply? When the invoice is wrong? Edge cases are where systems fall over.
- 4
Business value as the compass
Which automated processes deliver the biggest savings? That — not the technology — should decide where to start.
Summary — where to start tomorrow
Today
Move documents to Google Drive or OneDrive — start with a single folder.
This week
Describe one process you do regularly and manually — step by step.
This month
Set up Gmail filters or a simple Zapier/Make.com automation for that process.
This quarter
Review the results and decide whether to scale on your own or with a specialist's help.
Process automation in a company isn't an IT project. It's a shift in how you think about repetitive work. It starts with one task, one process, one tool. And then it grows.
Related
How to describe a process before automating it
Related
How much does process automation cost?
Related
Low-code vs. off-the-shelf CRM/ERP
Related
What is Open Mercato — the AI framework

Mateusz Kozłowski
Założyciel flowbiz · Ekspert automatyzacji procesów
Wdrażam automatyzacje, integracje i AI w średnich firmach na Pomorzu i w Kujawsko-Pomorskiem.
