Back to Development
Development / Maintenance

A site that stays working, not just one that launches

Plugin updates, core updates, security monitoring, and someone who actually knows why the site was built the way it was — not a support inbox that's never seen your code.

Founder-led, not outsourced to a queue Updates, backups & security checked monthly The person who built it is the one maintaining it
What's covered

Maintenance that catches problems before they're outages

Most "maintenance plans" are a renewal invoice and nothing else. This one is a person actually looking at your site.

Core, theme & plugin updates

Tested before they go live, not auto-applied and hoped for — a bad plugin update has broken more sites than it's fixed.

Security monitoring

Malware scanning, login protection and firewall rules kept current, so a WordPress vulnerability doesn't become your problem.

Backups & recovery

Regular, verified backups — not just a checkbox in a settings page nobody's actually tested restoring from.

Performance checks

Regular speed and uptime checks, so a slow site gets caught before it costs you traffic.

A maintenance plan should mean fewer emergencies — not just an invoice for hoping nothing breaks.
How it works

A monthly rhythm, not a fire drill

01

Audit

I start with a full health check — updates outstanding, security gaps, backup status — before anything else.

02

Monthly maintenance

Updates tested before going live. Security and backups checked every month, not just when something breaks.

03

Direct line, not a ticket

Something looks wrong? You email me directly. No first-line support reading from a script.

04

Plain-English reporting

A short summary each month — what changed, what's outstanding, what's monitored.

Questions people actually ask

FAQ

What's actually included in ongoing maintenance?

Core, theme, and plugin updates tested before they go live, security monitoring, backups, and uptime checks — the groundwork that prevents most emergencies.

What happens if something breaks between scheduled check-ins?

You reach me directly, not a support ticket queue — that's the actual point of a maintenance plan with one person behind it.

Is this only for sites you originally built, or can you maintain existing sites too?

Existing sites too, after an initial review — some inherited builds need a bit of cleanup first before ongoing maintenance actually protects them properly.

Available for projects

Tell me what's broken, or what you're starting.

One email or a fifteen-minute call. I read and reply to every one myself.