Most businesses don't need new software. They need the part of the process that today runs on Excel, WhatsApp and the memory of two people. That part is usually where the money leaks: approvals that sit for three days, stock that never quite matches, reports assembled by hand every Monday.

When it makes sense

The process has rules a spreadsheet can't enforce — approval limits, roles, an audit trail.
The data needs to connect to the ERP or the point of sale rather than sit on its own.
Several people work on the same document and copies multiply.
You need evidence of who approved what, and when.

How we build it

We start by following the process as it actually runs today, not as it was supposed to. Then we cut it into phases that ship one after another: the first phase replaces a small piece and goes live in weeks, not months. That way you see value before spending the full budget, and we learn your business before making decisions that are hard to undo.

What you get at handover

Source code in your repository, with the full commit history.
A test environment separate from production.
API documentation and a data model diagram.
User training and a written procedure for failure cases.
Database backup configured and restore-tested before handover.

Integrations & ERP

Connecting ERP, point of sale, warehouse and Kosovo tax fiscalisation. APIs, nightly syncs, data migrations with reconciliation.

Software

Legacy modernisation

Applications that run the business but nobody maintains. We document them, then rewrite in phases without stopping the work.

Not sure where to start?

The audit puts the whole picture on paper within two weeks, at a fixed price. The report stays yours whatever you decide afterwards.

Discuss a project