Business process automation without manual retyping.

From input to result

• Inputs: Form, Email, Excel / CSV, Scan or PDF
• Application core: Data validation, Business rules, Approvals, AI classification
• Results: Record in the register, Document or PDF, Team notification, Status overview

When it makes sense

• You manually enter the same piece of data in two or more places.
• The process stops when a particular person is away.
• Errors are only discovered at month end close.
• No one can quickly say what stage a matter is at.

What the first scope includes

• Process mapping: who, what, when and where the bottleneck occurs today
• One automated path from input to outcome, with no side branches
• Login and permissions: who can view and who can confirm
• A log of completed steps, so every outcome is traceable
• Email notifications wherever a human decision is required
• A short handover with instructions and access set up in your name

What process automation means in practice

Business process automation is not a robot replacing the team. It is a written down set of rules the team already follows, except software now carries them out. An order that arrives by email no longer gets retyped into three different files. A holiday request no longer sits stuck in the inbox. A monthly report is not assembled by hand for three hours; it is generated from data that has already been entered.

In micro and small companies, most time is lost precisely in the gaps between tools: copying from email into Excel, from Excel into the accounting package, from the package back into email. Every such transfer is a chance for an error, and every one requires a person who remembers to do it. Automation closes these gaps without having to replace tools the team already knows.

A custom software solution for a small company like this is not a pre packaged bundle with ten modules. It starts with one measurable bottleneck, uses the data and tools that already exist, and adds only the rules, roles and audit trail the process needs.

In practice I start with one process, not ten. I pick the one that repeats most often and has the clearest outcome. Once it runs reliably for a few weeks, the next one gets added much faster, because the foundations, login and records already exist.

Where automation makes the biggest difference

Not every process is worth automating. It pays off where a step repeats often, where a mistake costs something, and where everything today depends on one person.

• Receiving and confirming orders that arrive by email
• Preparing quotes and documents from existing data
• Internal approvals: procurement, holidays, travel orders, expenses
• Reminders for deadlines, contracts, servicing and renewals
• Monthly and weekly reports that someone currently compiles by hand
• Transferring data between a form, a register and accounting

What stays the same

Responsibility stays with people. The system prepares, suggests and records, but a person confirms, everywhere a confirmation carries business weight. That is why any step that sends something outward is, as a rule, designed with a review and a confirm button before it goes out.

Your data also stays yours. The application runs in your environment, access is granted in your name, and data export is always possible. For automation that touches personal data, who sees what and how long records are kept is decided at the design stage.

What I can connect

Where a system offers an API or a structured export, it can be connected. For Slovenian companies the most common technical candidates are Microsoft 365 and SharePoint, accounting solutions such as Minimax, Pantheon or SAOP, and business systems of the Business Central type. Whether a specific connection is feasible depends on your licence and access, I check this before giving an estimate, not after.

When no API is available, a reliable route remains through structured files: importing and exporting CSV or XML in an agreed format. It is not elegant, but it is stable and often entirely sufficient.

How it works

• We clarify the process: An hour or two of conversation and a review of existing files. The result is a diagram of the current state.
• Clickable prototype: You see the screens and flow before any logic is written. Changes are cheap at this point.
• Working first version: One path through the process, used with real data, usually within 1 to 3 weeks.
• Handover: Access, instructions and an agreement on what gets added next, based on actual use, not a wish list.

Frequently asked questions

• How much does automating one process cost? A first usable version for a clearly defined process starts from EUR 2,500 excl. VAT. Multi module systems are estimated after mapping and typically fall between EUR 8,000 and 25,000.
• What if the process isn't documented anywhere? That is normal. The first step is mapping: together we draw a diagram of how the work flows today. Often this alone reveals where the most time is being lost.
• Do we need to replace our existing tools? As a rule, no. The goal is to connect what you already use. I only suggest replacing a tool when it simply does not allow a connection.
• Who maintains the application after handover? Either you or I. Maintenance and additions are agreed separately; the code and access are yours in any case.