
Router Planner
Logistics routes organized straight from the CRM, without copying clients one by one.
Proprietary code
I started as an apprentice. Over time, I began turning operational problems into systems and automations.
Formal track
How the work changed
In the first months, almost everything was a first: opening up a laptop, diagnosing hardware, dealing with networks and understanding how technology works inside a real company.
Fundamentals
Ploomes is the company’s CRM. Studying it in depth at that stage is what later let me build on its API.

First tool
My first internal system came from a question: why spend an hour on something code can do in minutes?

~1 h
Before, per merge
~5 min
After, with the tool
~2×
Per week
Approximate figures.
See the mini caseDecember 2025


February 2026
When the department’s manager left, I took on a larger share of the area’s technical and operational responsibilities.
Today
I’m still on the infrastructure, systems and automations I built and maintain.
In less than two years: support, hardware, networking, infrastructure, automation, development and integrations. It wasn’t always simple — and maybe that’s why it’s where I grew the most.