Practical engineering, not hype

Delivery, architecture, and the parts that have to keep working long after launch.

My background is in product management and information systems, and before Aiki Labs I spent four years at a medical device manufacturer, two of them running its Pimcore instance along with the DAM, CRM, and translation workflows around it. That shaped how I approach every project: understand how the operation really works first, then design a system people can trust, maintain, and use day to day. At Aiki Labs I own how projects are structured and delivered, from early process mapping through build decisions to long-term reliability. We use AI where it genuinely removes work, but the goal is always software that still holds up in real operations long after the first demo.

Discovery, scope, and the client relationship from the first call on.

My job is to make sure we are solving the right problem before anything gets built. I spend most of my time talking to clients and understanding how their work actually happens day to day: what slows things down, what is messy, and what could work better. It is easy to build something that looks impressive and helps no one, so I keep us focused on what is genuinely useful. I also look after growth and the client relationship, so working with us stays clear and straightforward from the first message to delivery.