WordPress care
Updates, hardening, backups, and speed checks.
Uptime, errors, backups, and certificate expiry.
Core, plugins, dependencies, and security fixes.
Bugs and incidents with a clear response time.
Small features and cleanup inside the monthly pool.
Updates, hardening, backups, and speed checks.
Queues, logs, dependencies, and releases.
Store updates, crash reports, and SDK changes.
The scope is agreed in writing before the start.
Four stages, each with a written result.
We review the current state and agree on the result.
We choose the stack and describe the architecture.
You see progress in iterations, not at the end.
We hand over code, documentation, and warranty.
Maintenance is not a list of plugin updates. It is a routine that keeps the product predictable: backups that restore, monitoring that alerts, patches that do not break checkout, and a person who answers when something fails. We agree the response time and the monthly pool before work starts.
Small improvements are part of the same pool. A landing page, a new field, a slow query, or a security header can be fixed without a new project. The monthly report shows what changed, what was monitored, and what is planned next.
Silent failures are the real risk. A site that is up but cannot send email, a queue that stops processing, or a certificate that expires on a Sunday. Monitoring covers the paths that matter, not only ping. The monthly report shows what was checked and what changed.
Support also protects the budget. Small fixes inside the pool cost less than an emergency project, and the documentation stays current because the same team touches the code.
Monthly retainer: $500 to $2,000 depending on scope and response time.
What clients ask before the start.