01 - Product Setup
Setting up a new product cleanly.
With clear direction instead of flying blind and a foundation that carries later. Good decisions early instead of expensive corrections later. Web app and SaaS development.
I work with companies building or repositioning a SaaS product or web application - who need more than pure development delivery.
Not ticket work. Not an extended workbench. But real product work with ownership, judgment, and results built to carry.
01 - Product Setup
With clear direction instead of flying blind and a foundation that carries later. Good decisions early instead of expensive corrections later. Web app and SaaS development.
02 - Product Repositioning
With less downtime, clearer decisions, and more visible progress. Friction out, substance in. Software modernization.
03 - Critical Product Phase
When mere implementation isn't enough and direction, architecture, and durability become decisive. Technical leadership on a part-time basis.
I don't start with blind scoping and a blanket implementation mode, but with a clean assessment of the project. How important is it really? Where are the biggest risks? What needs to be right from the start so nothing has to be painfully reversed later? Where is speed enough - and where does it need judgment?
Only when this clarity is in place do we move to implementation. Together, with clear direction.
Central recruiting platform for multiple brands
Over roughly four years as the responsible point for architecture, technical leadership, and full-stack development. Today a multi-tenant platform that carries several corporate brands.
Applications for the match operations of a Bundesliga club
Ongoing since 2024 - conception, development, and integration with existing systems. Where off-the-shelf software didn't carry, custom-built applications now run in daily operations.
A product partner is worth it when a project matters enough that someone thinks along, sets direction, and takes responsibility, instead of just working through tickets. An agency delivers implementation capacity. This is about product work with ownership: good decisions early, an architecture that carries, a result that holds after go-live.
Many projects lack the person who carries technical direction, architecture, and responsibility in an important phase. That is exactly the role I take on temporarily: not as extra hands, but as technical leadership that owns decisions and keeps the product on course.
No. Windschatten IT does not work in task-execution mode or as an extended workbench. The collaboration makes sense where direction, judgment, and responsibility are needed: in setup, repositioning, or a critical product phase.
The focus is SaaS products and web applications with Python and Django, PostgreSQL, TypeScript, and modern web frontends. The technology follows the product, not the other way around; what matters is an architecture that carries later.
It begins with an assessment of the project: how important is it, where are the risks, what has to be right early? Only once that clarity is in place do we move into implementation, with clear direction instead of blind scope.
Mostly remote, across the German-speaking region (Germany, Austria, Switzerland). The base is Lenting near Ingolstadt; on-site meetings by arrangement.
A first conversation quickly clarifies whether mere implementation is enough - or whether it needs real product work.