Approach
How a project runs
No quote without looking at the actual process first. That costs me an hour and saves you a quote that misses reality.
First conversation
Thirty minutes, free of charge. You describe what is stuck. I say whether automation is worth it and give an order of magnitude.
Mapping the process
I look at how the work actually runs today, which systems are involved and where the data sits. That becomes a short description for you to read back.
Quote
A fixed price where the scope is clear. Time and materials only where it honestly cannot be estimated, and then with a ceiling.
Build
In small steps. You see work in progress and can intervene before something is built in the wrong direction.
Handover
The process runs on your real data. You also get a description of what happens where and what to do if something stops.
Operation
On request I take care of maintenance and changes. Or you take it over, and then you are not tied to me.
What you hold at the end
- Accounts and access in your own name
- A description of the process in plain language
- The option to move to another provider at any time
Where I stand, plainly
I automate processes and build applications to a solid standard. I am not a specialist for highly complex system landscapes with servers of their own, and I would rather say so beforehand than afterwards. For an ordinary operation with a shop, accounting, a warehouse and a pile of recurring manual work, I can move a great deal.