Rated 5 star on
Maintenance Contracts: What a Good One Covers
Quick answer
A good app maintenance contract defines the scope of work, severity levels with response and fix times, coverage hours and pricing. It lists exclusions such as new features and sets a change request process. Code, app store accounts and credentials should stay in your name. The contract should also plan the exit, with handover help.
Most app maintenance disagreements start with a contract that didn't say enough. "Ongoing support" turns out to exclude the update Apple now requires. An urgent outage waits until Monday because response times were never defined. When the relationship ends, nobody can find the store logins. A clear contract prevents all three by putting the details in writing first.
Key Takeaways
- Define exactly what maintenance includes, from bug fixes to app store updates and security patches.
- Set severity levels with response and fix times, and the hours they apply.
- Choose a pricing model that fits: a monthly retainer, a bank of hours or per-request work.
- List what's excluded, such as new features, and how change requests are priced.
- Keep code, app store accounts and credentials in your name.
- Plan the exit: notice periods, handover help and documentation.
Published: October 29, 2026 | Reading Time: ~9 minutes | Category: App Maintenance
This guide covers what a good app maintenance contract includes: the scope of work, severity levels and response times, pricing models, what's excluded, ownership and access, security, reporting and how to leave cleanly. Put plainly: if it matters when something breaks, write it down before it does.
This is general information, not legal advice. Have counsel review any contract before you sign.
In This Playbook
- Scope: what maintenance includes
- Severity levels and response times
- Pricing models
- Exclusions and change requests
- Ownership and access
- Security and data
- Reporting and reviews
- Term, notice and exit
- What are red flags in an app maintenance contract?
- How do we measure an app maintenance contract?
- The first three months
Scope: what maintenance includes
Bug fixes. Problems in existing features.
Phone software updates. Changes needed when new iOS and Android versions arrive.
App store compliance. Updates required by Apple and Google, such as minimum version rules.
Library and security updates. Keeping third-party code current and patched, as covered in React Native maintenance.
Monitoring. Watching crashes, uptime and errors.
Small changes. Text edits, minor tweaks and settings, up to an agreed limit.
The typical service list is covered in app maintenance services.
Severity levels and response times
Define each level. For example, critical when the app is down or payments fail, high when a key feature is broken, and lower levels for minor issues.
Response time. How quickly someone acknowledges and starts work.
Fix time. A target for resolving or working around the problem.
Coverage hours. Business hours only, or nights and weekends for critical issues.
How to report. The channel and details needed. Typical levels are covered in app maintenance response times.
Pricing models
Monthly retainer. A fixed fee for a defined scope and set hours.
Bank of hours. Prepaid hours used as needed, with rules for unused hours.
Per request. Paying for each fix or change, which works for very stable apps.
What's included in the fee. Monitoring, store updates and urgent support, or extra?
Price changes. How and when rates can increase. Overall costs are covered in the cost after launch.
Exclusions and change requests
New features. Usually outside maintenance, quoted separately.
Major redesigns or rebuilds. Separate projects.
Third-party outages. Problems caused by outside services, with clear expectations.
Change requests. How they're submitted, estimated and approved before work starts.
Ownership and access
You own the code. State it plainly, including work done during maintenance.
Accounts in your name. App store accounts, code repositories, hosting and services.
Credentials shared securely. Through a password manager, not email.
Access removed at the end. The provider's access is removed when the contract ends.
Security and data
Confidentiality. Protection for your code, data and customer information.
Data handling. How customer data is accessed, stored and protected during work.
Security fixes. Priority for known vulnerabilities.
Incident notice. How quickly the provider tells you about a security problem.
Reporting and reviews
Monthly reports. Work done, hours used, issues fixed and upcoming store deadlines.
Health checks. Versions, outdated libraries and crash rates.
Regular reviews. Quarterly meetings to adjust scope and priorities.
Term, notice and exit
Contract length. Monthly, yearly or with an initial term.
Notice period. How much warning either side gives to end the contract.
Handover help. The provider helps transfer knowledge to a new team.
Documentation. Current setup notes, release steps and known issues delivered at the end.
Questions to ask any provider. The same checks on access, ownership and exit apply to other partners, as covered in what to ask before hiring a task management partner.
What are red flags in an app maintenance contract?
Vague scope. "Ongoing support" with no list of what's included.
No response times. Or response times without fix targets.
Accounts in the provider's name. Makes switching providers difficult.
No exit terms. No notice period, handover or documentation.
Hidden extras. Store updates or security patches billed separately without warning.
How do we measure an app maintenance contract?
Response and fix times. Against the contract.
Hours used. Against the plan, month by month.
Open issues. How many, and how long they've been open.
Store deadlines met. Before they block releases, as covered in Google Play review and policy basics.
Crash-free users. Whether app quality is holding.
The first three months
Days 1–30: review or draft
Review your current contract against this list, or draft one. Confirm scope, severity levels, pricing, exclusions and exit terms, and have counsel review it. Check that all accounts are in your name.
Days 31–60: set up
Agree on how issues are reported, set up monitoring and a shared password manager, and schedule monthly reports.
Days 61–90: review performance
Compare response times, hours used and store deadlines against the contract. Adjust scope or pricing at the first quarterly review.
How Astra structures maintenance contracts
Astra Results Marketing writes app maintenance contracts that say what happens when something breaks. We define scope, severity levels with response and fix times, pricing, exclusions and change requests in plain language.
Code and accounts stay in your name, you get monthly reports and the exit terms are clear from day one. Engagements begin with an app and contract review through our app maintenance team.
Related reading
Frequently asked questions
What should an app maintenance contract include?
Scope of work, severity levels with response and fix times, coverage hours, pricing, exclusions, change request steps, ownership and access, security, reporting and exit terms.
What's the difference between response time and fix time?
Response time is how quickly someone acknowledges and starts work. Fix time is the target for resolving or working around the problem. A good contract defines both.
Which pricing model is best?
It depends on your app. A monthly retainer suits apps needing steady work, a bank of hours suits variable needs and per-request pricing suits very stable apps.
Are new features part of maintenance?
Usually not. New features and redesigns are typically quoted separately, with a clear change request process.
Who should own the app store accounts?
You should. Keep app store accounts, code repositories, hosting and services in your name, and share credentials securely.
What happens if we want to switch providers?
A good contract sets a notice period, requires handover help and delivers current documentation, and the old provider's access is removed.
Ready for a maintenance contract that covers what matters? Astra Results Marketing writes clear app maintenance contracts with defined scope, response and fix times, fair pricing, accounts in your name and exit terms from day one. ▸ CALL (786) 321-2866 · ▸ REQUEST YOUR CONSULTATION
