Software Maintenance and Support

Software maintenance and support for systems you inherited or have run for years. We review the code first, then keep it secure and current with updates, bug fixes and performance work, and replace outdated parts without stopping the business.

Tell us about your project

Our work

What's included

Code Audit and Handover

A review of the source code, dependencies, servers and access, with a written report of risks and priorities.

Security and Dependency Updates

Regular updates to frameworks, libraries and packages, tracking of known vulnerabilities and keeping up with App Store and Google Play requirements.

Bug Fixes and Small Improvements

Reported bugs resolved in order of priority, with small change requests planned and released in the same routine.

Performance Work

Slow pages, queries and screens measured, and their bottlenecks found and removed.

Gradual Modernisation

A strangler fig approach that replaces the old system piece by piece instead of one big rewrite, with old and new running side by side during the transition.

Documentation and Tests

Setup, release and architecture docs plus automated tests on critical flows, so changes are safer and a new developer can learn the system from the docs.

Questions

Will you maintain software another company built?

Yes. We first review the source code, dependencies, servers and access and share a written assessment. Once it is clear what needs fixing now and what can wait, we take over the maintenance.

Should we rewrite our software or modernise it?

A full rewrite risks losing business rules buried in the code over the years; you also have to keep the old system going until the new one is ready, and the switchover becomes one risky step. We usually recommend pinning down current behaviour with tests and replacing old parts one at a time, and we say so plainly when a rewrite is the better choice.

How much does software maintenance cost?

Ongoing maintenance runs as a monthly support package sized to the scope and the system. Larger work such as a modernisation is planned as a separate project, at a fixed price or on a monthly retainer, and we share a transparent quote after the first review.

What should a software maintenance agreement include?

What is in scope, bug priority levels and the response time for each, the monthly capacity set aside and how out-of-scope work is priced. It should also state that the source code and access belong to you; our guide to software development contracts covers the other clauses worth checking.

Can an old mobile app be kept up to date?

Usually, yes. Moving to current SDKs, updating dependencies and meeting new app store requirements can keep the app live. If the codebase is too old for that, we plan to rewrite its screens gradually.

Are servers and infrastructure included?

Maintenance focuses on the application code. If you also need server setup, deployment pipelines, monitoring or backups, we plan our cloud and DevOps service into the same support package.

Related guides

All articles

Let’s work together.

info@bernsoftware.com Not sure what you need?Plan your project in 10 steps