Existing software

When an important system needs to become manageable again.

I assess, stabilize and modernize evolved applications without rushing into a full rewrite and without losing sight of ongoing operations.

A strong fit when …

continued development keeps getting slower or riskier.
bugs, technical debt or missing documentation affect operations.
an existing developer or supplier needs to be replaced.
it is unclear whether repair, gradual modernization or a rebuild is appropriate.

A pragmatic starting point

Technical assessment

Code, architecture, data, operations and critical user journeys are evaluated together.

Prioritized action plan

Risks, quick improvements and larger changes are separated transparently.

Controlled implementation

The system is stabilized step by step without an unnecessary big-bang migration.

Technical fit

Technology is context here

For a takeover, the existing system comes first. I work with what is already there and recommend changes only where they materially improve risk, cost or product quality.

Scope

What I can own

The first objective is not a blind rewrite but restoring the ability to make sound decisions about the system.

Assessment

Bring the codebase, architecture, infrastructure, data and known issues into one shared view.

Risk reduction

Prioritize critical defects, security gaps, fragile deployments and missing safeguards.

Modernization

Renew components gradually, clarify interfaces and reduce technical debt deliberately.

Knowledge & handover

Document decisions and structure the system so it no longer depends on individual knowledge.

Collaboration

Clarity before change

01
Gain access
The system, operations and business requirements are assessed and immediate risks made visible.
02
Stabilize
The most urgent sources of defects and operational uncertainty are reduced in a controlled way.
03
Prioritize
Value, risk and effort produce an understandable sequence instead of a blanket rewrite recommendation.
04
Modernize
Improvements are delivered incrementally and evaluated by their real impact.

Relevant project evidence

More than a service promise.

These projects demonstrate comparable product, integration or operational requirements. Each case only presents what is documented for that project.

Self-developed · 2025

snaby - Baby Album App

snaby - The baby album app for families with Flutter and Node.js. Features: Chronological timeline, family member management, in-app purchases, local authentication and secure photo synchronization.

View case studyWhite-Label Platform · 2021

White-Label Travel App Platform

Multi-tenant Flutter platform for digital travel companion apps in bus tourism. One shared product core creates brand-specific iOS and Android apps through tenants, flavors, dynamic config, build CLI and automated asset, Firebase and native configuration.

View case studyRegional Event Platform · 2022

Oelsnitz-Ticket.de - Event Ticketing

Complete ticketing platform for events in Oelsnitz/Vogtl. with Flutter app, web portal and QR code scanner. Features: E-tickets, wishlist, push notifications, comment system and admin panel.

View case study

Next step

Not sure which category your project fits?

Briefly describe the desired outcome, current state and biggest open question. Technical framing is part of my work.

Describe your project