I help small teams automate repetitive tasks, connect information and turn manual work into a simpler digital process.
See how it works ↓Business process automation can start with one specific bottleneck: customer enquiries, scheduling, documents or repeated data entry.
Instead of manually copying and searching for information, the inquiry is structured and prepared for a response.
An appointment request can become a clear flow for confirmation, records and reminders.
Details from a quote, invoice or other document can be extracted and prepared for the next step.
You don’t need to know what the technical solution should look like. Just describe the problem.
Continue with this descriptionI don’t start with tools. I start with the part of your work that unnecessarily takes up time.
The solution adapts to the way you actually work, instead of forcing your work to adapt to software.
I test it against the real process and simplify anything that still creates friction.
A digital process should fit into your workday, not create another system you have to manage.
The best starting point is a recurring task that is clear enough to describe and important enough to improve.
This shows the type of improvement that is possible. It is not presented as a real client result.
One clearly defined problem and a functional first solution.
For a process with several connected steps that needs deeper simplification.
A custom business solution that does not fit a predefined package.
Clear guidance for deciding what to simplify first, what to leave manual and how to avoid an oversized software project.
How to recognise a strong first automation project, map the real workflow and measure whether it helped.
A practical way to connect information, improve existing tools and introduce change one useful step at a time.
You don’t need to know what solution you need. Just describe what takes up your time or creates unnecessary work today.
No. We start with the problem and your current way of working, then decide what is worth simplifying or connecting.
Yes. It is not always necessary to build from scratch. Often, the better approach is to remove unnecessary steps and connect what you already use.
It depends on the scope. A small improvement can be delivered quickly, while a more complex solution is first broken into clear steps. The planned timeline is confirmed before development starts.
The solution should remain clear and practical in everyday work. If further support or improvements are needed, they can be arranged separately.
A short description of the current process, a few representative examples and a person who can confirm how the work is actually done. Technical documentation is not required.
Your business data remains yours. Usage rights, source materials and handover are agreed clearly before work starts and recorded in the project scope.
You don’t need a technical brief. Just explain what you do manually today and what you would like to simplify.
I personally review the process, build the solution and remain your point of contact after delivery.
Tomislav UkićCallZagreb, Croatia