Assessment: how many hours your process consumes
Before we build anything, we sit with your processes and count hours. The result is a map — not a promise.
The first question in a conversation about automation is usually “what platform will you use?”. The second — more important — is: “which process should we tackle first?”. Answering it requires an assessment.
What the assessment involves
We sit with your processes and count hours. Not based on declarations — based on how documents actually arrive, who re-types fields, who approves, and how long waiting takes.
The result is a map:
- where invoices or orders come from: mailbox, scan, PDF, KSeF, email body;
- who currently re-types fields and which system they go to;
- who approves, who substitutes for an absent person, and how long a document can stand;
- which fields extraction handles on its own, and which go to a person because the read is uncertain.
Time for this step: 1–2 weeks.
What comes from the map
The map produces a sequence. One workflow at a time — we add the next only when the previous runs without us. We don’t promise to automate everything. We show what’s worth tackling first and why.
What this isn’t
This isn’t a “free audit” followed by a pitch for everything. We don’t collect data to sell more. The assessment ends with a map and a quote for one first process — nothing more.
After the assessment
Only from the map do you choose the tool. Sometimes it’s a platform you already have. Sometimes something different. But the tool appears in the middle of the conversation, not in the headline of an offer.
Because what stays with you is a working process — not a logo on a page.