any of these points feels familiar and you feel systems are not supporting what you want to build.
Repetitive tasks, scattered data, and decisions made without context or clarity.
Operations got complex and you need a solid foundation.
You need technical criteria, fast iteration and scalability.
Clear support, well-grounded decisions, and consistent execution.
I design and build systems that bring order to operations, turn ideas into products and remove friction.
When operations grow, generic software falls short. I design systems that reflect how your business works: real workflows, connected data and operational control.
It’s not about shipping an MVP fast and mortgaging the future. I build products that validate early, then evolve and scale without rewrites.
Automation isn’t about bots, it’s about removing friction where it hurts. I turn key processes into reliable, measurable and repeatable systems.
In many projects, code isn’t missing, technical judgment is. I act as a partner to define decisions, architecture and priorities, not just execute tasks.
A few representative projects from recent years.
For more than a decade, I supported the technological evolution of a growing real estate company, designing and developing a system that centralized operations, connected critical processes and sustained growth without losing control over information.
Development of a system focused on digitizing administrative and operational processes inside a medical organization, replacing manual tasks and improving information availability for daily management.
Design and development of a SaaS platform for issuing, managing and tracking GiftCards, helping automate commercial processes and simplify operations for multiple users.
Experience across different industries and business models.
I choose the right approach before starting to build.
Simple explanations for important decisions.
Systems that adapt as the business changes.
Clear process, explicit decisions and iterative delivery to build systems that work in the real world.
Before writing code, I understand how your business works today, or what you want to build if it does not exist yet. That is where real problems and priorities surface.
Not everything is solved with more features. I define what to build, what not to, where to start and how to avoid rewrites later.
The system is built incrementally with focus on real impact, early feedback and sound decisions.
Systems do not really finish, they stay alive. I support the technical evolution as the business grows, changes or scales.
You do not always need to build something new. Sometimes the highest value is in making better use of what already exists.
Let's review where the opportunities are and what makes sense to do next.