Diagnose, prepare and review.
Describe the impact and a repeatable example. Review the relevant modules and dependencies. Prepare the agreed correction or upgrade path. Run the selected checks and review the result before live action.
Define ongoing care separately.
A completed repair does not imply unlimited future support. Agree the systems covered, access, response arrangements and change process. Managed operations may suit an ongoing requirement; a bounded engineering engagement may suit a specific issue.
Useful questions, answered.
No. Start with the version, symptoms and a redacted example. Access can be arranged through the agreed process.
Source, licence and dependency review come first. The proposal should identify what can be retained, changed or replaced.
Explain the impact on your team.
Request a scoped assessment . Existing customers: Customer support .