Launch day feels like the finish line for a software project. In reality, it's the start of the software's working life — which may last many years. During that time, users find bugs, the business changes, phones and browsers update, security issues are discovered in underlying components and data grows. Software that isn't looked after slowly becomes unreliable. Planning support and maintenance from the start keeps your investment healthy.
What maintenance covers
Bug fixes
Every software system has bugs that only appear with real use: an unusual data combination, a rarely used screen, a specific phone model. A clear process for reporting, prioritising and fixing bugs keeps users confident in the system.
Security and platform updates
Applications are built on frameworks, libraries, databases and server operating systems that receive security updates. Applying them regularly — and testing that nothing breaks — is essential. Ignoring updates for years makes eventual upgrades much harder and leaves known vulnerabilities open.
Mobile platform changes
Phone operating systems and app stores change requirements regularly. Apps need periodic updates to stay compatible, meet store policies and work well on new devices.
Monitoring and backups
Someone should be watching that the application is up, responding quickly, not running out of disk space and that backups are running — and occasionally test that backups can actually be restored.
User support
Users need help: forgotten passwords, how to do something, unexpected behaviour. Some of this is handled by an internal administrator; some needs the developer.
Small enhancements
Once people use the system, they find small improvements: an extra field, a new report filter, a changed notification. These keep the system aligned with the business.
Performance and data growth
As data grows, some screens and reports may slow down. Periodic review of performance, database optimisation and archiving old data keep the system responsive.
Severity levels and response times
Agree in advance how issues are classified and how quickly they're handled. A simple scheme:
- Critical — system down or a core process blocked for many users.
- High — important feature not working, with no workaround.
- Medium — feature not working correctly, workaround available.
- Low — cosmetic issues or minor inconvenience.
Each level has an agreed response and target resolution time.
Releases and testing
Changes should go through a staging environment where they're tested before reaching users. Regular, small releases are safer than rare, large ones. Release notes tell users what changed.
Ownership and access
Make sure your business owns or controls the hosting account, domain, app store accounts and source code repository, with the developer given access. Keep a record of where everything is and who has access. If the relationship with your developer changes, you remain in control.
Documentation
Good documentation — how the system is deployed, how it's configured, key business rules, integration details — reduces dependence on individuals and makes support faster. Ask for it to be kept up to date as part of maintenance.
Structuring a support arrangement
Common approaches include:
- Support retainer or AMC — a regular arrangement covering maintenance, updates, monitoring and a set level of support.
- Bank of hours — a block of hours used for support and small enhancements.
- Per-request — each request estimated and approved separately.
Many businesses combine a retainer for maintenance with separately planned enhancement phases.
Planning a roadmap
Keep a list of improvement ideas from users and management. Review it every quarter or half year, prioritise based on business value, and plan enhancement releases. This keeps the system evolving rather than stagnating.
Signs maintenance is being neglected
- Users avoid certain features because they're unreliable.
- Nobody knows when the last backup was tested.
- Frameworks and servers are many versions behind.
- The mobile app has warnings in the app store.
- Small changes take a long time because the code is hard to understand.
An example
A service company had a custom app built several years earlier and no maintenance arrangement. Over time, the technician app started failing on newer phones, reports slowed down and an outdated framework needed urgent security updates. Catching up took far more effort than regular maintenance would have. Afterwards, the company set up a monthly maintenance arrangement covering updates, monitoring, backups and a small bank of hours for improvements, and planned two enhancement releases a year.
How we help
Corposol supports the custom software, web apps and mobile apps we build with ongoing maintenance and enhancement arrangements. Talk to us about keeping your application healthy.
An internal owner for the system
Every business system benefits from an internal owner — someone who understands how the business uses it, collects feedback, handles basic user questions, approves changes and is the main contact for the developer. Without one, requests arrive from many people with conflicting priorities, and nobody decides what matters most.
Budgeting for maintenance
Treat maintenance as a normal running cost of the system, like servers and licences, rather than an unexpected expense. Planning it in the annual budget avoids the situation where necessary updates are postponed until they become urgent and expensive.
Frequently asked questions
Why does custom software need maintenance if it works?
Because the world around it changes: phone and browser updates, security patches for frameworks and servers, new business needs and growing data. Without maintenance, working software gradually becomes fragile.
What's the difference between support and enhancements?
Support covers keeping the existing software working — fixing bugs, applying updates, helping users. Enhancements add new features or change behaviour, and are usually planned and estimated separately.
How quickly should issues be fixed?
It depends on severity. A system-down issue needs immediate attention; a cosmetic issue can wait for the next release. Agree severity levels and response times in advance.
Do mobile apps need regular updates?
Yes. App stores and phone operating systems change their requirements over time, and apps that aren't updated may stop working well or be removed from stores.
Who should own hosting and app store accounts?
Ideally your business, with the developer given access. This keeps you in control if the relationship changes.
