For a lot of small nonprofits, the honest answer is: nobody. And that's not a moral failing — it's a job that never got assigned.
The short version: the day your site launches is the day the real work starts — and it's the work almost no one plans for. A website isn't a thing you finish; it's a thing you keep. When keeping it is everyone's job, it's no one's, and it slowly rots: broken links, an expired plugin, a donation button that quietly stopped working three weeks ago. This guide names the actual jobs, lays out who can own them, tells you what each option really costs, and helps you spot the moment it's worth making upkeep someone's explicit job.
Up front: I run a studio (MissionAssist) that offers this as a paid service, so I'm not neutral. I've tried to earn your read the usual way — the cheapest fix that solves your problem gets named plainly, even when it isn't me. For plenty of orgs the right answer is "assign it internally" or "buy a basic care plan," and you'll find both below.
Key takeaways
- A website is kept, not finished. Launch is the start of the maintenance clock, not the end of the project.
- "Nobody's job" is the default failure mode for small orgs — not because anyone dropped the ball, but because upkeep never got named as a role.
- It's five distinct jobs, not one — and most of them are invisible until something breaks.
- The real risk is continuity: the volunteer or agency who "handles the website" leaves, and the passwords and know-how leave with them.
- You have cheaper options than a full-time hire — assign it internally, buy a basic care plan, or bring in an ongoing partner. Match the option to how much your site actually matters to your mission.
Who is actually supposed to maintain a nonprofit website?
For most small nonprofits, no one is — not on paper. The site got built by a volunteer, a freelancer, an agency, or a staffer wearing six hats, and once it launched, ownership of keeping it running was never handed to anyone. So it becomes a background task that surfaces only in a crisis: the site goes down the week of your gala, or a funder emails to say your "Donate" link is broken.
That's the pattern behind the phrase you've probably muttered yourself — it's nobody's job. It's the single most common gap I see in small-org digital, and it's almost never anyone's fault. You can't assign a role no one told you existed.
What does "website maintenance" actually involve?
More than most people think, and most of it is invisible right up until it isn't. Here are the five jobs hiding inside "keep the website running":
- Security and updates. Your CMS, plugins, and themes need regular updates. Skip them and you're one known vulnerability away from a defaced site or a data leak — a real problem when you're holding donor information.
- Uptime and backups. Someone has to notice when the site is down and have a recent backup to restore from. "We'll just rebuild it" is not a backup plan.
- The money paths. Your donation form, event registration, and email signups are the parts that quietly break in ways no error message announces. A broken donation page is lost revenue every hour it's down — and no one's watching the checkout.
- Content and accuracy. Last year's board list, a program you no longer run, a dead PDF link. Small rot, but it's what a first-time visitor sees.
- Small improvements. The site should get a little better over time — faster, clearer, more accessible — not just not-broken. This is the job that never happens when upkeep is a side task.
The difference between a site that compounds and a site that decays isn't budget. It's whether these five jobs belong to someone.
Who updates the website after the agency or volunteer leaves?
This is the question that catches orgs off guard, and it deserves its own answer, because it's where "nobody's job" turns into a genuine emergency.
Nonprofit teams turn over. Volunteers move on; agencies finish a contract and roll off; the one staffer who "just knew how the website worked" takes a new role. When they go, two things often walk out the door with them: the passwords (domain, hosting, CMS, analytics, the donation platform) and the know-how (how it's wired together, where things live, what not to touch). Orgs discover this at the worst possible moment — when they need to change something and realize no one can even log in.
Two moves protect you here, and you can do the first one this week for free:
- Own your accounts. Every account — your domain, hosting, CMS, email, donation tool, analytics — should be registered in the organization's name and email, not a person's. This is the single highest-leverage thing you can do, and it costs nothing. (More on this in The Nonprofit Website Checklist.)
- Write down the map. A one-page doc of where everything lives and who has access turns a departure from a crisis into an afternoon.
If you've already inherited a site and no one knows how it works, that's a common and fixable situation — the first step is an honest look at what you're holding. The free Website Grader will tell you what's working and what's quietly broken, no login required.
Who should own it — and what does each option really cost?
There's no universally right answer, only the right fit for how much your website actually matters to your mission. Rough ranges for the US small-nonprofit market, 2026 — anchors, not quotes.
| Who owns upkeep | Best for | Watch out for | Rough cost |
|---|---|---|---|
| A staffer, as a named duty | Orgs with a capable, willing staffer and time carved out for it — on purpose, in their job description | It's real hours, not a rounding error; it evaporates the moment they're busy or leave; needs a backup | Staff time (budget a few hours/month) |
| A basic care plan | Keeping the lights on — updates, backups, uptime, security patches | Patches and monitors; it does not improve anything or answer "can we…?" questions | ~$300–$1,000/mo |
| The original builder, on retainer | Continuity with whoever built it, if they offer ongoing support | Not everyone does; response times vary; get "what's included" and "how fast" in writing | Varies; often a monthly plan |
| An ongoing digital partner | Orgs whose site is core to fundraising or programs and needs to keep improving, not just not-break | Priced above a care plan because it's more than maintenance; overkill if you only need patching | ~$2,000/mo and up |
| Nobody (the default) | Nothing — this is the failure mode, not a choice | Quiet decay; a crisis at the worst time; lost donations no one traces | "Free," until it costs you a gala week |
(Deciding between a freelancer, an agency, and a partner in the first place is its own question — DIY, Freelancer, or Agency? walks through it. That's about getting help; this is about who keeps it running afterward.)
The jump from a $300 care plan to a $2,000 partner is the one people ask about most. A care plan keeps your site alive. A partner keeps it getting better — improving the donation flow, tightening the site's speed, reporting on what changed and what it moved — and gives you someone to call when something breaks or an opportunity appears. If all you need is patching, don't overpay; buy the care plan. The partner earns its place only when your digital tools are central enough that steady improvement pays for itself.
How do you know it's time to make upkeep someone's job?
When the cost of "nobody's job" starts showing up. A few honest signals:
- You've been locked out of an account, or you're not sure who controls your domain.
- Something on the site has been broken for a while and no one owns fixing it.
- A donation or signup form failed and you found out from a donor, not a dashboard.
- Every website change waits on one busy person — or one person who's already gone.
- You keep meaning to improve the site and it never rises above "on fire."
If two or more of those ring true, the fix isn't necessarily hiring anyone. Sometimes it's assigning the role internally and writing down the map. Sometimes it's a cheap care plan. And sometimes — when the site genuinely carries your fundraising or your programs — it's worth having a senior partner whose actual job is to keep it healthy and improving. That last one is what we do in Capacity; the goal there isn't to make you dependent, it's to build your team's confidence so the arrangement keeps earning its place.
FAQ
Who is supposed to update a nonprofit website? In principle, whoever the organization assigns the role to. In practice, at most small nonprofits no one is formally assigned, so it defaults to "nobody" and the site slowly decays. The fix is to make it an explicit job — internally or through a partner.
How much does ongoing website support cost? Basic care plans that handle updates, backups, and security run about $300–$1,000 a month. A partner who also improves the site, measures results, and advises on decisions typically starts around $2,000/month. If you have a capable staffer, the "cost" is a few hours of their time each month — as long as it's genuinely carved out.
A volunteer built our site and then left. What do we do? First, regain control of your accounts — domain, hosting, CMS, donation tool — and get them into the organization's name. Then get an honest read on what you're holding; the free Website Grader is a fast, no-login way to see what's working and what's broken. From there you can decide whether it needs a fix or an owner.
Can't we just handle maintenance ourselves? Absolutely, if you have someone with the time and the skill — and we'll say so plainly. The trap isn't doing it yourself; it's assuming someone's doing it when no one is. If you assign it as a real duty with a backup, DIY works fine.
Is a $2,000/month partner overkill for a small org? Often, yes — and if it is, we'll point you to a cheaper care plan. It's worth it only when your website is central enough to your fundraising or programs that steady improvement pays for itself. If you mainly need patching and peace of mind, buy the care plan, not the partner.
MissionAssist.digital is the digital agency inside Tomorrow Labs — technology that advances your mission, without adding to your workload.
Start here (free): Not sure what shape your site is in? Run the Website Grader — a few minutes, no login, and you'll see what's working and what's quietly broken. Prefer the bigger picture? The Nonprofit Digital Audit shows where your whole digital setup stands.
When you're ready to make it someone's job: Capacity is an ongoing partnership for orgs whose website has outgrown "nobody's job." Or just book a short call and we'll help you figure out whether you need a partner, a care plan, or a name in a job description — even if it isn't us.
Author: Weston Cox — founder of Tomorrow Labs and MissionAssist; a decade in nonprofit digital. Portland, OR.