Story
My story
This is not a CV. It is a path through manufacturing, sales, company management and systems created from real problems.

How I got into manufacturing
I entered manufacturing through real orders, people, deadlines and everyday decisions. Very early on I understood that a company does not work according to the org chart. It works according to how information, responsibilities and decisions move through it.
What sales taught me
Sales taught me to listen to the customer, but also to understand what happens behind every promise a company makes. Each order has to move through production, warehouse, logistics, service and people. When these worlds are not connected, even good sales create pressure and chaos.
What I understood while managing companies
While managing companies I saw how quickly growth can outgrow the current way of working. Suddenly there are more people, exceptions, orders and decisions. Without a simple system of work, the owner or management starts holding too many things in their head.
Why I became interested in systems
Systems did not interest me because of technology itself. They interested me because I repeatedly saw the same issue: Excel, emails, phone calls and duplicate data entry slowly became the unofficial operating system of the company.
Why Flowlizard was created
Flowlizard came from the question of what a simpler operational flow for manufacturing and distribution companies could look like. Not another heavy ERP, but a practical system that follows the real flow of orders, production, warehouse, logistics, tasks and people.
What I do today
Today I help companies look at how they work from the outside, name the chaos and find a simpler way of working. Sometimes the result is a better process, sometimes a system, sometimes clearer responsibilities. The goal is always the same: to make the company work with less friction.
What this looks like in practice
I recently worked with a client who runs an e-shop and also manufactures custom products to order. Custom orders came in by email, and orders from the e-shop landed in the system incomplete. To handle this at all, the company employed four people in back office whose only job was checking the paperwork and manually re-entering it, first into their own system, then into the supplier's.
We built a process where data entry moved directly to the customer, and all the data connected through an API straight to the supplier's system. Less time, lower costs, and far fewer faulty orders. This is exactly what my work looks like today.