Services · Business Automation · Kosovo
Business automation
for Kosovar companies.
The orders retyped by hand, the invoices filed twice, the report assembled every Monday morning, the approvals lost in email. I build the automations that remove that work, in Albanian or English, from Pristina.
What gets automated
Order and invoice intake
Orders and invoices arriving by email, PDF, or message turned into structured records in your system, with a human check where the numbers matter.
System-to-system sync
Stock, prices, customers, and payments kept consistent across your tools without anyone copying between them.
Reporting
The weekly report someone assembles by hand, generated on a schedule and delivered where your team already reads things.
Approvals and routing
Approval chains moved out of email into a flow with a clear state, a record, and a reminder when something stalls.
Customer messages
Incoming questions classified, routed, and drafted automatically in Albanian or English, with a person approving before anything sends.
Document handling
Contracts, forms, and delivery notes read into clean data, validated against your rules, and filed where they belong.
How a project actually runs
One process at a time, shipped and running before the next one starts. Automation programmes fail when they try to fix everything at once, because nothing reaches production and nobody trusts it.
1. Watch the process as it is
Half a day with the people doing the work. Not a workshop about the ideal process, but a record of the real one, including the exceptions everybody handles from memory.
2. Pick one process and quantify it
How many times a week, how long each time, what a mistake costs. If those numbers do not justify the build, I tell you and we pick a different one.
3. Build it with a human gate
The automation runs, but a person approves the output at first. That builds trust and surfaces the exceptions nobody mentioned in step one.
4. Loosen the gate, then move on
Once the error rate is known and low, the approval step narrows to the cases that need it. Then we start the next process.
Frequently asked questions
What is business process automation, in practical terms?
Taking a routine sequence your team performs by hand and having software perform it instead. Not a strategy exercise: a specific process, start to finish. An order arrives by email, someone retypes it into the system, someone else checks stock, someone emails the customer a confirmation. Automated, that sequence runs in seconds, leaves a record, and only involves a person at the step where judgement is genuinely needed.
Which processes are worth automating first?
The test I use is simple: high frequency, low judgement, clear rules. Order and invoice intake, quote generation, stock and price syncing between systems, recurring reports someone assembles by hand every Monday, approval chains that live in email, and customer messages that fall into a handful of predictable categories. Processes that are rare, or that genuinely need a human decision each time, usually should not be automated - and I will say so rather than build them.
Does this require replacing our existing systems?
No, and that is the point. Automation sits between the systems you already pay for and use. Your accounting software, your CRM, your spreadsheets, your inbox, your messaging apps all stay. What changes is that information moves between them without a person carrying it. Replacing core systems is a much larger and riskier project, and it is rarely what a company actually needs.
How much does business automation cost in Kosovo?
A single focused automation typically runs $3.5K to $15K to build, with low monthly running costs afterwards. A larger programme covering several connected processes runs higher, up to $60K for a full multi-workflow system. Retainers for ongoing work are quoted on the call rather than published. Every engagement starts with a free 30-minute call where I tell you honestly which process to automate first, and which ones are not worth it.
Can the automation work in Albanian?
Yes. I am a native Albanian speaker based in Pristina, so the system, the documentation, and the training can all be in Albanian. Where an automation uses AI to read or write text, Albanian works well for classification, extraction, and drafting, though slightly below its English quality on nuance - so I benchmark on your real documents and keep a person approving anything customer-facing. My guide to AI in Albanian covers where the line currently sits.
What happens if the automation makes a mistake?
It is designed on the assumption that it will. Every automation I build logs what it did and why, routes anything it is not confident about to a person instead of guessing, and can be switched off without taking your business down with it. Approval steps sit in front of anything that touches money or a customer. An automation you cannot audit or stop is a liability, not an asset.