01 / SOFTWARE
Extended property management software
Analyzed mature business logic, implemented new workflows and structured the codebase for further development.
PROJECTS / EXPERIENCE
Concrete problems instead of interchangeable technology logos.
Many projects are confidential. We show anonymized technical work and outcomes from projects we have actually worked on without exposing clients or data.
Project experience
Software, data, AI and operations — projects we have delivered and supported.
02 / DATA
Integrated meter data & billing
Connected and validated multiple data sources and energy processes through APIs and traceable handoffs.
03 / DELIVERY
Modernized CI/CD delivery
Turned manual delivery for a shipping company into reproducible builds, tests and releases.
04 / LEGACY
Stabilized legacy PHP
Mapped critical paths, added test protection and restored a predictable change cadence.
05 / AI
Integrated AI & billing workflows
Embedded AI features and billing processes into real product workflows instead of leaving them as isolated demos.
06 / DEVOPS
Built a secure production base
Combined Linux, deployments, monitoring, backups and security signals into a resilient operating foundation.
07 / E-COMMERCE
Built & operated online shops
Set up and customized Shopify, Shopware and WooCommerce shops, connected ERP and data flows and supported reliable operations.
08 / WORDPRESS
Managed multiple WordPress projects
Managed multiple WordPress websites and shops with updates, backups, monitoring, security checks and planned technical improvements.
What we show
Every project starts with an uncomfortably specific question.
- Which change can the team safely ship today?
- Where is data lost or misinterpreted between systems?
- What happens when a deployment or server fails?
- Which technical debt blocks the next useful feature?
Project proof
Work toward outcomes and name limits honestly.
Starting point
Describe the technical context and the real bottleneck.
Decision
Prioritize what must be solved first and what can consciously wait.
Implementation
Improve code, delivery or operations in the right scope.
Evidence
Make the result useful with handover, tests, documentation and next steps.
FAQ
Why no client logos?
- Are these real projects?
- Yes. The examples are anonymized and written so no confidential client information is published.
- Can I discuss a similar situation?
- Yes. The patterns are not a package catalog; they help us recognize a similar problem faster.
- Will you publish named references later?
- Once a client approves a named reference or attributable quote, we will add it transparently.
Next step
Does your project sound like one of these patterns?
Tell us what is not reliable today. We will help you frame the problem.