Web app and SaaS development that doesn't just go live, it carries.
I build web applications and SaaS products from the interface to operations, with ownership instead of task-execution mode, and custom software where standard solutions don't carry.
Don't just look finished. Be built clean, so it carries after go-live.
When standard software doesn't carry.
Custom software isn't worth it on principle, but where standard solutions don't cleanly cover the actual requirements: your own processes, multi-tenant logic, integration with existing systems, a product meant to become a competitive advantage.
When custom software is actually worth it.
Standard software is cheap, available fast, and almost always the right choice for common tasks. It hits its limits where your own process is what makes the business: if you'd have to adapt your way of working to the software instead of the other way around, you give up exactly the difference that sets you apart from competitors.
Custom software is worth it not as a status symbol, but as an investment in an advantage that lasts: a product that mirrors your logic, talks to your existing systems, and grows with you, instead of tying you to someone else's licensing models and roadmaps. The higher upfront effort pays off where the process is core to the business, not at its edge.
What I build.
- SaaS products and web applications from the interface to operations, in one hand
- durable architecture with Python and Django, PostgreSQL, TypeScript, and React
- multi-tenant structures and integration with existing systems
- good decisions early instead of expensive corrections later
- responsibility beyond go-live, so it keeps running without me
First the honest answer, then the build.
Not every project needs a rebuild. Where existing software carries, modernization is often the better and cheaper path. What speaks for it and how it works is covered in software modernization. Where a new build is the right call, I start with an assessment, not with blind scope.
Central recruiting platform for multiple brands
Over roughly four years, architecture, technical leadership, and full-stack development bundled in one point. 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 standard software didn't carry, custom-built applications now run in daily operations.
What matters when building web apps and SaaS.
What does a web application or SaaS product cost?
That depends on the scope and the phase. Instead of a blanket figure, it starts with an assessment: how important is the project, where are the risks, what has to be right early? From that follows a reliable frame, instead of chasing blind scope.
Custom software or standard software?
Standard software is the right choice where it cleanly covers the requirements. Custom software is worth it where your own processes, multi-tenant logic, or a product meant to become a competitive advantage are involved and standard solutions do not carry. Not on principle, but out of necessity.
Which technologies do you build with?
The focus is Python and Django, PostgreSQL, TypeScript, and modern web frontends with React. The technology follows the product, not the other way around; what matters is an architecture that carries later.
Do you also build just individual parts or the frontend?
The value comes when decision and implementation sit in one hand, from the interface to operations. Pure ticket work or an extended workbench is not the model; the collaboration makes sense where direction, responsibility, and durability count.
What is custom software development?
Custom software development means building an application specifically for your own processes, instead of adapting a standard product. Unlike a ready-made CRM or ERP, it maps exactly the logic that makes the business work, talks to your existing systems, and grows with you. Worth it where standard solutions do not carry, not on principle, but because the process is part of the core.
Should your product be built new or modernized?
A first conversation clarifies whether custom development is the right path and how the product is built so it carries.