Clarity before activity
The first task is to understand which decision actually needs to be made.
Jan Paul Buchwald
I have more than 20 years of experience designing and evolving complex software systems. I work at the point where business decisions, product direction and engineering reality have to line up.

Architecture in business context
My work has taken me across complex systems, different industries and organisations at different stages of maturity.
I am hands-on enough to understand the implementation reality, but my role is not to fill a development backlog. It is to help teams frame difficult questions, make sound technical decisions and connect those decisions to product and business outcomes.
Through YOPITER, I take on architecture, AI integration and technical-strategy mandates for established companies and growing technology teams.
Both sides of the table
Alongside consulting, I have co-founded companies, advised early-stage teams and invested in technology ventures.
This changes how I look at architecture. Technical elegance matters, but it has to coexist with timing, capital, organisational capability, product focus and commercial reality.
The same perspective informs YOPITER’s investments: strong technology is most valuable when it is attached to a clear problem and a credible path into real use.
Current roles
Working principles
The first task is to understand which decision actually needs to be made.
Architecture is not a search for a universally correct answer. It is the disciplined handling of consequences.
A decision is only useful if the team can apply it under real constraints.
Recommendations should follow the problem, not a preferred vendor, framework or technology.
Professional background
LinkedIn contains the complete professional history, previous roles and current activity.