Maintain the system yourself, or sign a maintenance contract?
Self-maintenance requires breadth in operations, security, and dependency updates that a small IT department rarely covers in full. A maintenance contract usually costs SEK 10,000–50,000 a month but provides readiness when something breaks. The choice comes down to how critical the system is and what downtime actually costs.
The question comes up only after launch, once the build itself is done and the product has to keep living. Should you maintain the system yourselves or sign a maintenance contract with an agency? The answer decides more than a monthly cost – it decides how long the product keeps working and what happens the day something breaks.
What self-maintenance actually requires
Maintenance sounds like just “keeping the lights on,” but behind that word are several skill sets that need to exist simultaneously. Operations need to be monitored so errors are caught before users notice them. Security needs to stay current – new vulnerabilities keep appearing and need addressing. Dependencies on libraries and third-party services must be updated, or they stop working or become a security risk.
None of this is unreasonable on its own. The problem is the breadth. A small IT department can often handle day-to-day work – a bug here, a change there – but rarely covers the whole spectrum around the clock. The person who knows the system’s code isn’t always the one who knows the server, and the person who knows the server isn’t always awake when the alarm goes off at three in the morning.
Self-maintenance works best when the system isn’t business-critical, when a couple of days of downtime is manageable, and when you have both the expertise and the time internally. That way you avoid a contract you don’t need.
The cost of a contract vs. the cost of an incident
A maintenance contract often lands at SEK 10,000–50,000 a month. Where in the range depends on the system’s size, how critical it is, and what response time you need. A simple, low-risk system sits at the bottom; a business-critical service with a short guaranteed response time and on-call coverage sits at the top.
That figure easily feels like a pure expense – until something breaks. Weigh the monthly cost against what a single serious incident costs without readiness. Downtime in a system that takes orders, a leaked personal-data register, a broken payment flow: things like that can cost more in a day than the contract does in a year, and that’s only counting the direct loss. The trust that’s lost doesn’t show up on the invoice.
The point isn’t that a contract always pays off. The point is that the comparison isn’t between “contract” and “free.” It’s between a known, steady cost and an unknown, uneven risk. The more critical the system is, the more the risk weighs.
Do the math for your own situation
Two questions make the choice concrete. The first: how long can the system be down before it really hurts? If you can handle a full day without losing revenue or customers, you’re in a stronger position going it alone. If every hour is costly, you need readiness.
The second: do you have the internal expertise to solve an error you haven’t seen before, quickly and under pressure? The difference between handling the planned and handling the unexpected is large. It’s in the unexpected that a contract pays for itself.
| Model | Typical cost | Fits when |
|---|---|---|
| Self-maintenance | Internal time | The system isn't critical, expertise is in-house |
| Own first line + an agency backing you up | Lower monthly fee + time | You want to own day-to-day work but have support for serious errors |
| Full maintenance contract | SEK 10,000–50,000/month | The system is business-critical and requires readiness |
The hybrid model that often fits best
The choice is rarely black or white. A common and often wise middle ground is handling first-line support yourselves – daily oversight, simpler cases, the ongoing contact with users – with an agency backing you up for what requires deep technical skill or a fast response. You keep control and knowledge of your own system, but you’re not on your own when something truly serious happens.
At Weapp, we build many of our maintenance setups exactly this way, tailored to how critical the system is and how much you want to own yourselves. Want to work out which level fits your product? You’re welcome to get in touch, or read more about our services.
Frequently asked questions
What's usually included in a maintenance contract?
Ongoing operations and monitoring, security updates, updates to third-party dependencies, bug fixes, and a guaranteed response time when something breaks. Many contracts also include a small allowance for further development. The exact scope varies, so it's important to read what counts as maintenance and what's billed separately.
What does a maintenance contract cost?
A common price range is SEK 10,000–50,000 a month, depending on the system's size, criticality, and desired response time. A simple, low-risk system lands at the bottom of the range, while a business-critical service with a short response time and on-call coverage sits higher. The price reflects readiness, not just the hours actually spent.
Can we maintain the system ourselves?
Yes, if you have the breadth internally. Self-maintenance requires competence in operations, security, monitoring, and dependency updates all at once – and someone available to act when it's urgent. Many smaller IT departments handle day-to-day work fine but lack readiness for the day a critical error shows up outside office hours.
What's the risk of having no readiness at all?
That an incident happens when no one can act. A security hole, a broken dependency, or downtime in a business-critical system can cost far more in a single day than a whole year of a maintenance contract. Without readiness, recovery becomes both slower and more expensive, and sometimes the damage is already done.
Is there a middle ground between the two models?
Yes. A common hybrid model is handling first-line support yourselves – simpler issues and daily oversight – with an agency backing you up for what requires deep technical expertise or a fast response. You keep control of day-to-day work but aren't left alone when something truly serious happens.