Application health review
Review the current setup, known problems and dependencies before agreeing on maintenance scope.
Application Support
Keep websites and applications maintainable with a defined review, update and issue-resolution workflow.

Business-first delivery
Existing software needs clear ownership after launch. Changes in dependencies, hosting, content and connected systems can affect behaviour over time. A practical maintenance plan identifies the systems in scope, the review cadence and how issues will be investigated and prioritised.
Review the current setup, known problems and dependencies before agreeing on maintenance scope.
Plan applicable updates, compatibility checks and staging review to reduce avoidable disruption.
Collect useful reproduction details, logs and environment context to investigate reported problems.
Define which routine content, configuration and administrative changes belong in the engagement.
Review existing backup arrangements and recovery responsibilities; verify any agreed restoration procedures.
Separate essential maintenance from new features, with clear priorities, estimates and approval boundaries.
How we work
Understand business goals, users, requirements and the existing environment.
Agree on scope, priorities, responsibilities and acceptance criteria.
Plan the experience, solution structure and integration boundaries.
Implement the agreed work in reviewable increments.
Check functionality, accessibility, performance and relevant edge cases.
Plan the release and verify the delivered result.
Review maintenance needs and the next improvements with the team.
Existing software needs clear ownership after launch. Changes in dependencies, hosting, content and connected systems can affect behaviour over time. A practical maintenance plan identifies the systems in scope, the review cadence and how issues will be investigated and prioritised.
Share the platform, hosting environment, repository or administrator access arrangements, known issues and existing support documentation. Access should follow an agreed, appropriate permissions process.
No. Define supported systems, update responsibilities, response expectations and exclusions explicitly. New features and substantial integration changes should be scoped separately rather than assumed to be included.
Agree on systems in scope, access arrangements, deliverables and review responsibilities before work begins. Identify dependencies and acceptance criteria for the first phase, then document open issues and the next decisions your team needs to make.
Explore your options
Share the platform, hosting environment, repository or administrator access arrangements, known issues and existing support documentation. Access should follow an agreed, appropriate permissions process.
No. Define supported systems, update responsibilities, response expectations and exclusions explicitly. New features and substantial integration changes should be scoped separately rather than assumed to be included.