Our Process

Here’s our general process for safely updating your site(s). We tailor this to meet the needs of each client.

Day 1

Introduction & Paperwork

Day 2

Downloading & Developing

Day 3

Discoving & Updating

Day 4+

Testing &

Day 5

Releasing &
DB Updating


Supporting & Add-ons

  • Introduction: Complimentary Zoom meeting or phone call up to 1 hour getting to know you and your site.
  • Paperwork: Reviewing our development contract (protecting confidential info, limited liability, etc.) and invoicing the initial phase payment based on an allotment of hours.
  • Downloading: Getting access to your site so we can get a copy using a typical backups plugin. Doesn't include Media Library files since we don't need those.
  • Developing: Setting up your site in our development environment with latest WP core and PHP 7.2 (common to all managed hosts) with a redirect to your media library files from live.
  • Discovering: See what all breaks, what error logs are showing up, which plugins need updating, etc.
  • Updating: Apply software updates accordingly. Some third party plugins or themes may require new client purchased licenses to provide the updates.
  • Testing: Running front end and back end smoke tests and black box testing to ensure the server logs are relatively clean. Client to run white box testing (all of your test cases) in development environment or hire us to consult with you and test for you based on your stated needs.
  • Add-ons: Additional SOWs that initial assessment could prove necessary. We will discuss these as we discover their relevance to your situation. See below for a list of common add-ons.
  • Releasing: Backing up live, then releasing your new site code to the live environment. While we do our best to prevent significant downtime, some downtime can be unavoidable. We schedule releases during normal business hours earlier in the day with ample runway to fix immediate issues on a mutually convenient day.
  • DB Updating: If we made database changes above, such as new configurations or data cleanups, those will have to be applied to production as well.
  • Supporting: Further testing, training and ongoing support services.

Common add-ons:

  • Overhaul: Potential major theme or plugin repair or replacement.
  • Options Table: Cleaning up your `wp_options` DB table – where all historic plugins store their settings that can slow down your site and eat up server RAM.
  • Edge Layer: Setting-up a service of choice to secure and buffer your traffic and improve performance.
  • Upgrading DB: tables to InnoDB with optimal settings to improve transactional performance.
  • Object Caching: Enabling persistent object caching with your host, where available, to improve performance.
  • APM: Application performance monitoring analysis of PHP and MySQL resources – useful if we see performance issues.
  • Page Caching: Setting up more caching to further improve performance of higher traffic sites that serve mostly static contents.