← Back to services
Services
System Health Check for business-critical .NET systems
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.
Process
- Kickoff: you show me the system, current problems, and release history. I need access to code, build, and logs. Production access is not required.
- Analysis: I review the build and deployment chain, safeguards, error and crash patterns, dependencies, and how knowledge is distributed across the team.
- Assessment: I classify each finding by outage risk and effort: critical, important, or later.
- Handover: we review the action list together, including the reasoning behind each item.
Result
- A prioritized action list based on the Pareto principle, separated into critical, important, and later.
- Reasoning and estimated effort per action to support budget approval.
- Identification of the areas where an outage would affect operations.
- The list stays with you and can be worked through without me.
Price range
2–3 days · €3,500–€5,000
Fixed price and documented acceptance.
Who it is not for
- Systems without business-critical operations: if an outage holds nobody up, the effort is not justified.
- Greenfield projects and new builds: there is no existing system to assess.
- Systems outside the .NET ecosystem. The findings come from working on .NET systems, not from a generic checklist.
How ready is your system for the next release?
The assessment classifies release risks in your business-critical software as stable, elevated risk, high risk, or critical.
Start Release Risk Check →