In summary, the maintenance plan is so you’re at the point where you login and see 0 updates for plugins and/or themes. Before being enrolled we’d need to do a small audit to confirm a few things. Mostly; No core files are edited and the child theme is structured properly.
Here is a sample doc we use to get started: https://docs.google.com/spreadsheets/d/1eK6a45vyw9lR1m18L-bRtAnP0KjEKxEnFqXGHtcSHZw/edit?usp=sharing
The maintenance plan includes:
– Keeping an inventory of plugins
– Monthly updates of plugins and WordPress core
– Unit testing for high priority plugins
As shown on the document, high priority plugins are identified. During an update, the beta release is installed on a staging server and is tested. This ensures there are no conflicts and the site is okay.
For you: it means no longer having to think about updates, ever.
In the event that a plugin is not compatible, we seek a quick fix, or in the worst case, deploy a backup plugin. If neither of these options work, the update is delayed, and/or new options are explored.
At times, during a major upgrade, eg: WooCommerce 2.8 to 3.0, or WP 4.1.2 to 4.2, a new Statement of Work may be required, that is not included in the plan. This would also apply if a plugin developer has abandoned shop. You will be notified in advance.
Any smaller updates, 4.1.2 to 4.1.3 are all included.