01
Baseline
The current condition is recorded.
Known risks and access gaps are identified before recurring responsibility begins.
Defined website care, not a vague AMC
Website Maintenance Services in India
A maintenance plan should state what is checked, what is changed, how quickly requests are reviewed, where backups live and which work needs a separate quote.
Plans from ₹2,500 per month · exact inclusions and response windows are written before work starts
Quick answer
Website maintenance should be sold as a written care plan, not an undefined annual contract. The plan should identify the websites covered, update and backup duties, monitoring, request channels, response windows, included change time, exclusions, third-party renewals and the process for urgent incidents.
7 yearsprofessional web work
500+projects contributed to through agencies and teams
from ₹8,000final quote depends on scope
Directaccess to the owner and developer
Start with access and a technical baseline
A provider cannot responsibly promise maintenance before seeing the platform and account condition.
A takeover review should confirm domain and hosting control, admin access, platform and versions, plugins or apps, licence ownership, backup status, current errors, analytics access and known custom code. Serious defects, a compromised site or an unsupported legacy stack may need a separate recovery project before routine care begins.
Write the recurring work and the limits separately
Updates, small content changes and new development should not be mixed into one unlimited promise.
- Preventive work: agreed platform or plugin updates, backup checks and monitoring review.
- Content work: a stated time allowance or task limit for text, image and existing-page changes.
- Incidents: severity definitions, acknowledgement windows, investigation steps and exclusions.
- New work: new pages, features, migrations and integrations receive a separate written scope.
- Reporting: a concise record of completed work, unresolved risk and upcoming renewals.
A backup is useful only if responsibility and restoration are clear
“Backups included” does not explain location, retention or recovery.
The plan should state who creates the backup, whether it is separate from the live server, how long copies are retained, what is included, how restoration is tested and what recovery objective is realistic. Provider-level backups can be useful, but they should not be assumed to cover every failure.
Difference
What an accountable maintenance scope contains
02
Window
Response commitments live in the plan.
No universal same-day or 24×7 promise is implied; the selected plan states the actual service window.
03
Record
Changes can be reviewed later.
Updates, requests, backup checks and unresolved items are recorded in an agreed format.
04
Control
The business retains its accounts.
Maintenance access should not require transferring domain, hosting or platform ownership to the provider.
Process
How the work is agreed and delivered
-
01
Access and condition review
Before retainer
Confirm ownership, platform, versions, licences, backups, errors and custom dependencies.
-
02
Care-plan proposal
Written
List covered sites, tasks, request windows, included time, reporting, exclusions, price and cancellation terms.
-
03
Baseline backup
Before changes
Create or verify the agreed recovery point and record any limitation.
-
04
Controlled maintenance
Per schedule
Perform only the agreed updates and requests, with staging or rollback precautions where the risk requires them.
-
05
Change record
Per plan
Report completed work, incidents, unresolved risks and upcoming renewals.
Pricing
Maintenance pricing starts with the site’s risk and workload
These are conversation starting points, not unlimited packages. The written plan controls the final scope.
01
Essential care
from ₹2,500 / month
Small informational site
- One agreed website
- Scheduled update and backup checks
- Defined request channel
- Small-change allowance stated in plan
- Change summary
02
Active business site
scoped after review
Regular content or integrations
- Everything explicitly agreed from essential care
- Larger change allowance
- More frequent review where justified
- Performance or form checks as named
- Renewal and risk notes
03
Store or critical workflow
scoped after review
Higher operational risk
- Checkout or lead-flow test plan
- Incident severity and response windows
- Provider escalation responsibilities
- Recovery assumptions
- No implied 24×7 cover unless contracted
Emergency recovery, new features, migrations and third-party provider charges are separate unless the written plan expressly includes them.
Questions
Questions before you decide
Can you maintain a website built by someone else?
Often, yes. A takeover review first checks access, ownership, platform condition, licences, custom code and backup quality. Unsafe or unsupported work may need a separate recovery scope.
Is maintenance compulsory after a new website?
No. Responsibility still needs to be assigned, but the business can handle it internally, use Overbuilt or choose another provider.
Does a maintenance plan include unlimited changes?
No. Included change time or task limits should be written. New features and material new pages need a separate estimate.
Do you provide 24×7 emergency response?
Not by default. Any after-hours monitoring, acknowledgement or recovery commitment must be explicitly priced and written into the selected plan.
Does maintenance guarantee the site will never go down?
No. Maintenance reduces avoidable risk, but hosting, networks, third parties, attacks and software failures can still cause incidents. The plan should explain detection and recovery responsibilities.
Next step
Send the website URL and describe what needs attention.
Ashish will first identify the platform, access and risk questions needed for a responsible maintenance quote.