₹499 + GST
per monthFor a simple brochure website
- 1 small update request
- WordPress and plugin update check
- Monthly backup check
- Contact form check
Clear inputs help a small maintenance allowance produce a useful result. Before the task begins, identify the exact page, the required change and the person who can approve the finished update.
Share the page URL and explain what is incorrect, outdated or not working. A screenshot is useful when the problem appears only on a particular phone or browser.
Provide approved text, original images, product details or account access needed for the request. This prevents the maintenance time being spent searching for missing inputs.
State what a visitor should see or be able to complete after the change. For forms, buttons or checkout steps, include the destination and the expected confirmation.
Check the updated page on desktop and mobile, then confirm approval or report one precise correction. Larger structural work can be separated into a redesign scope.
Need more than recurring updates? Compare website care, redesign and rebuilding, or review our website design services.
Website care is most effective when every request has a defined outcome and an agreed boundary. Routine maintenance, content updates and improvement projects require different inputs, review effort and risk controls.
Updates, backup checks and basic health reviews should consider compatibility and recovery, not just whether an update button was clicked. The exact platforms and tasks covered belong in the written scope.
Approved copy, images, products, offers or team information can be placed accurately when the source material and target pages are clear. New layouts or large catalogue imports may need a separate project scope.
Check that important calls, enquiry forms, email delivery, WhatsApp links, booking or checkout steps reach the intended destination. A care task should state the test performed and the result observed.
Image size, caching, broken links, redirects and plugin behaviour can be reviewed within an agreed task. Significant theme, hosting, database or application changes require their own risk and rollback plan.
Maintaining metadata, redirects and indexability during site changes is different from running a full SEO campaign. Keyword research, new content, digital PR and sustained authority work should be scoped separately.
A redesign, migration, new integration, custom feature or structural rebuild should not be hidden inside a small care allowance. When the request becomes a project, the new deliverables and quote are confirmed first.
Choose care for controlled updates and maintenance on a usable site. Choose redesign when the existing site can be improved safely through better templates, content and journeys. Choose a rebuild or development project when the platform or architecture cannot support the required outcome.
Use the redesign-versus-rebuild guide →Share the page URL, expected result, approved assets and any deadline. We will confirm whether it fits a listed care option or needs a separate custom scope.
Not necessarily. Hosting and website-care responsibilities depend on the written scope. The scope should identify who manages the server, backups, domain, email, licences, platform updates and site changes.
A controlled page update or a simple approved page may fit an agreed care task. New templates, large content structures, integrations or customer journeys should be scoped as a separate project.
No responsible provider can promise zero risk. Maintenance can reduce avoidable risk through updates, recovery planning, access hygiene and monitoring, but platform, hosting, credentials and third-party components still matter.
The listed option or custom quote should match the exact request, required access, review effort and risk. Deliverables, exclusions and approval responsibility are confirmed before the task begins.
QUICK CONTACT