Keeping a custom enterprise system running is two contracts, not one. Maintenance keeps the software up to date, meaning security patches, dependency and platform upgrades and compatibility fixes, and costs about 10 percent of the project cost per year as a rule of thumb. Support is coverage for incidents and questions, priced by the hours you want covered: business hours and days with a two-hour critical response at $1,000 (€870, £740) per month, extended business hours with a one-hour critical response at $2,000 (€1,500, £1,500) per month, and 24x7 with a 30-minute critical response and a 100% uptime SLA at $5,000 (€4,500, £3,500) per month as a rule of thumb. Each uptime SLA is backed by a matching disaster recovery arrangement. 7L International offers a free assessment and a quote for both. New features are separate.
Prices are in US dollars. Euro and pound figures in parentheses are approximate, rounded conversions. Quotes are issued in the currency of your contract.
The system goes live, the project team moves on, and the question nobody asked during the build arrives in week two: who do we call, how fast will they answer, and what does that cost. Support is the part of enterprise software that runs for ten years and is discussed for ten minutes. This post explains the difference between maintenance and support, what each one covers and costs, what the support tiers mean in response times and money, and how to read a service level agreement before you sign it. It belongs to our buyer's guide to enterprise software development, and it assumes you have read, or will read, what the build itself costs.
Maintenance versus support: what is the difference?
The two words are used together so often that most buyers treat them as one line item. They are two different services, with different costs, and it pays to contract them separately.
Maintenance is keeping the software up to date. Operating systems, frameworks, libraries, cloud services and the systems you integrate with all change on their own schedules, and a system that is not kept current drifts until an upgrade becomes a project of its own. Maintenance is planned work: dependency upgrades, security patches, compatibility fixes when a browser, a mobile operating system or an integrated system changes, and the annual major upgrades of the platform the system runs on. As a rule of thumb it costs about 10 percent of the project cost per year. A system built for $400,000 (€350,000, £295,000) needs roughly $40,000 (€35,000, £30,000) a year to stay current. The exact figure depends on the stack, the number of integrations and how fast the surrounding platforms move, which is why 7L International offers a free assessment of any system, ours or someone else's, and provides a quote for its maintenance.
Support is being there when something goes wrong or someone has a question. It is reactive work with a clock on it: an incident is reported, a qualified engineer responds within the agreed time, and the issue is resolved or worked around. What you pay for support depends on the hours you want covered, not on the size of the build, because the cost is a rota of engineers who know your system and are paid to be available. We provide support up to 24x7, and the rule-of-thumb monthly rates are in the table below.
| Maintenance | Support | |
|---|---|---|
| What it is | Keeping the software up to date | Responding to incidents and questions |
| Type of work | Planned: patches, upgrades, compatibility fixes | Reactive: diagnosis, fixes, workarounds, answers |
| Priced by | The size and stack of the system | The hours of coverage |
| Rule of thumb | About 10 percent of the project cost per year | $1,000 (€870, £740) to $5,000 (€4,500, £3,500) per month depending on coverage, with a critical response of two hours down to 30 minutes |
| How to get a firm number | Free assessment and quote from 7L | Free assessment and quote from 7L |
Added together, maintenance and support usually land in the 15 to 25 percent of build cost per year that the rest of our buyer's guide uses as the all-in running cost, with small systems at the top of that range and large ones at the bottom, because the support rate does not grow with the build. Infrastructure, meaning hosting, databases, monitoring and backups, is a third line and is billed by the cloud provider.
What does support actually cover?
A support contract covers keeping the system you paid for working as specified, with maintenance keeping it current underneath. In practice that means five things.
- Incident response. Something is broken or down, and someone diagnoses and fixes it within the agreed time.
- Bug fixes. Defects in delivered functionality, found after the warranty period, are corrected.
- Security patches. The operating system, frameworks, libraries and dependencies are kept current, and vulnerabilities are patched when disclosed. This is maintenance work, and it belongs in the maintenance contract.
- Upgrades and compatibility. When a browser, a mobile operating system, a cloud service or an integrated system changes, the application is adjusted to keep working. Also maintenance.
- Monitoring and housekeeping. Uptime monitoring, error tracking, backup verification, certificate renewals, log rotation, database maintenance.
What support does not cover is change. A new report, a new user role, a new integration, a redesigned screen: these are enhancements, priced separately as small projects or drawn from a retained bucket of hours. The line between a fix and an enhancement is the most argued clause in any support contract, so the contract should define it. A fix restores specified behaviour. An enhancement changes it.
What are the support tiers?
| Tier | Coverage | Critical response | Critical resolution | Uptime SLA | Monthly rate |
|---|---|---|---|---|---|
| Basic | Business hours, business days | 2 hours | 1 business day | Best effort | $1,000 (€870, £740) |
| Standard | Extended business hours | 1 hour | 8 hours | 99.9% | $2,000 (€1,500, £1,500) |
| Premium | 24x7 | 30 minutes | 4 hours | 100% | $5,000 (€4,500, £3,500) |
- Basic covers business hours on business days in one time zone. It suits internal tools, departmental systems, and anything where a day of downtime is an inconvenience.
- Standard covers extended business hours, 7am to 9pm on weekdays, plus on-call weekends. It suits core operational platforms, customer portals, and systems with external users in two or three time zones.
- Premium covers every hour of every day of the year. It suits revenue-critical and regulated systems, platforms serving customers globally, and anything with a contractual uptime obligation to your own clients.
These are support rates only. Maintenance, at about 10 percent of the project cost per year, sits on top of them, and so does any retained budget for enhancements. The jump from Standard to Premium is large because a 30-minute response at any hour of any day means a rota of engineers who know your system, paid to be available through nights, weekends and holidays. It is not a switch the vendor flips. If only one component of your system is revenue-critical, ask for Premium on that component and Standard on the rest. Good vendors will do it. The rates above are a rule of thumb: the number of systems, integrations, users and time zones all move them, so 7L International offers a free assessment and provides a quote for the support tier that fits.
What stands behind the uptime SLA?
An uptime SLA is a promise about outcomes, and a support rota on its own cannot keep it. 99.9% allows about nine hours of downtime a year. 100% allows none, which means no single failure may take the system down and any unplanned outage earns a service credit. If a database host dies at two in the morning, the 30-minute response gets an engineer looking, but whether the system is back inside the resolution target depends on what was built before the failure: tested backups, a standby environment, a rehearsed procedure. That is disaster recovery, and each uptime SLA is only credible when the disaster recovery arrangement behind it matches.
Disaster recovery is described by two numbers. The recovery time objective, RTO, is how long until the system is back after a failure. The recovery point objective, RPO, is how much data can be lost, measured as the time since the last usable copy. The table ties both to the tiers, and the RTO mirrors the critical resolution target on purpose: the resolution target is only achievable if the recovery arrangement supports it.
| Tier | Uptime SLA | Disaster recovery arrangement | RTO | RPO |
|---|---|---|---|---|
| Basic | Best effort | Daily backups, restore on request | 1 business day | 24 hours |
| Standard | 99.9% | Backups every few hours, documented restore procedure, rehearsed yearly | 8 hours | 4 hours |
| Premium | 100% | Active-active or standby environment across zones, continuous replication, automatic failover, tested quarterly | 4 hours after a full regional disaster | 15 minutes to 1 hour |
Disaster recovery is infrastructure and architecture, not support labour, so it is not inside the monthly support rate. Backups and a documented restore cost little beyond storage. A standby or active-active environment means a second set of infrastructure, replication and a setup project, which can add 50 to 100 percent to the monthly cloud bill for the components it protects. The uptime SLA in a support contract is conditional on that arrangement being in place, and a vendor who commits to 100% on a system with a single server and nightly backups is promising something they cannot deliver. 7L International assesses the current disaster recovery posture of any system for free and quotes the infrastructure changes alongside the support tier, so the uptime SLA and the architecture are agreed together.
What is the 10 percent maintenance rule?
Over a year, keeping a custom system up to date costs about 10 percent of what the system cost to build. A platform built for $400,000 (€350,000, £295,000) needs roughly $40,000 (€35,000, £30,000) per year in patches, dependency upgrades, platform upgrades and compatibility fixes. Add the support tier you choose, from $12,000 (€10,000, £9,000) to $60,000 (€50,000, £44,000) per year, and the total running cost of the same platform is $52,000 to $100,000 (€45,000 to €85,000, £38,000 to £75,000) per year, which is close to the 15 to 25 percent figure used elsewhere in our guide for total running cost. The low end of the maintenance rule applies to a stable system on a mainstream stack with few integrations. The high end applies to a system with many integrations, each of which changes on someone else's schedule, or to a system on a stack that moves quickly. Well below 10 percent, something is being skipped, usually dependency upgrades, which show up two years later as a security finding or a framework that can no longer be updated. Because the right figure depends on the system, 7L International offers a free assessment and a quote for the maintenance of any system, including ones we did not build. What is technical debt describes the compounding. How much app maintenance costs covers the smaller-product version of the same rule.
What should an SLA define?
An SLA is a list of promises with measurements attached. Read it for the following, and if any is missing, ask for it.
- Severity definitions. What counts as critical, high, medium and low, in terms of business impact, not technical symptoms. "The system is unavailable to all users" is critical. "A report is slow" is not. Both sides should be able to classify an incident in a minute.
- Response versus resolution. Response is when a qualified person starts working. Resolution is when the issue is fixed or a workaround is in place. Many SLAs promise only response. Ask for resolution targets, even if they are targets rather than guarantees.
- Coverage hours and time zone. Business hours in whose business and whose time zone. A vendor in Athens with a client in New York must say what 9am means.
- Uptime measurement. Measured how, over what period, and excluding what. Planned maintenance windows are normally excluded, but they should be bounded and announced.
- Disaster recovery. The RTO and RPO stated in the contract, the architecture that delivers them, who pays for the standby infrastructure, and the date of the last tested restore. A backup that has never been restored is the most common gap in an SLA.
- Escalation path. Who you call when the first line is not solving it, with names and numbers, not a ticket portal.
- Service credits. What happens when the SLA is missed. Credits are usually a percentage of the monthly fee. They are an incentive, not compensation, so do not over-negotiate them. Negotiate the response times instead.
- Included hours. How many engineering hours per month are inside the fee, what happens to unused hours, and the rate for hours beyond them, typically $45 to $90 per hour (€40 to €80 per hour, £35 to £65 per hour) nearshore and $120 to $220 per hour (€105 to €190 per hour, £90 to £165 per hour) onshore.
- Reporting. A monthly report of incidents, response times, uptime, hours used and patches applied. If the vendor cannot report it, they are not measuring it.
- Exit. Notice period, handover obligations, and confirmation that documentation, credentials and infrastructure are yours. MSA, SOW and change requests covers how the support schedule fits with the rest of the contract.
What are the common traps?
- Warranty confused with support. Most builds include a warranty period of 30 to 90 days for defects. That is not support. Monitoring, patches and incidents outside working hours start when the support contract does.
- Support with no monitoring. A vendor who waits for you to report an outage is not supporting the system. Monitoring with alerting to the vendor's on-call should be in every tier above Basic.
- Hours that vanish. Included hours that expire monthly and cannot be pooled turn into a fee for nothing in quiet months. Ask for quarterly pooling.
- Enhancements that drain support. Small change requests consume the included hours, and then an incident has no hours left. Keep enhancements on a separate budget.
- Support sold without maintenance. A cheap support fee with no maintenance behind it means the system is defended but never updated. Within two years the incidents are caused by the drift. Contract both, and make sure the maintenance line is explicit.
- No upgrade plan. Patches without a yearly plan for major framework and platform upgrades means the system drifts until an upgrade becomes a project. Ask for an annual upgrade roadmap inside the maintenance fee.
- Single point of knowledge. One engineer at the vendor knows the system. Ask how many people are trained on it and how handover happens when they leave.
How do you choose the tier?
Price the hour of downtime. If the system is down for a working day, what does it cost in lost orders, idle staff, penalties and reputation. If that figure is under $10,000 (€8,500, £7,500), Basic at $1,000 (€870, £740) per month with a two-hour critical response is adequate. If a day of downtime costs $10,000 to $100,000 (€8,500 to €85,000, £7,500 to £75,000), Standard at $2,000 (€1,500, £1,500) per month with a one-hour response. Above that, or if you have uptime obligations to your own customers, Premium at $5,000 (€4,500, £3,500) per month with a 30-minute response around the clock. Then check the integrations: a system that depends on five external systems will see more incidents than one that depends on none, and the tier should reflect the incident rate as well as the impact. Finally, consider the hours: a system used in three continents needs coverage in three continents regardless of the impact figure.
Before you sign a support contract
- Maintenance and support as separate, explicit lines.
- Severity definitions in business terms.
- Resolution targets, not only response.
- Monitoring with alerts to the vendor, not only to you.
- Included hours pooled quarterly, with a published overage rate.
- An annual upgrade roadmap inside the fee.
- A monthly report you would actually read.
- RTO and RPO in writing, with a tested restore behind them.
- An exit clause with handover.
How 7L runs support
7L International is a custom software development and digital transformation firm with business hubs in New York, London and Athens, which is why our support rotas can cover European and American business hours without a night shift. We contract maintenance and support separately. Maintenance is quoted per system after a free assessment, with about 10 percent of the project cost per year as the starting point, and it includes an annual upgrade roadmap. Support is offered at the three tiers above, from business hours with a two-hour critical response to 24x7 with a 30-minute critical response, and the monthly rates are quoted after the same free assessment, together with the disaster recovery arrangement that backs the uptime SLA. We monitor every production system we support and alert ourselves before the client notices, and our monthly report lists incidents, response times, uptime, patches and hours. Enhancements run on a separate retained budget so support hours are there when an incident needs them. Support is one of the seven things end-to-end has to mean. If you have a system that is live and under-supported, a system someone else built that nobody is keeping current, or a build that is approaching go-live without a support plan, ask us for a free assessment and we will come back with a quote for maintenance, for support, or for both.
Frequently asked questions
What is the difference between software maintenance and software support?
Maintenance is keeping the software up to date: security patches, dependency and platform upgrades, and compatibility fixes when browsers, operating systems or integrated systems change. It is planned work and costs about 10 percent of the project cost per year as a rule of thumb. Support is responding to incidents and questions within agreed times. It is reactive work priced by the hours of coverage, from business hours to 24x7. Contract them as two explicit lines.
How much does enterprise software support cost per month?
As a rule of thumb, $1,000 (€870, £740) per month for business hours and business days with a two-hour critical response, $2,000 (€1,500, £1,500) per month for extended business hours with a one-hour critical response, and $5,000 (€4,500, £3,500) per month for 24x7 coverage with a 30-minute critical response. The rate is driven by the hours covered rather than the size of the build. Maintenance, at about 10 percent of the project cost per year, and any enhancement budget are separate. 7L International offers a free assessment and a quote for the tier that fits.
How much does software maintenance cost per year?
About 10 percent of the original project cost per year as a rule of thumb, covering security patches, dependency upgrades, platform upgrades and compatibility fixes. For a platform built for $400,000 (€350,000, £295,000) that is roughly $40,000 (€35,000, £30,000) per year. The figure moves with the stack and the number of integrations, so 7L International offers a free assessment and provides a quote for the maintenance of any system, including ones built by someone else.
What is the difference between a warranty and a support contract?
A warranty, typically 30 to 90 days after go-live, covers defects in what was delivered, at no extra charge. A support contract covers everything that keeps the system running after that: monitoring, incidents at any hour, security patches, upgrades when platforms and integrated systems change, and bug fixes found later. Warranty ends; support continues for the life of the system.
What is the difference between response time and resolution time?
Response time is how quickly a qualified engineer begins working on an issue after it is reported. Resolution time is how quickly the issue is fixed or a workaround is in place. Many SLAs promise only response, which can mean an acknowledgement within an hour and a fix whenever. Ask for both, with resolution expressed as a target per severity level.
Do we need 24x7 support?
Only if an outage outside business hours costs real money or breaches an obligation to your own customers. For most internal and departmental systems, Basic or Standard coverage at $1,000 (€870, £740) or $2,000 (€1,500, £1,500) per month is enough. If one component is revenue-critical, ask for Premium coverage on that component alone, which most vendors will price separately rather than applying 24x7 to the whole platform.
What is the difference between an uptime SLA and disaster recovery?
The uptime SLA is the promise: best effort, 99.9% or 100% availability, with service credits when it is missed. Disaster recovery is what makes the promise deliverable: backups, a standby or active-active environment, and a rehearsed restore, described by a recovery time objective and a recovery point objective. A support rota cannot keep an uptime SLA on its own, so the two should be agreed together and the disaster recovery infrastructure priced as its own line.
Can our own IT team support a custom system instead of the vendor?
Yes, if the vendor delivers documentation, runbooks, monitoring and a handover, and if your team has the skills for the stack. A common arrangement is first-line support in-house, with the vendor on a reduced retainer for second-line engineering and upgrades. Make sure the contract includes a handover period and that all credentials and infrastructure are already in your name.