Support and Maintenance en Manchester
How we work in Manchester
In the first week we fix nothing
It goes entirely on being able to go back: a full backup off the server, a restore tested on a separate environment and somewhere to reproduce changes before they go up. Touching production without ever having restored a backup is the quickest way to turn a small problem into an expensive one.
What is actually running and what is being paid for
An inherited project nearly always has scheduled jobs nobody remembers creating, third-party services billing a card that nobody uses and versions out of support. It all gets listed with its date and its cost. More than once, the first maintenance payment is covered by what gets cancelled.
We do not sign for what we cannot restore
If there is no way to reproduce the environment or bring the site back from a backup, maintaining it would mean charging for a promise we cannot keep. In that case we say no, or propose a piece of work first so that we can say yes. It is the awkward conversation that prevents the disaster six months out.
Stabilise first, improve later
The temptation with someone else's code is to rewrite it in the first month. We do not: first we stop what is breaking, update whatever carries a security risk and write the documentation that never existed. The big changes come once we know what depends on what, which is almost never what it looked like.
Answering your questions
What people ask us about Support and Maintenance in Manchester.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs