FAQ
How do you calculate the cost of manual work?
For every manual step I count how many people do it, how many hours a week, what an hour of their work costs including overheads, and what the errors cost: corrections, returns, late payments. The sum is money per year. The numbers come from your team and your systems, not from my head.
Why pay up front?
The map is a diagnosis, and I diagnose before I fix anything. You pay for it like an audit or a legal opinion: up front, whatever the result. If we start implementation within 60 days, the full amount counts toward it.
What if the map shows automation isn't worth it?
That's a result worth paying for too: you know before spending PLN 80,000 on implementation, not after. You get the map with the numbers and decide for yourself.
How much of my team's time does it take?
Usually 2–4 hours of interviews and observation with each person who runs the process, plus read access to the systems. I do the rest.
Do I have to do the implementation with you?
No. The map is yours. If you choose me within 60 days, the full PLN 15,000 comes off the implementation price.
Do you sign an NDA?
Yes, before I see any data. Your template or mine (mutual NDA).
Why don't you bill by the hour?
With an hourly rate you pay for my time, not the result, and the slower I work the more I earn. With a fixed price the overrun risk is mine, and you know up front what you'll spend and what you'll get.
How do you know what it should cost?
From the conversation and the Automation Map: we know what manual work costs you today and how much you'll recover. The implementation price is a fraction of that, aiming for payback within a year. You get three options with different scope and choose.
Why pay in full up front?
Because the price is fixed and I carry the overrun risk. You pay once, for an agreed scope, and know the amount won't change.
What if the scope changes?
Every change is a separate, small quote that you approve before I start on it. No surprises on the final invoice.
What technology do you use?
Java 21 and Spring Boot 3 on the backend, Angular with SSR on the frontend, PostgreSQL, AWS or your own infrastructure. The same discipline as in banking (PKO BP Finat): tests, CI/CD, monitoring, audit logs.
Who owns the code?
You do. Code, repository, data and documentation are yours from day one. You can keep developing the system with your own team or anyone else.
Do you work alone?
Yes, one person is accountable for the result. I take on 2 implementations per quarter so each gets full attention.
What does the monthly scope include?
We agree it before we start: monitoring, updates, incident response and a pool of small changes. Larger features are quoted separately before I start.
Can I cancel?
Yes, in any month. You get full documentation and access so you can hand the system over.