Koch is German for cook

My last name is Koch. In German, that is simply the word for cook. Translate it, and Sebastian Koch becomes Sebastian Cook, which is exactly where the name of this site comes from.

The kitchen metaphor stuck around, because it fits the work better than I expected: figure something out once, test it properly, then write down the recipe so the next person can follow it without the detours.

I am Sebastian, an industrial engineer by training and a consultant by trade, based in Munich. I studied Wirtschaftsingenieurwesen in Bayreuth, which is a long German word for someone taught to sit between engineering and business and translate one into the other. That is still what I do most days.

I am, happily, a bit of a generalist. Jack of all trades, master of none, but as the rest of that saying goes, oftentimes better than a master of one. In a given week I might sketch a solution architecture, wire up a Power Automate flow, write a plugin or a piece of form JavaScript, untangle a consent model, and then stand at a whiteboard arguing about strategy. I like the range. The common thread is that I look at the whole process, not just the screen in front of me.

My home base is the Microsoft Power Platform and Dynamics 365, from model-driven apps and Dataverse to Copilot Studio. Where I currently go deepest is marketing automation with Customer Insights - Journeys: consent, double opt-in, real-time journeys, and the custom tables, plugins and flows that make it hold up in production and under GDPR. Depth where it counts, on a base that stays broad.

Before consulting I spent a lot of time in student initiatives and case competitions, including winning the finals of Germany's largest student case study competition with my team. That taught me two things no certification does: how to think under pressure, and that the best solutions get argued out with good people, not handed down.

This site is my cookbook. Recipes from real projects: practical Power Platform and Dynamics 365 patterns, the consent and compliance details most people skip, how I put AI to work without cutting corners on data protection, and the traps that cost me hours so they cost you less. Some posts are deep dives, some are quick notes. All of them come from something I actually had to solve.

Digitization is tactical, transformation is strategic.