Development and automation: from problem to result

For more than eight years I've been solving technical problems for businesses. Before AI took off, I connected systems through services like Albato, wired up webhooks by hand, and used whatever method the job called for — but the goal was always the same: cut manual work, reduce the chance of human error, and make the business run more efficiently.

Hundreds of companies over my years at JivoChat — a business automation service — taught me one thing: they don't want automation. They want one job to stop eating hours — and money — out of every day, and how it works underneath isn't something the owner needs to worry about. That kind of optimization happens to be exactly what I enjoy.

Today I take the whole thing on: I work out what you already have running, propose a solution, build the missing pieces, connect your services to each other, and set up the automation — on n8n and similar platforms, and bring in AI where it actually helps rather than just because it's the trendy word. From the first conversation to the point where the process runs without you.

Sometimes that calls for a separate application. Sometimes it's enough to connect what you already have — and I won't sell you a new build just to sell one. The choice follows the problem, not habit.