Incidents and fixes
Problems are investigated from the logs, traced to a cause and fixed, with a controlled release and a note of what changed.
Software that runs a business needs someone looking after it. We investigate incidents, fix what breaks, keep dependencies current and plan improvements, under a support arrangement that sets out who does what and how quickly.
Problems are investigated from the logs, traced to a cause and fixed, with a controlled release and a note of what changed.
Frameworks, libraries and platforms move on. Regular updates keep the application secure and supportable.
Small changes and new features are prioritised with you and released on a steady rhythm.
A clear support arrangement defines responsibility, response expectations and the next improvement priorities.
Discuss a support arrangementScope, price and timing are agreed for each project after we understand the work.
We review the code, the hosting and the history before taking responsibility for it.
Coverage, response expectations and priorities are written down.
Monitoring, updates and fixes follow a regular rhythm.
We look back at what happened and agree what to improve next.
Yes, after a review. We need to understand the code, the hosting and the known problems before agreeing what we can take on and how.
Response expectations and coverage hours are agreed for each engagement, based on how critical the system is to your operation.
No. Most arrangements include updates and time for small improvements, so the system keeps getting better instead of only being kept alive.
Tell us what you’re building, changing or figuring out.