What should app maintenance include?

Launch is the start of operating a product. A maintenance agreement should explain which work is included, how issues are reported and what happens when you need a new feature.

Separate fixes from new development

An agreed feature that fails needs a different discussion from a new workflow. Record the delivered scope and the applicable support period so both sides can distinguish defect fixes from changes.

Agree on the services you need

• Compatibility checks for relevant operating-system and dependency updates.
• Review of error reports and the core journeys affected by a change.
• Hosting and backup responsibilities, including restore checks where agreed.
• Updates to third-party integrations and account configuration.
• Planned improvements estimated separately from routine support.

Set clear support expectations

Specify support hours, reporting channels and how urgent issues are prioritised. A response target and a resolution target are different: resolving a problem can depend on reproducing it, third-party services or access to the affected system.

Keep ownership and access organised

Know who owns your domain, hosting, store accounts and source code. Agree on access permissions and a handover process. Avoid making daily operations depend on one undocumented account.

Review the plan as your product grows

An app with occasional updates may need a different arrangement from a platform with frequent releases and busy exam or sales periods. Match the plan to actual usage and business needs. Discuss maintenance and support.