On this page
What long-term maintenance is
Long-term maintenance is an ongoing retainer that combines the routine care every system needs: updates, security patches, monitoring, backups, small changes and support when something goes wrong. Instead of arranging each piece separately, or calling someone only in an emergency, you have one agreement and one team responsible for keeping everything healthy.
The benefit is predictability. A fixed monthly arrangement replaces surprise invoices, and problems are prevented on a schedule instead of fixed under pressure. Just as importantly, the same engineers stay with your systems over time, so knowledge about how they work, and why past decisions were made, builds up rather than walking out of the door with each change of developer.
Who it’s for
Any business that expects to rely on its software for years. A clinic with a custom patient portal, an e-commerce store with integrations to payment gateways and couriers, a real estate company with a listings platform and CRM sync, a SaaS startup that wants a dependable engineering partner, or a manufacturer whose web systems connect to an ERP.
It is especially useful when:
- The original developer or agency has moved on.
- You have no in-house engineers, or they are focused on new features.
- Past problems were only found when customers complained.
- Maintenance costs have been unpredictable, arriving as emergency invoices.
- The system is important enough that downtime directly affects revenue or operations.
What a retainer typically covers
The scope is written down so both sides know exactly what is included. A typical retainer brings together:
- Website Maintenance and Server Maintenance on a fixed cycle.
- Security Updates, with urgent patches out of cycle.
- Application Maintenance to keep frameworks and libraries current.
- Performance Monitoring and uptime alerts.
- Backup checks with periodic restore tests.
- Bug Fixes and small changes within an agreed allowance.
- Technical Support with agreed response times.
- A regular report and a periodic review of priorities.
How the retainer works
- Assessment. We review your systems, hosting, code, backups and documentation, and identify anything urgent.
- Written scope. We agree what is covered, how often, response times, and how larger requests are handled.
- Stabilise. Any catch-up work — overdue updates, broken backups, missing monitoring — is done first.
- Routine cycle. Scheduled maintenance, monitoring and support run month to month.
- Review. We meet periodically to look at reports, upcoming end-of-support dates and your plans, and adjust the scope if needed.
Planning years ahead, not weeks
A long-term view changes how decisions get made. Frameworks, runtimes and operating systems all have published support lifecycles; APIs from payment gateways, CRMs and messaging platforms get new versions and retire old ones. With a retainer, those dates go on a roadmap and are handled in planned steps, spread across months, instead of arriving as a crisis. The same applies to capacity: monitoring data shows when growth will need more resources, well before it does.
What affects scope and cost
The retainer depends on the number and complexity of systems covered, the hours and response times of support, the allowance for small changes, and the current condition of the systems. A well-built, up-to-date system needs less ongoing work than one that has been neglected. Larger projects, such as a major new feature or a platform migration, are scoped separately so the retainer stays predictable.
Most retainers start with a stabilisation period, because systems that have gone without regular care usually carry some backlog: overdue updates, missing monitoring or backups that have never been restored. Once that is cleared, the routine work tends to settle into a steady, predictable pattern, and the time saved on emergencies can go towards improvements instead.
Common mistakes
- Budgeting for the build but not for the years of running it afterwards.
- Agreeing a retainer without a written scope, leading to disputes about what is included.
- Paying for maintenance but never receiving or reading reports.
- Letting the retainer cover only one layer — the website, for instance — while the server and integrations go unattended.
- Choosing a provider who keeps credentials and documentation to themselves, making it hard to ever change.
Our maintenance and support guide goes further into planning ongoing care, and the full range is on our Maintenance & Support page. For infrastructure automation alongside maintenance, see DevOps. When you are ready, contact us to discuss a retainer.
Frequently asked questions
What’s the difference between a retainer and paying per job?
Paying per job suits occasional needs but means problems are usually found late. A retainer covers preventive work on a schedule, gives you agreed response times and makes costs predictable.
Can the retainer cover systems another company built?
Yes. We start with an assessment and any catch-up work needed, then move to the regular cycle once the systems are stable and documented.
What happens with requests outside the scope?
Larger requests are scoped and quoted separately, and you approve them before work starts, so the retainer itself stays predictable.
Can the scope change over time?
Yes. We review the retainer periodically and adjust it as your systems, usage and business priorities change.
Do we keep ownership of our code and access?
Always. Your code, servers, domains and accounts remain yours, and documentation is kept so you can move to another provider if you ever choose to.
Talk to us about long-term maintenance
An ongoing retainer that keeps your systems working years after launch day.