About me
I automate the processes I first had to automate in my own business
I have worked in trade for over 20 years, and have run my own trading company since 2016. When orders, documents, shipping, the bank and reports started taking more and more manual work, I began connecting those processes with code. Now I do the same for other companies.
How I got here
My main business is trading in industrial equipment: wholesale, B2B and e-commerce. Before it came eight years at a chain of DIY hypermarkets — from the shop floor to running a department — and eight years as a product manager for a manufacturer of welding equipment, working with dealers, specifications and quotations every day.
As the company grew, it accumulated small work that nobody saw as a problem of its own: move an order across, create a waybill, upload a document to the e-document service, check a payment, update a stock figure, put a report together.
Each operation took a few minutes. Together — hours of the team's time.
Off-the-shelf systems covered their own parts of the process well, but a person was still left standing between them.
So I started connecting them myself.
For myself first
At first I automated separate operations:
- putting quotations together;
- waybills and labels;
- stock synchronisation;
- documents;
- bank statements;
- reports.
Then the separate scripts turned into connected systems: a portal for partners, shipping from one window, document flow and management analytics.
Some of those processes are on this site, in the cases and in the demo — not a contractor's portfolio, but what my team uses every day.
This is no longer a set of scripts
Alongside automating my own business I grew as a backend developer: Python, Django, APIs, databases, task queues, integrations and AWS.
I also work with systems where the point is no longer a few dozen internal operations but far larger volumes of data and separate services: one of my outside projects is a data-labelling platform for machine learning, built from several connected services, with AWS infrastructure and over a hundred thousand annotations.
So I build business automation not as a one-off macro, but as a system that can be maintained, monitored and handed over to another developer.
AI is a tool, not a requirement
I use AI where it genuinely helps: classifying an unusual email, preparing a draft, making sense of unstructured text.
Where a business needs a predictable result — a price, a stock figure, a payment, a document, a status — I prefer clear rules and integrations.
The goal is not to add AI to a process. The goal is for the process to work.
Not everything needs automating
I do not start from the assumption that every manual action should become a program.
If an operation happens once a month and takes five minutes, leaving it as it is may well be cheaper.
If an off-the-shelf module solves the task properly, buy the module. I do not write code for what an existing tool solves for less.
Custom development makes sense where a repeated process already costs the business real time or limits how far it can grow.
I automate the standard path. Decisions and exceptions stay with people.
That is how the processes in my own company are built: a standard shipment goes through by itself, an unusual one goes to a manager; a recognised payment is posted by itself, an unclear one goes to the accountant.
You work with me directly
I hold the first call, take the process apart, design the solution and answer for the implementation. So there is no chain of managers between your explanation of a business task and the person building the system.
For particular tasks I may bring in other specialists, but the architecture and the responsibility for the result stay with me.
Company names and project details, for anyone who needs them, in person on the call.
My job is not to make you dependent on me
The code, the access and the documentation stay with you.
The solution must not require my daily presence to keep working.
If another developer maintains it later, they should be able to understand the system without rewriting it from scratch.
If there is a process you would like to stop doing by hand — show it to me
You do not have to decide in advance which program or integration to order.
It is enough to describe what a person does today: where they take the data from, where they move it to, and what has to happen as a result.