Routine changes and dependencies
List the website or app components, hosting and external services involved. Decide which updates and checks are covered and how changes will be reviewed before release.
Sanu Tech / Support & maintenance
Website and app
maintenance.
Keep your website or app supported with our Hyderabad team. Agree routine updates, issue handling and practical improvements after launch.
Built around your objective
Clear responsibilities.
Practical ongoing support.
Maintenance works best when routine tasks, new features and third-party issues have clear owners. We review the current build before agreeing coverage, priorities and response arrangements. Support for businesses across India is scoped to the systems and access actually available.
A good fit for: Existing websites or apps that need a defined maintenance arrangement or a planned improvement programme.
- Technical review
Review the website or app, its dependencies and safe access arrangements before taking on support. Identify any inherited limitations at the start.
- Routine maintenance
Define updates, checks, backup and monitoring responsibilities within the plan. Do not assume every task is included in a general support fee.
- Issue handling
Agree contact channels, severity levels, working hours and response arrangements. The written scope determines coverage; this is not an automatic 24/7 guarantee.
- Planned improvements
Keep a prioritised backlog for content and usability changes. Separate new web development or app features from routine maintenance.
Plan the right scope
Know what is covered and who owns each task.
A maintenance arrangement starts with the condition of the existing system. Agree the supported components, access requirements and escalation route before relying on a general support label.
Issues and recovery
Define severity, reporting channels, supported hours and response arrangements. Record backup ownership and recovery expectations so an incident does not reveal missing responsibilities.
Improvements and larger work
Keep a prioritised list of small changes, recurring problems and desired features. Separate maintenance from a redesign, migration or new functionality that needs its own estimate.
The journey
A clear path
from scope to handover.
/01
Review the current build
Inspect the available code, dependencies, hosting and existing issues.
/02
Agree the coverage
Document supported systems, routine tasks, working hours and responsibilities.
/03
Prioritise the work
Separate urgent defects, planned maintenance and new-feature requests.
/04
Review and hand over changes
Record completed work, verify agreed checks and update the remaining priorities.
Useful details
Let’s make
the scope clear.
Every project has its own requirements. These details help us start with the right questions.
Can you maintain a website or app built by another team?
Support starts with a technical review of the code, dependencies, hosting and available access. We agree what can be maintained and identify any corrective work before committing to coverage.
Does maintenance include round-the-clock support?
Not by default. Support hours, severity definitions and response arrangements must be stated in the proposal. Third-party uptime and new feature development are separate unless expressly included.
How is maintenance priced and scoped?
The platform, current condition, dependencies and covered tasks determine the arrangement. Agree updates, backup responsibilities, incident handling and review periods so that ongoing work is not confused with a redesign.
What information helps you assess an existing website or app?
Share the public URL or app listing, known issues, platform details if available and the work you need covered. Access can be arranged securely after the review scope is agreed; do not put passwords, keys or user data into the enquiry form.
Connect the dots
You might also need…
Let’s make it happen
Let’s define your
next step.
Share your website or app link, current issues, platform details if known, and the support coverage you need. Do not include passwords or API keys.