Managed support pricing
For maintaining, supporting and improving live applications within an agreed service boundary and operating rhythm.
Pricing factors made visible
We use the information available to document a defensible quote. Where uncertainty remains, the assumption and its effect are stated instead of hidden.
What shapes the commercial proposal
- Applications and environments covered
- Service window and response expectations
- System complexity, risk and current condition
- Planned maintenance and improvement capacity
What the proposal defines
- Defined coverage and request channels
- Incident priorities and response targets
- Maintenance, release and reporting rhythm
- Escalation paths and service responsibilities
Major enhancements, unplanned migrations and work outside the agreed service boundary require separate approval or a revised support plan.
Understand the model before committing
No. The retainer covers the applications, service expectations and capacity defined in the proposal. Larger changes are estimated and approved separately.
Where appropriate, the proposal defines service hours, incident priorities, response targets, dependencies and exclusions. Resolution times depend on the issue and agreed support boundary.
Yes, after an assessment of the codebase, environments, documentation, security, operational risks and handover needs.