Hello! Thanks for stopping by. It means a lot that you took the time to learn a little more about me. Below you'll find my professional journey. I'm always open to opportunities where I can solve tough problems, build great products, or simply make something better than it was yesterday. If anything resonates with you or you'd like to connect on LinkedIn(opens in a new tab) don't be shy!
You and I have something in common. 80,000 hours of work in a lifetime.
- SpainAlbesa · 1998
- TurkeyIstanbul · 2015
- GermanyKleve · 2016–20
- Netherlands’s-Hertogenbosch · 2020–now
- CATHola, em dic ArmandNative
- ESPHola, me llamo ArmandNative
- ENGHi there, I'm ArmandFluent
- NLDIk ben Nederlands aan het lerenLearning
Anthony Veder B.V.
Anthony Veder is a Dutch gas shipping company that has been moving liquefied gases across the world since 1937. They operate a fleet of gas tankers serving the world's leading energy and chemical companies.
What I learned while working at Anthony Veder:- Caring deeply about what customers want is much different from continually asking them what they want; it requires intuition and instinct about desires that have not yet formed. My task is to read things that are not yet on the page.
OverviewAfter almost six years at a startup, I made a deliberate decision to join an established company. I wanted more balance, but I was also genuinely curious to see how a mature organisation tackled the same challenges we had been struggling with at CtrlChain.
At Anthony Veder, I own the product relationship with two core platforms: IMOS, the industry standard maritime operating system used to manage the full voyage lifecycle, and Box, the company's enterprise content management platform. My day to day combines product ownership with project management, acting as the internal bridge between Anthony Veder's operational teams and external vendors.
HighlightsIMOS Workflow Optimisation
Identified and structured a set of long-standing operational pain points across cargo handling, bunker management, laytime calculations, and voyage order templates into a formal consultancy engagement with Veson, the makers of IMOS. Managing the delivery of solutions end to end.
Content Management Strategy
Leading the definition of a strategy to restore Box as a reliable single source of truth across the organisation, addressing years of accumulated digital clutter and search fatigue.
CtrlChain B.V.
2019 — 25
CtrlChain focuses on removing chaos out of road freight, so shippers and suppliers can focus on moving goods instead of managing spreadsheets and emails.
What I learned while working at CtrlChain:- Work to ensure that the entire customer experience is delightful beyond just product.
- Perform continuous discovery to define what customers are willing to pay for.
- Avoid the trap of falling in love with the solution. Instead focus on the problem you are trying to solve.
- It takes a lot of hard work to make something simple, to truly understand the underlying challenges and come up with elegant solutions. Simplicity is not merely a minimalist style or the removal of clutter. To be truly simple, you have to go really deep.
OverviewThe Product Owner role came at the wrong moment. I was exhausted, the company was going through significant changes following the strategic partnership with Haven Ventures, and the environment was becoming increasingly difficult. Expectations kept rising while resources stayed the same or diminished. I took the role anyway and gave it everything I had.
In this role I led a cross-functional team of seven people spanning design, development, business analysis, and scrum. Without formal HR responsibility, I contributed to performance feedback and shaped how the team worked together day to day.
Looking back, I am proud of what I contributed. CtrlChain was never just a job to me. I was part of the first group of people who believed in something bigger than what we had, and that is something I will always carry with me.
HighlightsEcosystem Mapping and Three-Layer Model
Defined the strategic model for how CtrlChain could scale through network effects. The model was built around three layers: an Open Space for broad, decentralised participation whose primary value was the data it generated at scale; a Control Space for organisations requiring quality guarantees and compliance; and a Managed Transportation layer where participants could hand off fulfillment directly to CtrlChain at a premium price point.
RBAC Revamp
Evolved the original access control system in two meaningful ways: introduced self-service permissions management for customers operating in the Open Space, and implemented data visibility rules so internal users only saw the data relevant to their specific context rather than everything.
OverviewThis was the sweetest period at CtrlChain. We were growing fast, adding talent, shipping faster, and expanding into Spain and the United States.
During this time, I owned the requirements across product development and operations, translating commercial goals into shippable parts of the product.
HighlightsPivot to Full Truck Load
Led the transition from parcel courier services to Full Truck Load, driving 175% revenue growth in under three years.
Booking Flow Redesign
Incrementally redesigned the booking experience to support recurring requests, refrigerated transport, and full truck load bookings, resulting in faster booking times and lower error rates.
Carrier Onboarding and Vetting
Built the framework for how we onboarded and monitored carriers, giving the operations team the data they needed to make informed decisions and ensuring only qualified carriers received orders.
Role Based Access Control
Defined the core user roles for both internal teams and external users, translating how the business actually operated into a set of specific permissions within the platform.
OverviewI joined what would become CtrlChain at the absolute beginning. Back then, there were no defined processes, no clear value proposition, and we hadn't even settled on an identity. In fact, we were trying to be three different companies at once: ChainCargo, ChainRoute, and ChainCode. Our ambition was huge, but we were still figuring out our actual direction.
Most of our early days were spent searching for product-market fit. That turned out to be a lot harder and took much longer than any of us expected. Because we didn't have established roles or structures, I ended up doing a bit of everything, helping out across the entire business.
What started as a standard nine-month internship turned into something much longer. I realized the problem CtrlChain was trying to solve was real, and it was a problem worth sticking around to fix.
HighlightsRoute Optimisation Engine — Technical Proof of Concept and Investor Pitch
During my internship, I used my Bachelor's thesis to build a technical proof of concept for CtrlChain. The goal was to prove to early investors that we could actually build our own route optimization software, and the thesis gave our pitch the technical credibility it needed to succeed.
The work was about taking an existing algorithm called Ant Colony Optimisation and adapting it for real logistics. The original algorithm solves a simpler problem: visit every city once and find the shortest route back. We had to make it work for couriers handling multiple simultaneous orders, which meant adding five practical rules: start where the courier actually is; only go to a delivery point after picking the goods up first; finish every task in an order once you've started it; end the route at the courier's desired destination, for example their home; and relax the one-visit-per-node rule when real scenarios made that impossible. We called the result the ChainCargo Ant System.
The thesis also mapped out the three core problems the platform would need to solve, which fed directly into the early investor pitch materials.
Parcel Tracking MVP — Requirements Engineering & Delivery
With very limited resources and time, helped define and ship a minimal mobile app to track parcel deliveries in real time. Working closely with the dev lead on technology decisions and managing a junior developer directly, we went from nothing to a production-ready app in under a week.
The app was deliberately stripped down to only what mattered: driver login, real-time location tracking powered by Hypertrack, and a simple set of buttons for drivers to log timestamps against key delivery milestones.
The app was shipped and used in production by suppliers and customers.