01
CMS & plugin updates
WordPress core, themes, and plugins updated on a planned cadence — with eyes on breakage before your homepage surprises you.
Nonprofit website maintenance
Keep the site healthy after launch day.
CMS updates, backups, security and performance monitoring, content changes, and light development — ongoing support for mission-driven websites that cannot wait in a ticket queue forever.
The problem
Launch is not the finish line. It is when the real ownership starts.
Plugins age. Forms break after an update. Someone needs a landing page by Thursday. Without a care plan, small issues pile into a redesign you did not budget for. Maintenance is the boring work that protects trust — and frees your team to focus on programs instead of WordPress admin screens.
What's included
Care for the rooms you already built.
Exact hours and tooling are agreed per plan. This is the work we typically cover for WordPress and Next.js sites we maintain.
02
Security monitoring & backups
Malware scanning where applicable, access hygiene reminders, and backup verification so restore is not a theory.
03
Hosting oversight
We can recommend and set up hosting, or work with your existing host — monitoring uptime and performance signals either way.
04
Performance & broken-link checks
Core page speed watch-list, obvious regressions, and broken links that frustrate donors and volunteers.
05
Forms, analytics & accessibility spot-checks
Donation and contact forms tested after updates. Analytics tags verified. Accessibility regressions flagged when we touch templates.
06
Content updates & light development
Staff bios, program pages, landing pages, and small design or development improvements within agreed monthly support hours.
Scope clarity
Hosting, maintenance, and development are not the same job.
| Area | What it means | How CauseHouse treats it |
|---|---|---|
| Hosting | Where the site lives — servers, DNS, SSL, environments. | Recommend, configure, or coordinate with your host. Not the same as writing features. |
| Maintenance | Keep the site healthy: updates, backups, security, monitoring, small fixes. | Core of a support retainer. Predictable monthly care. |
| Ongoing development | New templates, integrations, redesign sections, larger UX work. | Scoped separately or drawn from retainer hours when capacity allows. |
Who it's for
Teams that need a reliable web partner between projects.
- Nonprofits on WordPress who want updates handled without drama
- Orgs that launched with us — or elsewhere — and need ongoing care
- Small teams without a full-time web person on staff
What is not included
- Full website redesigns or replatforms (those are project engagements)
- Unlimited rush work outside agreed hours without a conversation
- Legal compliance certification or ADA legal advice
- Managing every third-party SaaS you use — unless it is in the written scope
Related
When maintenance is only part of the answer.
Nonprofit web design
When maintenance is not enough and the site needs a real rebuild.
Explore →Nonprofit SEO servicesOngoing search work that pairs well with a healthy, updateable CMS.
Explore →Institutional website risk reviewIf you are unsure whether to maintain, remediate, or redesign — start with the risks.
Explore →Website redesign guideBudgets, timelines, and post-launch support questions boards ask before they rebuild.
Explore →Questions
Before we talk hours and hosts.
- Which platforms do you support for maintenance?
- Most often WordPress (including ACF or Elementor Pro setups). We also maintain custom Next.js sites for teams with a clearer engineering context. If your stack is something else, we will say whether we are the right fit before you sign anything.
- What is the difference between hosting, maintenance, and ongoing development?
- Hosting is infrastructure. Maintenance keeps that infrastructure and CMS healthy. Ongoing development adds new capabilities. Retainers usually cover maintenance plus a block of hours for content and light development — larger builds get their own scope.
- How do support plans work?
- We agree on monthly hours, what is included, and how requests are submitted. Unused hours and rollover rules are written into the agreement so expectations stay clear. We do not publish one-size pricing here because scope varies by CMS and traffic.
- What are response-time expectations?
- Routine requests are handled inside the monthly cadence. Urgent production outages are prioritized. Exact response windows depend on the plan we agree — we will not invent a number on a marketing page that your contract does not match.
- Is emergency support unlimited?
- No. We stabilize true site-down or security emergencies as a priority, then review hours and next steps. Emergency work can consume monthly hours or become a separate invoice depending on your agreement.
- We already have a developer. Can you still help?
- Yes — sometimes as a second set of eyes for updates and monitoring, sometimes as overflow for content and campaign pages. Coordination with your developer is welcome when roles are clear.
Start building