Automation
The work nobody counts
Hand over to the machine the chores nobody wants to do, and that everyone ends up rushing.
Exporting a spreadsheet to import it somewhere else. Copying an order into the invoicing tool. Chasing people who haven’t replied, by hand. Checking every morning whether a file has arrived.
Taken one by one, these tasks take two minutes. Added up over a year, they amount to whole weeks. And because they are boring, they are the first to be forgotten on busy days. Yet an order that never gets entered doesn’t warn anyone.
Every repetitive task now takes care of itself
I connect your tools so that information flows without anyone having to step in: what goes in on one side comes out on the other, in the right format and at the right time.
Every automation stays readable and editable: you stay in control of it, even without me.
- You keep your current tools: we connect them, without replacing them
- Readable automations that you can open and understand without being a developer
- An alert as soon as something fails, so that no breakdown goes unnoticed
- Migration of your past data if needed, not just the new data
- The time saved is estimated before we start
What I build them with
The choice depends on your tools, and on who will look after it afterwards.
N8N
Visual automations that can be hosted on your own infrastructure. The right choice if you want to be able to change them yourself.
APIs and webhooks
A direct connection between two tools, when they can already exchange data and just need to be linked.
Python
When data needs to be transformed, cleaned or matched before it is passed on.
Scheduled tasks
The jobs that need to run every night, every Monday, or at the end of each month.
Spreadsheets and files
Import, export, automatic file drops: the most common starting point, and often the most cost-effective.
Monitoring
Run history and alerts on failure, so that nothing stops without warning.
How it works
1. You show me the task as you do it today, in real conditions
2. Together we estimate how often it comes up and how much time it takes you
3. I build the automation and run it alongside your current method
4. We switch over once both give the same result several times in a row
Still have questions?
I answer all your questions.
-
Do I need to change my tools?
No, quite the opposite: an automation that forces you to change tools often fails, because the team keeps using the old one.
I start from the tools you already use. If one of them really allows no data exchange, I tell you before we begin, and you decide with full knowledge of the facts.
-
What happens if the automation breaks down?
It warns you. This is a point I don’t compromise on: an automation that stops silently does more damage than the manual work it replaced, because everyone believes it is still working.
Every run is logged, and a failure triggers an alert where you will see it.
-
Who will be able to change it later?
You, as far as possible: that is why I favor N8N when your needs allow it. The automation reads like a diagram, and you can add a step without writing any code.
When the logic is too specific for a visual tool, the code is commented and documented, and it belongs to you.
-
Is it worth it for a small business?
Often more than for a large one: in a small business, the person doing these tasks is also the one doing everything else. The time saved is put to use elsewhere straight away.
The calculation is simple, and we do it before starting: the time the task takes, multiplied by how often it comes up, compared with the cost of the automation. If it isn’t worth it, I tell you so.