AriesDevs engineering team Engineering notes
5 min read
Many businesses budget carefully for building software and forget what comes after. Browsers update, libraries age, security issues appear and users ask for improvements. Without maintenance, even a good product slowly breaks. Budgeting for it up front avoids unpleasant surprises.
What maintenance includes
- Bug fixes and small improvements.
- Security patches and dependency updates.
- Monitoring, backups and uptime checks.
- Compatibility with new browsers, operating systems and devices.
- Hosting and infrastructure management.
- Small feature changes and content updates.
A sensible yearly budget
A common rule of thumb is to plan roughly 15 to 20 percent of the original build cost per year for maintenance. Simple websites may need less; complex products with many integrations or regulated data may need more. Treat the figure as a starting point and refine it once you see real usage.
Choosing a support plan
- Response times: agree how fast urgent issues are acknowledged and fixed.
- Reserved hours: a monthly block of time for small changes keeps work flowing.
- Named engineer: someone who already knows your code beats a ticket queue.
- Reporting: a short monthly note on incidents, hours used and what is next.
Costs that are easy to miss
- Hosting, domain names and certificates.
- Third-party licences and API usage that grow with traffic.
- Monitoring and error-tracking tools.
- Periodic security reviews and accessibility checks.
The cheapest maintenance is good engineering
Automated tests, clear documentation and a clean structure make every later change faster and safer. Asking about these during the build is the best way to keep the cost of ownership low.
