Maintaining Client Sites Print

  • developersgitdeployment, developers, plugins, backup, security, php, themes, performance, errors, troubleshooting
  • 0

Ongoing work after launch.

WHAT MAINTENANCE ACTUALLY INVOLVES

Applying core, plugin and theme updates Checking backups ran Monitoring uptime Checking for errors Reviewing security Occasional small content changes

BEING EXPLICIT ABOUT SCOPE

"Maintenance" means different things to you and the client. State exactly what is included: which updates, how often, how many change requests, what response time, and what is billed separately.

THE RISK TO MANAGE

You become responsible for a site the client also modifies. Agree who may install plugins, and say what happens if a client change breaks something.

A ROUTINE

  • Monthly: updates, backup verification, error check
  • Quarterly: security review, performance check, plugin audit
  • Annually: PHP version review, full review with the client

TESTING UPDATES

On staging for anything significant. A plugin update that breaks a client's shop on a Friday is your problem regardless of cause.

PRICING IT

For the time, not the technical cost. Support time is what this actually consumes.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot