Practical software engineers
We find solutions that fit the exact business case and hold up in daily use — based in Germany, working in English and German, with clients across Europe and the US.
Let's talk →A small team with a practical approach.
Yes, we're newer than the big agencies you've probably talked to. We think that's an advantage — you deal directly with the people writing the code, in English or German, not a rotating cast of account managers. Here's how we actually work.
Principles that guide our engineering work.
These principles shape the way we think, plan and build. They help us stay focused on what matters and deliver software that creates real value.
The people behind Found Key
From paddock to the codebase
I started as a motorsport journalist — making TV programs about karting and racing events alongside PR and media for drivers and teams. That work put me in the same room with some of the most successful drivers at every stage of their careers. Our crew interviewed Max Verstappen before he became famous, we supported Robert Shwartzman’s path through his early years and had programs involving Michael Schumacher. I was able to see the difference — how professionals prepare for their events and how much of winning is organization, not mythical talent.
In parallel with that I raced myself in Esports and on real karting tracks. I tried to recreate those organizational approaches on my own path. It led me to participating at a few European LAN events and I made it to a bootcamp with a real Formula 1 team at Silverstone. Organizing online championships and events myself was also an interest of mine, but there were no decent tools at the time, so I invited a few talented software developers and engineers who were in love with the world of motorsports as much as I was, and we built them.
We faced a lot of challenges along the way — matters of workflows, data, coordination, and we learned how to deal with them and to align the development processes with our goals. Over the years our team grew into a network of 30+ specialists in different areas, and eventually into Found Key Solutions. The vision hasn’t changed since the paddock days: preparation beats improvisation, tools should serve the people doing the work, and a small motivated crew outperforms a big indifferent one.
Built by hand, understood to the end
My path into development didn’t start with a career calculation — it started with curiosity. I like taking technology apart to see how it works, and building working solutions with my own hands. Over time that curiosity turned into a habit of depth: if I take on a problem, I follow the understanding all the way down instead of stopping at the first answer that compiles.
That same habit shapes how I choose tools. Years of practice convinced me that technology should be applied where it fits — not because it’s fashionable or “how it’s done.” I deliberately avoid, for example, introducing microservice architecture into projects that don’t need it yet: complexity for its own sake slows development and multiplies risk. My priority is simple, resilient solutions that grow with the project rather than weighing it down from day one.
At Found Key I run the internal side of the company — engineering processes, the tech teams, and the paperwork that keeps everything solid — so that what we promise on this site is exactly what gets delivered.
How we work
We follow a clear process to turn complex problems into practical, valuable software. Here's our journey together from start to finish.
Who we work with
We tend to work well with people who:
How do we start
An introduction call never hurts. Let's have a conversation!
Let's talk →