Maintenance & Support

Updates that are tested before they reach production.

Nothing is applied blind. Core, theme, and plugin updates run on staging first, get QA'd, then ship across every site in the portfolio, on a schedule you can plan around.

Update workflow

Staging first. Always.

An unattended auto-update is how a plugin conflict takes down a product site the morning of a launch. We test the same update on the same environment stack before it touches production.

Updates & patching

WordPress core, theme, and plugin updates tested on staging before production
Security patching prioritized ahead of the regular cycle when severity requires it
Compatibility review across the portfolio before a shared plugin is upgraded
Deprecated and abandoned plugin replacement planning

Database & housekeeping

Database housekeeping: revisions, transients, orphaned tables, and index health
Media library and upload directory cleanup
Cache and object-cache configuration review
Performance regression checks after each release

Post-update QA

Cross-browser verification of key templates
Mobile responsiveness checks at standard breakpoints
Form submission and integration testing
Broken link and redirect validation

Reporting & response

Monthly reporting per site: what changed, what was tested, what needs attention
Quarterly executive report per portfolio for IT leadership and the board
Direct rapid-response support with the engineer who runs your sites
No ticket triage, no account manager relaying messages

Priority Response SLA

Our speed is contractual, not aspirational.

Three response tiers. Pick the one that matches what an hour of downtime costs you. Every tier reaches the same senior engineers. The difference is the commitment we sign.

Priority response SLA tiers and coverage
Tier	Response	Coverage window	Included
SLA/01Standard	Business-hours response	MON-FRI 09:00-18:00 PT	Response during business hours, Pacific time Same-day resolution targets for standard incidents Scheduled maintenance windows Monthly per-site reporting
SLA/02Priority	2-hour response	EXTENDED HOURS · 07:00-21:00 PT	Two-hour response commitment Extended-hours coverage beyond the business day Escalation direct to the engineer on your account Priority scheduling for out-of-cycle patches
SLA/03Mission Critical	1-hour response, 24/7	24/7/365 · LAUNCH STANDBY	One-hour response commitment, 24 hours a day Around-the-clock coverage including weekends and holidays Launch-window standby with a named engineer on call Quarterly executive reporting included

Tiers are scoped per portfolio. Response commitments are written into the agreement.

Executive Reporting

Documentation IT leadership can take to the board.

Alongside monthly per-site reporting, each portfolio receives a quarterly executive report: uptime across every property, incidents blocked, malware scan results, patches applied, and blocklist status.

It is written to be read by people who do not administer WordPress: a record of what was protected, what was updated, and what remains open.

Maintenance is invisible when it works. That is the point.

The measure of this service is that nobody on your team spends a morning figuring out why a form stopped submitting after an overnight update.

You get a monthly report and a quiet portfolio.

Next step

Let's talk about your portfolio.

Engagements are scoped per portfolio. Tell us how many sites you run and what keeps breaking.

Talk to us