Guide
"Website maintenance" can mean anything from a plugin update once a month to a developer on call. Here's what it should include, what it typically costs, and how to tell a fair quote from a padded one.
By Jeremy Gimbel, founder of Conflux Group · Last reviewed
A website isn't a brochure you print once. It's software, and software that isn't updated becomes a security risk. Good maintenance covers:
| Task | How often | Why it matters |
|---|---|---|
| Software updates (CMS core, plugins, themes) | Monthly, or as soon as security fixes are released | New security flaws in plugins and themes are published every week, and attackers move on them quickly |
| Backups, and testing that they restore | Daily or weekly automatic, tested quarterly | An untested backup is a hope, not a backup |
| Uptime monitoring | Continuous | So someone knows the site is down before your visitors tell you |
| Security monitoring | Continuous | Catches malware and suspicious logins early |
| Hosting and domain oversight | Ongoing | Renewals, SSL certificates, server updates, and someone who talks to the host for you |
| Small changes and content help | As needed | The "can you just…" requests every organization has |
| An annual review | Yearly | What's working, what's aging, what to plan for next year's budget |
Sometimes included, depending on the provider and the site:
| Task | How often | Why it matters |
|---|---|---|
| Performance checks | Quarterly | Sites slow down as content and plugins accumulate |
| Accessibility checks | Quarterly, or after major changes | New content and features can introduce barriers, such as missing alt text or unlabelled forms |
What's usually not included: redesigns, new features, major version upgrades (for example, Craft 4 to Craft 5), content writing, and day-to-day content updates you can make yourself in the CMS. Those are projects, or your own team's work. A good maintenance agreement says so clearly, so there are no surprises.
When a client asks us what to budget for a site that's already built, we give them two numbers, and a reminder about a third.
| What it covers | What we tell clients to budget |
|---|---|
| Maintenance and support: updates, backups, monitoring, hosting oversight, and help when something goes wrong | Roughly $3,500–7,000 per year |
| Upgrades and changes: new features, major version upgrades, design changes, the projects that come up every year | Another $5,000–10,000 per year, set aside |
| Fixed costs: hosting, domain names, software and plugin licences, and the platforms your site is integrated with, such as donations, ticketing or email marketing | Depends on your setup. Usually paid to those providers directly |
The second number is the one most organizations leave out. A website budget usually covers the build and then stops, but every site needs changes after launch, because your organization changes. Setting money aside each year turns those changes into planned work instead of emergencies, and it's what keeps a site from drifting toward an expensive rebuild.
These are planning figures for a typical small organization's site, not a quote. A simple site with few plugins sits at the low end; a site with donation, ticketing or membership integrations sits at the high end, or above it.
Maintenance is usually sold in one of four shapes.
| Type of plan | What you get | Typical range |
|---|---|---|
| Basic care plan | Updates, backups, monitoring. Little or no developer time. | Roughly $100–300 per month |
| Care plus support hours | The above, plus a set number of developer hours for changes | Roughly $300–600 per month |
| Retainer | A larger block of hours, priority response, ongoing improvements | $1,000+ per month, set by the hours included and usually discounted compared to ad-hoc hourly rates |
| As-needed / hourly | Pay when something needs doing | Roughly $80–200 per hour |
Our maintenance figure of $3,500–7,000 per year works out to roughly $300–600 per month, the "care plus support hours" range. The upgrades budget and the fixed costs are the parts these plans don't cover.
Probably yes, if your site runs on a self-hosted CMS, takes payments or donations, collects personal information, or would cost you real money or reputation if it went down for a day.
Probably not, if you're on Squarespace, Wix or a similar hosted builder, and someone on staff is comfortable making content changes. The platform handles the technical upkeep. You might want occasional help, not a plan.
Usually nothing, for a while. Then, typically, one of three things:
Ask every provider the same questions:
A provider who answers all seven clearly, without hesitation, is likely to be a good one.
Questions
No, though some companies bundle them. Hosting is the server your site lives on. Maintenance is the work of keeping the software on that server current, secure and backed up. Many hosts offer basic automatic updates, but rarely the testing, monitoring and human judgement that real maintenance involves.
Hosting is usually billed separately, as one of the site's fixed costs. Whoever manages it, the account itself should be in your organization's name. Then changing maintenance providers never means moving your site.
On a simple site, partly. Updating plugins through the dashboard is straightforward. What's hard is knowing when an update is safe, noticing when something has quietly broken, and fixing it when it has. That's the part people pay for.
For a well-built small site, very few. The routine work is often an hour or two per month. Hours beyond that go into changes and improvements, which is why many plans bundle a block of developer time.
Many providers do, and it's always worth asking. We offer nonprofit rates for organizations working with tight budgets.
Get started
Tell us what your site is built on and what you're paying now. We'll tell you honestly whether it's fair, and whether you need us at all.