Software and Application Maintenance
Ongoing upkeep for software that is already live: small fixes, routine checks and minor changes handled on a regular cycle instead of one project at a time, run by GullySystem for businesses without an in-house developer.
What Falls Under General Maintenance
Maintenance is different from a new build. It covers the small, recurring work that keeps a live application usable, not a redesign or a new module, but the everyday attention that stops small problems from becoming big ones.
Small Bug Fixes
A form that silently fails for some users, a report that shows the wrong total, a screen that breaks on a particular browser: issues too small for their own project but large enough to annoy customers or staff.
Minor Changes and Content Updates
Updating a price list, adding a field to a form, changing a rule in an approval flow, or swapping a banner image: small requests that arrive every month regardless of what else is happening.
Routine Technical Checks
Confirming certificates have not expired, disk space has not filled up, scheduled jobs are still running, and third-party integrations have not silently stopped working.
Coordinating With Other Vendors
Talking to your hosting provider, domain registrar or a third-party API vendor on your behalf when something on their end affects your application.
Why Live Software Drifts Without Attention
Nothing about a working application stays fixed. Browsers update, a plugin stops receiving updates from its author, a hosting renewal is missed, or a small request sits unassigned because no one owns it. None of this shows up on launch day; it shows up months later.
- A browser update changes how a page renders and nobody notices for weeks
- A plugin or library stops receiving updates from its author
- A hosting or domain renewal lapses because no one is watching for it
- Small requests pile up in a chat thread with no order and no owner
How the Work Gets Organised
A Single Place to Raise Issues
Every request, big or small, goes through one channel instead of being scattered across calls, messages and emails, so nothing gets lost.
Work Ordered by Impact, Not by Order Received
A billing error affecting customers is worked before a cosmetic tweak, even if the tweak was asked for first.
A Monthly Record of What Was Done
A short, plain-language summary of what was fixed, what was changed and what is still open, so you are not relying on memory of a conversation from weeks ago.
Ways This Can Be Structured
Depending on how critical the application is to your business, ongoing maintenance can run as work billed against a fixed monthly allowance, an annual contract, or a support agreement with defined response commitments. The right structure depends on how much risk a delay carries, not on the size of your business.
Who Needs This
Businesses Without an In-House Developer
The application runs the business, but there is no one on staff who can safely touch the code.
Businesses Whose Developer Only Helps Occasionally
Requests get answered eventually, but there is no defined process, no backlog and no accountability for what is outstanding.
Businesses That Want to Stop Firefighting
Every change currently happens as an emergency because nothing is planned or scheduled in advance.
Frequently asked questions
What counts as maintenance rather than a new project?
Maintenance covers small fixes, minor changes and routine checks on software that already exists and is in use. A new module, a redesign or a feature large enough to need its own scope is treated as a separate project, even while maintenance continues alongside it.
What decides how much maintenance costs?
The complexity of the application, the volume of requests you typically raise, and how much capacity you want reserved each month. A simple internal tool needs far less attention than a customer-facing application with integrations.
Do you need access to the original source code to start?
Yes. If a repository exists we ask for access to it; if it does not, we recover a working copy from the live server and rebuild the development environment before any maintenance begins.
Can you maintain an application you did not build?
Yes. Most of the applications we maintain were built by someone else. We read the code, document what we find, and take on maintenance from there.
Who owns the code and hosting accounts once you start maintaining our application?
You do. Repository, hosting, domain and any related accounts stay registered in your business's name throughout the engagement.
What do you need from us to get started?
Access to the code and hosting, a list of the issues currently bothering your team, and one person on your side who can approve changes and answer questions.
What if maintenance reveals the application needs more than upkeep?
We tell you plainly. If the underlying code cannot reasonably support ongoing maintenance, we say so and describe what a partial rework or rebuild would involve, rather than continuing to bill for patches on a failing foundation.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private