We keep WordPress sites patched, backed up, monitored, and fast, with real developer hours attached instead of a plugin that emails you when something already went wrong. Every plan includes a restore test, because a backup nobody has restored is a guess.
“Our site went down and nobody noticed for a day.”
Uptime checks run every minute and a human is paged, not just a dashboard. See what’s monitored
“We’re scared to run updates.”
Updates get applied on a staging clone and visually diffed before they touch production. See how updates run
“We have backups but have never tested one.”
Every plan includes a quarterly restore drill to a scratch environment. See the plans
“We just need someone for small fixes.”
The Standard plan carries two developer hours a month for exactly that. Compare plans
These figures cover every Gatilab service, not this one alone. We’d rather say that plainly than imply a per-service record we haven’t published.
Brands we’ve delivered work for
Every plan covers the same monitoring and backup baseline. What changes is response time and how many developer hours come with it. Hours don’t roll over, and we’ll tell you when you’re on the wrong plan.
For brochure sites, blogs, and small business sites that need someone watching but rarely change.
One site · 48-hour response
If an update breaks the site, we roll it back and fix it at no extra cost.
For business sites that ship small changes monthly and cannot afford a broken checkout or form.
One site · 8-hour response · 2 dev hours
Unused hours don’t roll over. We’d rather right-size your plan than bank your money.
For ecommerce, membership, and lead-generation sites where an hour offline is measurable revenue.
One site · same-day response · 8 dev hours
We cap Priority accounts per engineer, so we’ll say if we’re full rather than stretch.
Maintenance is easy to sell and hard to verify, so every item here produces something you can see in your inbox or your staging site.
Week 1
We inventory plugins, PHP and WordPress versions, existing backups, and whatever is already installed and abandoned. Most sites we take over are running at least one plugin nobody can explain.
You leave with: A written inventory and a list of what we recommend removing.
Week 1 to 2
Backups get configured offsite and restore-tested, file permissions and admin accounts get reviewed, and monitoring goes live before we touch anything cosmetic.
You leave with: A tested restore and monitoring you can log into.
Ongoing
Updates land on a staging clone first, get visually diffed and smoke-tested against your forms and checkout, then go to production. Anything that breaks stays on staging.
You leave with: A change log naming every version that moved, and why.
Monthly
One page: uptime, backup and restore status, updates applied, blocked threats, Core Web Vitals, and hours used. No 40-page PDF nobody reads.
You leave with: A one-page report and a standing invitation to ask about any line.
Maintenance retainers are the easiest place in this industry to quietly charge for nothing. Two of these are reasons we turn work down.
Something not covered? Ask directly and you’ll get a straight answer, not a calendar link.
No, deliberately. We don’t resell hosting, because bundling it means leaving us also means moving your site. You keep the hosting account in your name and we work inside it. If your host is the actual problem, we’ll tell you and help you move, but the account stays yours.
It usually doesn’t reach you, because updates go to a staging clone and get smoke-tested against your forms and checkout first. If something slips through to production anyway, we roll back from that day’s backup and fix the underlying conflict at no extra charge. That’s on us, not billable.
No. Rolling hours sound generous and quietly turn into a balance nobody uses and both sides argue about later. If you’re consistently not using your hours, we’ll move you down a plan. If you’re always over, we’ll tell you before the invoice, not after.
A plugin tells you something happened. It doesn’t decide what to do, test a restore, read a PHP error log, or diff a layout after an update. The plugins we install are part of the work, not the work itself. The difference you’re paying for is a person who reads the alert.
Yes, and most of what we maintain was built elsewhere. The onboarding audit exists precisely for this. Expect it to surface abandoned plugins, an outdated PHP version, or a backup that has never been restored. We fix what we find before starting the normal cycle.
Cancel any month with no exit fee. We hand over backups, credentials, documentation, and the staging environment. Nothing about the setup is proprietary to us, which is intentional.
Send the URL and whatever keeps you up at night, whether that’s an ancient plugin, a backup nobody has tested, or a form you’re not sure still works. We’ll tell you which plan fits, or that you don’t need one yet.
Free to download, no email required. A maintenance retainer is worth exactly what its reporting and service levels say it is. Here is the agreement we work to, plus the SOP format behind the actual monthly run.
Rollover caps, service levels, and reporting commitments. The terms that decide whether a retainer is worth renewing.
A one-page SOP format people actually follow, with a worked maintenance-run example.
If you would rather have this done than do it yourself, tell us what you are working on. If not, the templates are still yours.
