Companies most often automate six areas: invoices and documents, sales and orders, reports and data, customer service, internal processes, and tasks where a language model helps. You calculate the savings with one formula: hours per month that return to your team × the cost of an hour of work. Below you will find business process automation examples with calculations and an indicative amount of work — the figures in the examples are assumptions; we will calculate yours when we prepare your estimate.
What is business process automation and how does it differ from integration?
Business process automation is a program that performs repetitive steps by itself according to set rules: it moves data between systems, issues documents, sends notifications and creates reports.
Integration via API is a connection in which programs exchange data by themselves. It is usually the first step: once data flows by itself, it is easy to automate the next tasks. The difference is simple — integration makes data move between systems, and automation adds rules on top: what should happen, when, and who approves it.
That is why almost every automation has two layers of cost: the connections to systems and the logic of the process itself. This article is about the second one.
How do you calculate what process automation saves your company?
Take a calculator and three numbers: how many hours a month the process takes today, how many of them the program will take over, and what an hour of work costs for the person who does it. In the examples below we consistently assume €14 per hour of work.
Euro amounts converted at the NBP mid-market rate of 14 September 2026 (€1 = 4.3391 zł) and rounded. We invoice in PLN.
Example (the figures are assumptions, not an offer): two people each spend 5 hours a week re-typing orders, which is about 40 hours a month. At a labour cost of €14/h that is €550 a month. An automation that takes 60 hours of work costs €2,750 net, so it pays for itself in about 5 months.
You calculate the payback time like this: automation cost ÷ monthly saving. On top of that comes an effect you cannot put in a table — fewer mistakes made in a hurry and a shorter path from order to invoice.
Business process automation examples — six areas
Invoices and documents
Today: someone re-types data from a paid order into the invoicing program, issues the document, emails it, uploads the PDF wherever it is needed and files a copy in the archive.
After automation: the invoice is created by itself from the paid order, goes to the document archive and to the customer, and the team gets a signal only when something has failed. Invoices from your system can also be attached automatically to orders on Allegro (Poland’s largest online marketplace) — the Allegro API lets you add up to 10 PDF invoices to each order, each up to 3 MB.
This is also where KSeF, Poland’s National e-Invoicing System, comes in: integration via API lets you send and receive invoices without logging into the system manually. Mandatory invoicing in KSeF has applied to the largest companies since 1 February 2026 and to other VAT payers since 1 April 2026, and it will cover the smallest companies from 1 January 2027. How the implementation itself works is described in KSeF integration with your own system, and receiving purchase invoices in importing purchase invoices from KSeF. Your accountants confirm your company’s obligations — CodePort handles the technical side and does not give tax advice.
Assumption: 1.5 hours a day × 20 working days = 30 hours a month. 30 h × €14 = €410 a month. Work on the process logic: 24–60 hours, plus hours for the connections to systems.
Sales and orders from several channels
Today: orders come in from the online shop, from a marketplace and from the form on your website. Someone merges them in a spreadsheet, enters them into the accounting program, changes statuses and writes to customers about what is happening.
After automation: all channels go into one system, statuses change by themselves based on events (payment, shipping), and the customer gets notifications without the team’s involvement.
Assumption: this is exactly the example from the calculation above — 40 hours a month and €550. Work on the process logic: 24–60 hours. The full scenario “orders from the shop to accounting, the invoice created by itself, a notification to the customer, an error view for the team” takes 55–130 hours, i.e. €2,550–6,100 net.
Reports and data
Today: before every meeting someone pieces together a report from several spreadsheets, CRM exports and sales data. A week later they do the same again.
After automation: data from the CRM, sales and spreadsheets lands in one panel, and the report is generated by itself on a set day. The team discusses the numbers, not why they do not match.
Assumption: 3 hours a week, i.e. about 12 hours a month. 12 h × €14 = €170 a month. Work: 16–44 hours of logic plus 6–14 hours of interface design.
Customer service
Today: requests arrive by email and phone, someone copies them into a spreadsheet, keeps track of deadlines and sends reminders by hand.
After automation: the form creates a request straight away, the customer sees the status of their case in a customer panel, and reminders about payments and deadlines go out by themselves.
Assumption: 1 hour a day × 20 days = 20 hours a month. 20 h × €14 = €280 a month. Work: 16–40 hours.
Internal processes: approvals, document flow, roles
Today: a job order circulates by email, the approval sits in an attachment, the contract in someone’s inbox, and the change history in the memory of two people.
After automation: job orders, approvals, contracts and document flow live in one tool with roles, permissions and change history. You can see who has the case and since when.
Assumption: 4 people × 2 hours a week = 8 hours a week, i.e. about 32 hours a month. 32 h × €14 = €440 a month. Work: 30–80 hours of logic plus 8–20 hours of panel design.
AI where it makes sense
Today: someone clicks data out of PDFs into a spreadsheet, sorts requests into categories and writes replies from scratch, 80% of which are the same.
After automation: a language model reads data from documents, organises requests and drafts replies. A person approves the result — that is a condition, not an extra.
Some of our own tools work this way: in the cost calculator the model estimates the amount of work for features the client describes in their own words, and from the project brief it prepares a preliminary technical specification.
Assumption: 15 hours a month × €14 = €210 a month. Work: 20–56 hours.
How many hours come back and how much work it takes — table
All the hours “to win back” are assumptions from the examples above. The amount of work is calculated at €46/h net for development and covers the process logic — on top of that come the hours for connections to systems and 10–20 hours of groundwork (architecture, task queue, logs, error handling, deployment).
| Process | What the program takes over | Hours/month to win back (assumption) | Amount of work |
|---|---|---|---|
| Invoices and documents | Invoice from a paid order, sending, archive, KSeF, Allegro | approx. 30 h | 24 – 60 h |
| Sales and orders | Orders from several channels in one system, statuses, notifications | approx. 40 h | 24 – 60 h |
| Reports and data | Data from the CRM and sales in one panel, report generated automatically | approx. 12 h | 16–44 h + 6–14 h design |
| Customer service | Requests from a form, status for the customer, reminders | approx. 20 h | 16 – 40 h |
| Internal processes | Job orders, approvals, document flow, roles and change history | approx. 32 h | 30–80 h + 8–20 h design |
| AI in the process | Reading data from documents, sorting requests, draft replies | approx. 15 h | 20 – 56 h |
Which process should you automate first?
The best candidate is repetitive, has clear rules and takes the same hours from someone every week. You will recognise it by five situations:
- data re-typed by hand between systems, for example orders from the online shop into the accounting program;
- tasks always done in the same order, for example an invoice once an order is paid and an email to the customer;
- reports pieced together from several spreadsheets before every meeting;
- reminders about payments, deadlines and appointments sent by hand;
- mistakes that come from rushing while re-typing, not from a lack of knowledge.
Start with the one process that takes the most hours. Starting with the whole company at once raises the cost and delays the moment when anything starts working.
What not to automate?
A process that changes every month, or one that nobody can describe step by step. It needs to be put in order first — automating chaos only gives you faster chaos.
Also, do not start by replacing the tools your company already uses. First we check whether they can be connected through their API; we build a new system when the current ones do not allow integration or do not support the process.
How much does automation cost and what does the rollout look like?
The cost is the number of hours × the rate: development €46/h net, design €35/h net. The number of hours depends on how many systems are connected, the quality of their APIs and the number of exceptions in the process. We set out the full price ranges for individual processes in the article on how much automation and integration cost.
At CodePort, the rollout has four stages:
- Conversation and process map — the process written out step by step; you get the price range and schedule within 2–3 working days.
- Prototype — a data flow diagram or a clickable mock-up of the dashboard, before the first line of code is written.
- Sprints — every 1–2 weeks you see a working part of the automation, not a presentation.
- Launch and further development — going live, monitoring, fixes and the next processes.
Automating one process with two systems usually takes 4–7 weeks, and connecting two systems with good API documentation takes 3–5 weeks on its own. After launch, vendors change their APIs, which is why we offer ongoing support: monitoring, updates and fixes, usually 5–15 hours a month, i.e. €230–690 net. You will find more about the scope of work on the business process automation page.
If you already know which process takes your team the most hours, describe it in the project brief builder — we will reply within one working day and prepare a free price range and schedule within 2–3 working days.
Frequently asked questions
Does process automation in a company require replacing the systems we already use?
Usually not. First we check whether your current tools can be connected through their API; we build a new system only when integration is not possible or the tools do not support the process.
What does automating one process cost?
The cost is hours × €46/h net for development. On top of the hours for process logic and connections to systems come 10–20 hours of groundwork: architecture, task queue, logs, error handling and deployment.
Will invoicing automation handle KSeF?
Yes — integration via API lets you send and receive invoices without logging into the system manually. Confirm the scope of obligations and the deadlines for your company with your accountants, because CodePort does not give tax advice.
What should you prepare before the first conversation about an automation rollout?
A step-by-step description of the process, how many hours a week it takes and from whom, and the names of the systems together with access to their API documentation. A clearly described process and available documentation lower the cost, while systems without an API and data that needs cleaning raise it.
Who makes sure the automation keeps working after launch?
We work under a contract and an NDA, the code goes to the client’s repository, and we register external services in the client’s company name, so access to the data stays under your control. Ongoing monitoring and fixes are covered by ongoing support billed by the hour.