Cetus Automation: we automate the work that eats up your team's time

For more than six years we have been building business software at CETUSPRO. We have over 60 deployments behind us, and our systems run in production on three continents. In many of these projects we saw the same thing: instead of doing what they were hired for, employees spend hours retyping data from one program into another.

People shouldn't be the cable between programs

An invoice arrives by email, so someone retypes it into the accounting system. An order from the CRM has to be entered by hand into the warehouse system, and every sales offer is written from scratch. One by one, these are small things. Across a team, though, they can add up to a full-time job that nobody hired for, yet the company still pays for. According to the 2024 Slack Workforce Index, repetitive tasks take up an average of 41% of office workers' time.

At the same time, fewer than 9% of companies in Poland use artificial intelligence, compared with an EU average of 20% (Eurostat, December 2025). A company that starts now will build an advantage before AI becomes standard. That is why we took what we learned from large deployments and turned it into a separate service line. That is how Cetus Automation came about.

What Cetus Automation does

We automate repetitive processes that are handled manually today and connect systems that run separately inside a company. Often the result is a single system the whole company works in, instead of paper notes, spreadsheets and copying data from program to program.

Examples of processes we automate

• Booking purchase invoices: AI reads the invoice from an email and prepares it for accounting
• Preparing sales offers from data the company already has
• Moving data between the CRM, the warehouse and accounting without retyping
• Handling service tickets, applications and customer inquiries that today wait in a queue for an employee
• An AI assistant built into the company's app that knows its data and that you talk to like a person

First we count, then we build

We start by picking one process, the one that eats up the most of the team's time, instead of tackling ten at once. Then we calculate what that process costs the company today at its real rates, because automation has to pay for itself. We set numerical success criteria before we start and check them after 30 days. If the audit shows that automation won't pay off, we say so before we build anything.

A person stays in the process from day one. The tool handles on its own only the cases it is sure about and passes the rest to an employee.

Who is behind it

Cetus Automation is run by two people, supported in their work by CETUSPRO's team of more than 40 people. Arkadiusz Dworak, AI Transformation Lead, maps processes, talks to the client's team and makes sure the tool becomes part of daily work. Kamil Jan, AI Automation Engineer, builds the prototype and is responsible for the production deployment. He also builds automations and AI tools in his own companies in Poland and Iceland, and keeps them running himself.

We consider a deployment finished only when people are still using the tool a month later, without being reminded.

To start: a free pilot

We are launching Cetus Automation with a pilot for three companies. In each one we pick a single process and launch a working automation prototype within 30 days.

How the pilot works

1. Days 1 and 2, on-site audit: we map the process with the person who knows it and measure how it runs today
2. Before the start, success criteria: we agree in numbers what should change, such as time, number of errors or cost
3. Within 30 days, a prototype on your data: we build and test the tool on our side
4. After 30 days, measuring the effect: we measure the same indicators again, and the result is shared openly