Norml Care · WordPress

Care for your WordPress site. Monthly. With hours on top when you want changes.

A flat subscription that keeps your site healthy — updates, backups, security, monitoring. Optional committed hours each month for the changes you want done. One predictable invoice. No prepayment.

Baseline
Stable sites with rare updates.
$200 / mo
on our Cloudways · $300/mo on your server
No included hours · ad-hoc at $40/hr
Updates, backups, security, monitoring, monthly report — all in.
Changes you ask for get an estimate and approval before we start.
Start with Baseline
Pro
Sites with regular small changes.
$550 / mo
on our Cloudways · $650/mo on your server
10 hours / mo included · $35/hr effective
Everything in Active, with 10 hours each month.
At 80% used we send a heads-up. At 100% we stop and ask.
Choose Pro

Why two prices for each plan

Sites on our managed Cloudways environment are $100 cheaper across every tier because we already know the stack — we update, test, and revert in minutes. On a server we don't host, we need extra time to be careful. Same scope and same SLA either way; the $100 covers the extra care.

Need more than 10 hours each month? That's a different conversation — at 20+ hours/month it's co-development, and we structure it case by case with a custom rate. Email us with what you're trying to do.

What's in baseline, what's not

Included every month (all plans)
  • Core, plugin, and theme updates — tested on staging first
  • Daily offsite backups, 30-day retention, monthly restore test
  • Security monitoring — malware scan, file-integrity, login alerts
  • Uptime monitoring with 5-minute downtime alerts
  • Monthly forms smoke test (every contact / lead form)
  • One-page monthly report
  • 1-business-day response SLA (2 hours if site is down)
  • Written zone-of-responsibility exhibit
Not in baseline (use included or ad-hoc hours)
  • New pages, sections, functionality
  • Design changes — layouts, components, brand updates
  • Content writing — blog posts, case studies, page copy
  • SEO copywriting (we update what you write, we don't write it)
  • Plugin licenses you don't already own
  • Major version migrations (WP / PHP major bumps) — quoted
  • Image editing or sourcing
  • Migration of the site between hosts — quoted

How the hours work

1
You ask for stuff.
Email, Slack, or chat. "Update the headline." "Add this image to the team page." "New blog post here." You don't estimate it — we will.
2
We just do it.
On Active or Pro, anything within your monthly hours gets done without per-task approval. We execute on staging, send you a preview, push to production once you've seen it.
3
Heads-up at 80%.
When you've used 80% of your monthly hours, you get a note so nothing is a surprise.
4
We stop and ask at 100%.
Hit the cap and we pause. You can approve overage at $40/hr, defer to next month, or upgrade your plan.
5
Hours don't roll over.
End of the month they reset. Use them or save by downshifting — we don't carry a ledger of "we owe you 7 hours from June."

Billing, simply

One model. Same for every plan.

Monthly, post-factum. End of each month, one invoice covers (baseline fee + any overage hours used). No prepayment. You pay for the month that just ended.

Auto-charge via QuickBooks. Card or ACH on file, charged on invoice date. One number, one charge, no reconciliation.

Why post-factum? Prepay-then-reconcile is how things get tangled — pre-paid baseline, post-paid overage, partial credit for unused work. One invoice at the end of the month sidesteps all of that.

Term and cancellation

Month-to-month. Auto-renews each calendar month. No annual contract, no early-termination fee.

30 days written notice to cancel. Email us, we work through the end of the next full calendar month, that month is billed normally, then service stops.

Example: you email June 10. We continue through July 31. You're billed for June (end of June) and July (end of July). Done.

Either side can give notice on the same terms — if we ever decide we can't continue serving the account, we give 30 days and finish the month.

Getting started

1
15-minute intro call.
We walk through your site, your hosting, what you actually need. No deck. Email maxtymosh@norml.studio to book.
2
Pick a plan.
Baseline, Active, or Pro. Cloudways or your own server.
3
Sign the agreement.
Plain-English service contract sent through PandaDoc. Defines plan, billing, scope, SLA, cancellation. Your lawyer is welcome to review.
4
Onboarding (~2 hrs, included free).
We connect to your site, set up monitoring, configure backups, document the current state, store credentials securely. You're welcome on the call.
5
First monthly report.
End of month 1, you see exactly what was done, what's coming up, and the invoice for the month that just happened.

Common questions

What if I don't use my hours one month?
They expire. Hours don't roll over. Use them or save by downshifting your plan. We considered the alternative and it ends with us holding 40 hours of debt from clients who paid for them in January.
Can I change plans mid-month?
Yes. Email us. The change applies to the next billing month. We don't pro-rate inside a month — it gets messy fast.
What if you do work I didn't approve?
We won't. Anything inside your hours is fair game — that's the deal, you trade per-task approval for a lower rate. Anything above your cap requires written go-ahead. If we ever break that rule, the overage hours are on us, not you. This is written into the contract.
What if my site is on a host you don't recognize?
We'll look. Most major hosts (WP Engine, Kinsta, Pantheon, SiteGround, GoDaddy, etc.) are fine — we'll be at the $300 tier. If your host doesn't let us configure backup destinations, install monitoring, or has restrictive PHP, we might recommend migrating to Cloudways before signing. Happy to discuss in the intro call.
What about emergencies?
If your site is down, we respond within 2 hours (business) / 4 hours (off-hours), regardless of plan. Emergency response inside the SLA doesn't count against your hours. Root-cause fix time does — unless it was caused by something we did, then it's on us.
Are credentials safe with you?
We use macOS Keychain for client credentials. They never leave our machines. Backup destinations are encrypted at rest. SFTP/SSH access is per-team-member, revocable, logged.