Stabilize legacy systems.
Keep production running.
Stabilize business-critical .NET systems.
At fixed prices, without rewriting or downtime.
Symptoms & Root Causes
When releases become a risk.
Typical warning signs in business-critical legacy systems. They show up before a team starts postponing releases because the next deployment feels too risky.
Release risk: high
- Telemetry 01 Slow Feedback
4h
Full Build & CI Duration
Every hotfix waits at least four hours for the pipeline. If a run fails, the wait starts over. The team only finds out hours later whether a change works.
- Pipeline throughput
- Bottleneck
- Telemetry 02 Heavy Coordination
2× / Year
Release Cadence
Every deployment needs sign-off from several sides, a maintenance weekend, and often a night shift. With six months between releases, six months of changes go live at once.
- Deployment batch size
- 6 Months of Changes
- Telemetry 03 Blind Spot
Unknown
Actual Test Protection
The unit tests pass on the build agent. Whether they catch the defects that show up in production, nobody on the team can say for sure.
- Automated safety net
- Unverified
- Telemetry 04 Bus Factor = 1
1 Person
Deployment Knowledge
Which configuration goes where, and in which order things get deployed, is known to one person on the team or to a former supplier. When that person is on vacation, the release waits.
- Deployment backup
- None
- Telemetry 05 Direct Cost
€50,000/h
Average Downtime Cost
When a business-critical system goes down unexpectedly, orders and customer requests pile up. The cost keeps running until the fix has made it through the pipeline and into production.
- Earliest fix live
- After 4h Pipeline
- Telemetry 06 No Fallback
0 Rollback
Tested Rollback
There is no tested way back to the last working version. When a release fails, the team patches directly in production. Nobody can say in advance how long that will take.
- Mean time to recovery
- Unpredictable
How long does a hotfix take in your team, from commit to production?
In the System Health Check, I go through that path with you in 2–3 days: build and deployment chain, tests, dependencies, and who on the team knows what. You get a prioritized action list. I don't need access to your production environment.
How I work
Fixed price with a clear scope
You know in advance how much it costs and what you're getting. No open-ended engagements or hourly billing.
Responsibility for the outcome
I take responsibility for my work. You receive an acceptance record. If something is not the right fit, I will say so.
Working with your team
I share knowledge from day one. After the project, your team can continue working independently.
From diagnosis to stable production.
System Health Check
I analyze your business-critical system and prepare a prioritized action list using the Pareto principle: critical, important, and later. The list supports budget decisions.
Learn more →Request System Health Check →.NET Legacy Stabilization
I stabilize your system step by step during ongoing operations, improve build, test, and deployment processes, and reduce crash and error rates. I share the knowledge with your team so they can continue independently.
Learn more →Discuss stabilization →Future Readiness
Once the system is stable, I prepare it for Industry 4.0: OPC UA integration, Asset Administration Shell (AAS), and technical preparation for regulatory requirements such as the Digital Product Passport (DPP).
Learn more →Fixed price and documented acceptance.
I take responsibility for the result and speak openly when something is not the right fit.
Results from project work.
Oliver Fries
I have worked with .NET systems for more than 14 years, including research at Fraunhofer, enterprise environments at Miele, and analytics at OPTANO.
I care about keeping systems reliable in day-to-day operations, including when changes are needed.
I work directly with the teams responsible for these systems and implement changes alongside them.
I stabilize existing systems and share knowledge with your team so they can continue independently. I am open about what is feasible and where the limits are.
How ready is your system for the next release?
18 diagnostic questions. 6-9 minutes. Clear risk classification.
The assessment carries no obligation.
The assessment classifies release risks in your business-critical software as stable, elevated risk, high risk, or critical.
Start Release Risk Check →No account needed. Diagnostic report by email.
Let’s talk.
In a free 30-minute introductory call, we can discuss current problems with your system or how to keep it stable as it develops.
Free and without obligation.