GUIDE · CARE
What WordPress maintenance actually costs
If you run a 10–100 person SaaS or e-commerce team, WordPress maintenance cost is easier to judge line by line than as a monthly sticker. Quotes for the same site run from $20 to $500 a month, and the gap is rarely the software. This guide breaks a retainer into hours, compares four ways to cover the work, and lists what separates a cheap subscription from a managed service.
The short answer. Managed WordPress care typically runs from $50 to $500 or more a month. A one-site brochure build with updates, backups and monitoring sits around $100–$250. The number moves with sites, WooCommerce, response time, security scope and included human hours.
Why the same site gets a $20 quote and a $500 quote
The two quotes are rarely the same service at different margins. At $20 a month you buy a subscription with a support queue: automated updates, a cloud backup, an uptime ping. At $500 you buy scheduled human time, staging, a tested restore, a named person, and a response commitment that costs the vendor when missed.
Most buyers land in the middle, where the feature list is least useful. Three lines decide whether a $150 plan is good: who does the work, what is tested before production, and what happens after a failed restore. They are cheap to promise and expensive to deliver, so they go first when prices are cut.
What a monthly retainer actually pays for
A retainer is not a block of hours sold at an hourly rate. It is a share of a maintenance window, a queue position and a set of tools. These are planning ranges for one brochure site, not survey data.
| Line item | What it involves | Time per month | Separately, roughly |
|---|---|---|---|
| Updates and testing | Core, plugin and theme updates on staging, then page and checkout checks. | 1–2 h | $80–$200 |
| Backup and restore test | Off-site copy restored to staging; database, uploads and checkout verified. | 0.5–1 h | $50–$120 |
| Uptime and TLS monitoring | External checks, alert routing, certificate and domain expiry. | 0.1–0.5 h | $10–$40 |
| Malware scan and triage | Scheduled scan, verify hits, remove payloads, rotate credentials; removal policy in writing. | 0.5–1 h | $50–$150 |
| Response-time commitment | A named person's time held in a window, ahead of other work. | Retained, not task time | $50–$150 |
| Staging environment | Separate copy, refreshed before updates, promoted after testing. | 0.25–0.5 h plus hosting | $15–$50 |
| WAF and CDN | Rules, bot and rate limiting, cache purge after changes. | 0.25–1 h | $0–$80 |
| Monthly report | What changed, what broke, scan results and next month's plan. | 0.5–1 h | $50–$120 |
The last column totals more than a small-studio plan. That gap is not a trick: tools are shared, updates are batched, and the plan caps your hours.
A restore test is the only proof a backup works, which is why WordPress update documentation treats a backup as part of updating; without a dated test you own a file, not a recovery plan.
What the three price tiers buy
$20–$50: a plugin subscription
Automated updates, off-site backup, uptime alerts and a ticket queue. No staging, no restore test, no named engineer, and a scan result you interpret yourself. The OWASP Top Ten covers what a scan will not find. Fine for a brochure site; thin for a store.
$100–$250: a small studio or specialist
A named person, staging before updates, a monthly restore test, scans someone reviews, a short report, capped hours (usually one to three) and a business-day response. Most teams should start here.
$400 and up: multi-asset or revenue-critical
Several sites or a store, daily backups, checkout monitoring, four-business-hour response, quarterly review and sometimes security-questionnaire evidence. You pay for coverage and documentation, not more plugins. Not 24/7 cover unless contracted.
What a very low monthly fee hides
Two things go missing first, and neither appears on a feature list.
The tested restore. Backups are easy to show and cheap to store. Restoring one to staging, checking the database, uploads and checkout, then writing down the date is an hour with no visible feature. Ask for last month's restore date; a plan without one has a backup, not a recovery plan. CISA's StopRansomware guidance treats tested, offline backups as a recovery control.
A named human. At $20 the person answering the ticket has probably never opened your site. They follow a script, escalate when it runs out, and the clock restarts. Accountability is what automation cannot supply.
The third cost arrives after an incident. Cheap plans cover monitoring but not removal, so a compromised site becomes a separate clean-up quote. Compare the annual fee plus one incident.
Four ways to cover the work, compared
The hour-by-hour comparison for the first row is in DIY WordPress maintenance vs a care plan. This table is about who carries the risk.
| Option | Monthly cost | Response | Restore tested | Security work | Reporting | Accountable |
|---|---|---|---|---|---|---|
| DIY | Tools $0–40 plus your hours | When you get to it | Only if you test it | Scans you configure | None | You |
| Freelancer, ad hoc | Hourly, as quoted | 1–3 business days, if free | On request | Quoted per job | Invoice only | The freelancer |
| Care plan, small studio | $100–250 | 1 business day | Monthly, written | Scan, harden, patch | Monthly, one page | A named person |
| Agency retainer | From $400 | 4 business hours or better | On a schedule, with evidence | Review, WAF, runbook | Monthly or quarterly | Account lead and contract |
The middle of the table is where the money goes. A care plan and an agency retainer run the same updates; the difference is coverage, evidence and who answers on Monday.
What changes the price
Seven variables explain most of the gap between quotes for similar sites.
- Number of assets. Every site adds an update window, backup, scan review and report line. As a planning assumption, a second site adds roughly 40–60% rather than 100%, because tools are shared.
- WooCommerce or brochure site. A store adds checkout testing, payment plugin compatibility and order data. Updates take longer and a failed test costs revenue. The WooCommerce security checklist shows the extra surface.
- Compliance pressure. A SOC 2 or ISO request turns care into evidence collection: access lists, patch records, restore dates. That is billable work, and no plan should imply certification.
- Page builder. Elementor, Divi and WPBakery updates can break layouts per template. More templates means more post-update checking: hours, not a license.
- Hosting quality. A managed host with staging, object cache and backups removes firefighting. A cheap shared host adds it and may block the tests you need.
- Legacy plugins. An abandoned plugin is a permanent surcharge until replaced. A quote that maintains it without a removal plan will rise after the first incident.
- Number of environments. Production plus staging is the minimum. A QA, multilingual or wholesale environment adds sync work and another place for changes.
Five questions to ask before you sign
Send these with the quote; a good vendor answers in writing.
- Can you show the date of my last restore test? Worry if the answer is nightly backups. A backup is not a restore. Without a dated test, nobody knows how long recovery takes.
- Who does the work, and who do I call when it breaks? Worry if the answer is a department, a portal or a salesperson. You want a name, timezone and escalation path.
- What sits outside the monthly fee? Worry if removal, emergency response or migrations are quoted separately with no rates. Ask for the rate card and who approves work.
- What does the response time cover? Worry if same day has no business hours, timezone or definition of response. An acknowledgement is not a fix, and 24/7 is a staffing claim.
- What happens if the site is compromised on your watch? Worry if the answer is that it will not happen, or that it is not covered. Ask what gets isolated first, what clean-up costs and what the report covers.
Where Keelpost's plans sit, and what they leave out
Care starts at $129 a month for one site, one hour and a two-business-day response. The $249 plan doubles the hours and moves response to one business day; the $449 plan is for a store with checkout, with four hours and a four-business-hour response. Updates, backups, monitoring and a monthly report are included. Compare the care plans and their hour limits.
Support runs 09:00–18:00 GMT+8, Monday to Friday, and we are not a 24/7 SOC. If you need out-of-hours incident cover, we will say no. We also do not hold ISO 27001 or SOC 2 and do not sell certification. What monthly care covers is written out in full.
The plans exclude unlimited edits, malware clean-up (a separate fixed-scope job from $750) and any promise of a specific security outcome. Those exclusions are why the price is fixed. If you want a review first, the one-off security audit starts at $490.
FAQ
Questions buyers ask before they email
Is $20 a month enough for WordPress maintenance?
What should a WordPress care plan include?
Do I need a care plan if I rarely change my site?
Is hourly freelance work cheaper than a care plan?
Do you offer 24/7 support or incident response?
Keep reading
The next question buyers ask
Care
DIY WordPress Maintenance vs a Care Plan
What a care plan replaces: hours per month, the six recurring jobs, the failure modes, and the real cost of doing WordPress maintenance yourself.
Read the guideSecurity
WooCommerce Security Checklist
A 14-point WooCommerce security checklist: admin access, plugin hygiene, checkout hardening, headers, backups and logging, in the order that matters.
Read the guideNEXT STEP
Send us the site and the quote you have.
We will tell you which lines are missing, what the hours actually cover and whether a smaller plan would do. A written reply within one business day.