Fractional CTO & AI strategy
I'm Dominik. I help founders and leadership teams decide what to build, how to organise delivery and where AI is worth the investment. I work directly with you and your team, combining commercial judgment with hands-on engineering experience.
You may be hiring your first engineering team, relying on a development partner or trying to turn an AI idea into something useful. I help make the decisions, assign ownership and carry the work forward.
Continuing technical leadership when the business needs clearer priorities, a hiring plan or someone to guide its team and development partners. We agree the decisions I own and how they connect to daily delivery.
Assess a specific opportunity, compare the costs and alternatives, and test whether it is useful enough to adopt. I can work through the technical details as well as the investment decision.
At INFO, I led a 35-person engineering organisation and helped shift the studio toward smaller teams and paid specialist consulting. Today I lead the technical programme for openJII at the Jan IngenHousz Institute. I am also completing an MBA in AI, Data & Analytics at the University of Amsterdam.
Smaller teams, paid specialist advice and client work spanning fractional architecture at Growy, Greenwheels consulting and startup support for ErasmusAI.
Research migration, engineering capacity and practical AI on a platform holding more than 48 million production measurement records in October 2026.
You work directly with me. I can also bring in freelance engineers, designers and DevOps specialists from my network, including people in Croatia, or explore working with an established delivery partner. We choose the support around your needs and budget, with scope and costs agreed separately.
Based in Amsterdam. I take on defined engagements alongside my role at JII, with availability and responsibilities agreed before work starts.
A code review on a small UX change collided with a notebook full of 45,451 free-text plant-science questions. The data made a stronger argument than any hunch could: don’t hardcode what your users call things.
First entry in a recurring short-form series. My second week on the job at JII, I was on a plane to Accra to help train plant breeders, crop physiologists, statisticians and data scientists at the first dedicated photosynthesis hackathon. A few notes on what made it work, on what I learned about training a room full of domain experts, and on what the platform underneath quietly enabled.
