As-is survey
Interviews with process participants, mapping of document and approval routes, an inventory of existing systems and of the places where data is carried by hand.
We implement modern IT solutions and do not develop software of our own. Every implementation is preceded by consulting: first a process survey and an estimate, then the system.
A separate service with its own deliverable, not a free pre-sales conversation. It can be bought on its own — and you can take the conclusions to any contractor, including not us.
Interviews with process participants, mapping of document and approval routes, an inventory of existing systems and of the places where data is carried by hand.
Where the process stalls, where entry is duplicated, which stages have no owner, which data exists in two versions at once.
What the process should look like after the change, which steps disappear, which routes become formal, and what of this the system has to support.
Functional and non-functional requirements, integration needs, requirements for access rights, audit and document retention.
Implementation scope, a breakdown into waves, indicative budget and timeline, and the list of risks and conditions under which the estimate will change.
Including this one: "do not implement a new system now, first put your reference data and roles in order." That is a normal outcome of a survey.
Three layers that in practice almost always meet inside a single document — a request, a contract or an act.
Moving approval routes into the system: initiator, approvers, stage deadlines, behaviour on rejection and on return for rework. The process becomes visible — you can see exactly where it is stuck.
Registration, routing, signing and storage of documents with access rights and a change log. Including the filing schedule and retention rules, not just "files in a system".
The accounting core, payroll, inventory, budgeting, contracts and procurement. The subsystems and the platform they run on are on the Solutions page.
Data exchange with the systems that stay in operation: accounting, HR, banking and industry-specific ones. Within the implementation, not as a separate endless project.
Moving reference data, balances and the document archive. Usually the most labour-intensive part of a project — and the one most often underestimated in plans.
Training by role rather than a general product demo; instructions written for your actual routes; support and evolution after go-live, when new processes appear.
So that it does not have to be discovered halfway through a project.
How the work is structured by stage, what we ask from the client and which indicators we use to judge the result is on the How We Work page.