First find where time is lost. Then automate what pays off.
I come from industrial automation, where processes have to run without anyone touching them. I apply the same thinking to office, trade and production processes: where is data retyped, exported, copied and imported again? I map the processes, calculate what automation actually saves and implement the parts worth doing. If something does not pay off, I say so.
I come from industrial automation, where a line does not run on request, it runs on its own. That is where I look first: where is someone retyping numbers from one screen into the next? Where do things get exported, renamed and imported again? I do the math on those spots before I build anything, and if automation does not pay off, I say so honestly.
Let us talk about itModern company sites that load fast and get found.
Visible on Google and inside AI answers.
Custom portals, dashboards and customer areas instead of page builders.
iOS and Android from one codebase, built on TypeScript and React.
Tools for workstations that need more than a browser tab.
Systems that finally talk to each other.
Plugins, connections and extensions in the JTL ecosystem.
Servers that stay up, and someone who watches them.
Software only stays good if someone keeps at it.
Numbers that carry a decision, not just another spreadsheet.