Maintenance & support
Someone answers when it breaks, and somebody is watching so that it breaks less. Launch is the start of an application's life, not the end of the project.
Contact Us
What happens to unmaintained software
It does not stay still. Dependencies accumulate known vulnerabilities, browsers and mobile operating systems change annually and break things that worked, certificates expire, and the business it was built for moves on until the software describes a company that no longer exists. None of this is dramatic on any given week, which is exactly why it is neglected. Then something urgent arrives, and the work that should have been an afternoon has become a project because the application is four years behind on everything.
What maintenance actually covers
Security patching and dependency updates on a regular cadence, applied and tested rather than listed in a report. Monitoring with alerts, so an outage is noticed by us rather than reported by a customer. Bug fixing on an agreed response time, by severity. And iteration, which is the part companies underestimate. Every application generates change requests once real people use it through a full business cycle. Budgeting for that up front is the difference between software that keeps fitting the business and software that slowly stops being used.
Including software we did not build
We take over applications built by other suppliers, which usually happens when the original developer became unavailable or stopped responding. We start by reading the code and documenting what exists, because that documentation frequently does not. We will be straightforward about what we find, including when the honest answer is that a rewrite would cost less than continuing to maintain it. That is not the answer we prefer to give, but it is occasionally the true one and you are better off hearing it early.
What you get
Patching on a cadence
Security and dependency updates applied and tested regularly, not listed in a report nobody actions.
We notice before your customers
Alerting on uptime and errors, so an outage is something we are already working on when you hear about it.
Agreed response times
By severity, written down. A production outage and a cosmetic bug are not the same thing.
Budget for change
Every application generates change requests once real people use it. Planning for that is what keeps it in use.
Including software we did not build
We read the code and document what exists, because that documentation frequently does not.
An honest verdict
Including when a rewrite would cost less than continued maintenance. Better to hear that early.
Technologies
Frequently asked questions
How is maintenance priced?
Usually a monthly retainer covering patching, monitoring and a bank of hours for fixes and small changes, with larger work quoted separately. The retainer is sized on the application rather than applied as a blanket percentage of the build cost.
Will you maintain an application you did not build?
Yes, and it is common. We begin with a review of the code, dependencies and deployment, which produces documentation that often did not previously exist. You get that review regardless of what you decide afterwards.
What if nothing goes wrong in a month?
Then the patching, dependency updates and monitoring still happened, which is precisely why nothing went wrong. Quiet months are the product working, not the service being unused.
Stop finding out about problems from your customers
Contact UsGet Free Estimation
Have a question or want to discuss a project? We'd love to hear from you. Get in touch and we'll respond as soon as possible.
Contact Information
Fill out the form and our team will get back to you within 24 hours.
Location
Serbia