How to Write a Software Requirements Document (PRD)
Learn how to write a software requirements document that outsourced teams can build from: structure, user stories, acceptance criteria and a ready checklist.
What software maintenance really covers, why it never drops to zero, and how to plan a realistic post-launch budget when you outsource support and upgrades.
Many teams plan the build budget carefully and leave “what happens after launch” as a single line, or nothing at all. Then the first browser update breaks a form, a dependency gets a security advisory, and a customer reports a bug on a Friday evening. Software is not a finished object; it is a service that has to be kept running.
This guide explains what maintenance covers, how to think about its cost, and how to set a budget you can defend to your finance team.
Maintenance is not just bug fixing. It usually splits into four kinds of work:
Operations sit beside these: monitoring, backups, incident response and hosting. If you do not name them, nobody owns them.
Even if you never add a feature, the world around your software keeps moving:
Skipping this work does not save money. It defers the cost and usually increases it, because upgrading across several major versions at once is harder than doing it incrementally. See our guide to managing technical debt for how this compounds.
| Driver | Why it matters |
|---|---|
| Size and complexity | More code, integrations and environments mean more to patch and test |
| Code quality and test coverage | Weak tests make every change slower and riskier |
| Documentation | Missing documentation makes each new engineer slower to be useful |
| Support hours | 24x7 cover costs more than business-hours cover |
| Response targets | Tight response and resolution times need more standby capacity |
| Release frequency | Frequent releases need stronger automation but smaller, safer changes |
| Third-party dependencies | Each one is a potential source of breaking change |
Notice that nearly all of these are decided during the build. Investing in tests, documentation and a clean deployment pipeline up front lowers the cost of every year that follows.
1. Fixed monthly retainer. A set number of hours or a defined scope each month. It is predictable and good for stable products. Agree what happens when you exceed the hours.
2. Dedicated maintenance team. One or more engineers assigned to your product, with deep context. It suits products with continuous change and heavier support demand. Our fixed price vs dedicated team comparison covers the trade-offs.
3. Time and materials, on demand. You pay only when something needs doing. It looks cheap, but response is slower and nobody holds context, so it is risky for anything customer-facing.
Most companies end up with a retainer for routine work and an agreed rate card for larger changes.
Avoid inventing a percentage from a blog post, including this one. Instead, build the figure bottom-up:
Before go-live, confirm that you have:
If any of these is missing, fix it now. It is far cheaper than discovering the gap during an outage.
When you hand maintenance to an offshore team, make the arrangement explicit: access and security rules, handover documentation, reporting cadence and escalation paths. Ask for monthly reporting that shows tickets resolved, time to respond, upgrades completed and risks ahead. Regular reporting turns maintenance from a black box into something you can manage.
If you want a realistic maintenance plan for an existing product, or want to hand over support and upgrades to a dependable team, see our application support and maintenance services. You can also contact us with a short description of your system, and we will suggest a sensible scope and engagement model.
Learn how to write a software requirements document that outsourced teams can build from: structure, user stories, acceptance criteria and a ready checklist.
How to design a product analytics event tracking plan: naming rules, properties, ownership and QA, so your web and mobile data is trustworthy from day one.
A practical go-live readiness checklist covering testing, security, infrastructure, rollback and support, so your software launch is calm instead of chaotic.
Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.