Ongoing service
Managed Application Care
Someone accountable for your software after it ships.
- Duration
- Ongoing, monthly
- Format
- Support agreement with defined response targets
- Fee
- Scoped after discovery
This is for you if
- A business-critical application has no clear owner now that the project has ended.
- Security patching and dependency updates happen when someone remembers.
- You need a defined response when something breaks at eight in the morning.
This is not for you if
- You need 24/7 follow-the-sun cover — we will refer you to a partner who does that properly.
- The application is due to be retired within the year; spend the money on the replacement.
The problem it solves
Most production incidents are not exotic. They are an expired certificate, a dependency with a published vulnerability, a disk filling up, a job that silently stopped running months ago. All of it preventable by someone paying attention on a schedule.
The value of managed care is not heroics during an outage. It is the outages that never happen because someone was watching.
How it runs
What we actually do
-
Onboard
Runbook, monitoring and alerting review, access and credential hygiene, backup and recovery verification — we test the restore, not just the backup.
-
Operate
Monitoring, incident response to agreed targets, security and dependency updates, bug fixing, small enhancements.
-
Review
Quarterly roadmap review: what broke, what it cost, what we are changing so it stops.
Deliverables
What you receive
Documents you keep, whether or not you continue with us.
- Monitoring, alerting and an on-call process
- Incident response to agreed response and resolution targets
- Security patching and dependency vulnerability management
- Bug fixing and performance improvement
- An agreed allowance of small enhancements each month
- Backup verification and tested recovery procedures
- Operational runbook, kept current
- Quarterly service and roadmap review
What happens afterwards
Care engagements often surface the modernization work worth doing — and because we are the ones being paged, our recommendations tend to be well calibrated.
Questions we are usually asked
Will you support an application you did not build?
Yes, after a short onboarding assessment. Occasionally that assessment concludes the system needs work before anyone can support it responsibly, and we will say so.
What are the response targets?
Agreed per engagement against business impact rather than a generic tier. Out-of-hours and urgent cover are priced separately and explicitly.
Does this include new features?
A defined allowance of small enhancements. Larger work is scoped separately so support capacity is never quietly consumed by a project.
What if we want to bring support back in-house?
The runbook and documentation are written for that from day one. Transition is a contract term.