Routine that runs itself
Retyping, forwarding and manual checks are on us. Your people go back to what you pay them for.
What one routine costs you
Money does not vanish in big projects but in the small acts nobody counts, because they only take a moment. Try adding up one of them.
Pick what sounds familiar and put in your own numbers.
A rough estimate from your numbers. During mapping we sharpen it against what really goes on in the company.
Per month
8 hours of manual work
Per year
12 working days of manual work
How it goes with us
One process at a time. We start with the one that takes the most time, and the rest of the company runs as before.
-
We map where the time goes
We walk one process end to end with your people and write down every step a human does by hand. Out of that comes what costs the most hours and what is worth automating first.
-
We connect what you already have
Usually we replace nothing. The e-shop, the accounting and the warehouse normally work fine, they just do not talk to each other. We put a layer between them that passes the data along by itself.
-
We run it alongside the manual work
For the first week the automation runs alongside the way it has been done so far and we compare the results. We switch over only once it matches. After that we watch it run and get in touch when something breaks.
What we most often automate together
The most common places where companies retype by hand. Your case need not be among them; the principle stays the same.
Orders and the e-shop
- The order in the warehouse created the moment it is placed, nobody retypes it
- Reservations and stock goods reserved and an alert when stock drops below the limit
- Statuses and labels delivery labels and the order status go back into the e-shop
Invoicing and payments
- An invoice after dispatch issued and sent by itself as soon as the goods leave the warehouse
- Matching payments by the payment reference and the amount
- Exceptions go to a human whatever does not add up lands on the pile for manual review
Documents and data
- Retyping from a PDF from email attachments straight into the system
- Working with files moves and renames according to rules
- Exports and reports regularly and without opening Excel
Communication
- Alerts into the chat into the company chat instead of an overflowing inbox
- Replies to the customer automatic confirmations and replies
- Reminders approaching deadlines and unpaid invoices
Custom systems
- Connecting through an API where an API exists
- A bridge over the system for a system that has no API
- One sign-in and one role across the tools
Artificial intelligence
- Reading attachments and emails including the ones with no structure at all
- A proposed classification a human only confirms it
- An agent inside the system it reaches into the system for you
When we do not go for it
Not every routine is worth it. If our numbers say the automation will not pay for itself, we say so before you start paying.
-
When the process changes every month
Automating a process that is all over the place means setting it in concrete. First we straighten it out; only then does building around it make sense.
-
When it comes out as a few hours a year
If the calculator above shows a few hours of manual work a year, the integration will not pay off. We say so straight out, even if it costs us the job.
-
When the data is a mess
Duplicate customers and one product under two codes can swallow more time than the connection itself. That is why we run the data clean-up as its own stage with its own budget, not as preparation.
-
When a mistake has fatal consequences
Some cases cannot be judged automatically, and a wrong decision costs more than the whole saving. The system sets those aside for manual review instead of guessing.
What it costs
Automation has no price list, because no two companies have the same process. So we build the price in one of two ways and you choose which. We can start from €200.
What you ask most often
-
Do we have to change the systems we use because of it?
Usually not. We put a layer between them. If it turns out that some tool does not allow integration at all, we say so before we start and talk through what to do about it.
-
How long does it take?
Mapping the process is a matter of days. The first connection is usually running within weeks, not months, because we do it one process at a time, not the whole company at once. We name the exact date after mapping, once we know what we are getting into.
-
What if the automation gets it wrong?
It does not rewrite what it is not sure about. Doubtful cases it sets aside for manual review, and you can see why it did. On top of that, the first week it runs alongside the manual work and we compare the results.
-
Will the people who did it lose their jobs?
It has not happened with us so far. We take the retyping off them, not their remit. In the companies where we automated, the time saved usually flowed into work nobody had got round to before.
-
Who will maintain it when something changes?
We will. The systems around change, APIs get versioned and forms stop matching. We watch it run, and when an integration falls over, we find out, not you from a customer.
-
Where will it run?
Either on our hosting next to your website, or at your place if your security policy requires it. We can do both; hosting with us is simply more convenient, as you get one place for operations and development alike.
What do you do
over and over again?
Tell us which routine takes the most of your time. We will look at it and work out what removing it would cost, even if the answer turns out to be that it is not worth it.