Service / CRILOX Solutions
Maintenance & support
Ongoing care matched to the agreed system, response expectations and support boundaries.
Plan this kind of projectProblems solved
Where this work helps.
- Dependencies and compatibility changing after launch
- Small defects and content updates accumulating
- Unclear ownership for monitoring and recovery
Typical deliverables
What may be included.
- Agreed updates and compatibility work
- Monitoring and review cadence
- Scoped defect response
- Maintenance record and recommendations
Delivery path
- 01
Define covered systems and response expectations
Details and acceptance checks are confirmed in the approved scope.
- 02
Agree the maintenance scope separately
Details and acceptance checks are confirmed in the approved scope.
- 03
Review updates and issues on cadence
Details and acceptance checks are confirmed in the approved scope.
- 04
Quote new development outside the care scope
Details and acceptance checks are confirmed in the approved scope.
Support boundary
Maintenance is care, not an unlimited feature queue.
Covered updates, monitoring, compatibility work, response expectations and agreed fixes are defined for the system being maintained. New pages, product features, major redesigns, migrations and third-party costs are new development and are reviewed separately.