Ask five agencies what their website maintenance plan includes and you will get five different lists.
Some cover hosting and nothing else. Some bundle a vague number of "support hours" that expire at the end of the month. Some promise unlimited everything and then route every request through a ticket queue where it waits a week. The owner of one consulting practice summed up the buyer's position better than any sales page:
I don't even really understand all that it means to maintain a site and to have somebody be checking on it.
That is a reasonable place to be. Most organizations buy a managed website plan once every few years, and the category has no standard definition. This post is the definition we work from, including the parts we think should not be in a plan at all.
The Baseline: What Every Plan Should Include
These are not upgrades. If a plan leaves any of them out, it is a hosting account with a support email attached.
- Hosting that someone watches. Not just a server, but uptime monitoring that alerts a person when the site goes down, before your members or customers tell you.
- Security patching. The CMS, its plugins or extensions, and the server software underneath all need updates. Someone has to apply them, test that nothing broke, and do it on a schedule rather than after an incident.
- SSL certificates kept current. Certificates expire. An expired one puts a browser warning in front of every visitor. This should never be your problem.
- Daily backups, stored off the server. A backup that lives on the same machine as the site is not a backup. Ask how quickly a restore can happen, and whether anyone has done one recently.
- A real person to call. One point of contact who knows your site, not a rotating support pool that has to rediscover it every time.
- Plain-language reporting. A monthly note covering uptime, traffic, and what was changed. If you cannot tell what you paid for this month, the plan is not doing its job.
- Access to your own site and data. You should be able to get a full copy of your content, files, and database at any time. More on this below.
None of this is exotic. It is simply the work of keeping a website running, and it is the work most often skipped when nobody is checking.
The Line That Actually Separates Plans
Once the baseline is covered, the real difference between plans is almost never the website. It is how content changes get handled.
Some organizations change their site twice a year. Some change it every week, because events, board lists, news, and program pages keep moving. Those two organizations need the same hosting, the same security, the same backups. What they do not need is the same arrangement for changes.
This is how we structure our own plans, and it is the structure we would recommend looking for anywhere:
- Essential, $95 a month. Hosting, security patches, SSL, daily backups, uptime monitoring, and a real person to call. Content changes are quoted and billed when you want them.
- Standard, $295 a month. Everything in Essential, plus a quarterly content cycle. You send changes, they get batched, and they ship on the cycle.
- Unlimited, $495 a month. Everything in Standard, plus priority response and unlimited content changes. You send the change and it gets made.
The site is identical on all three. That matters. A plan that gives you a slower server or skips security updates at the lower tier is asking you to pay for reliability in installments. Reliability should be the floor on every plan. What you choose is how much of the ongoing editing you want to hand off.
What a Plan Shouldn't Include
This is the part most buyers do not think to ask about, and it is where most of the disappointment comes from.
Custom Development Disguised as "Support Hours"
A bundle of monthly hours sounds generous. In practice, it blurs two very different kinds of work. Changing the text on a page and building a new member directory are not the same job, and pricing them the same way means one of them is priced wrong.
New features, integrations with other systems, and e-commerce should be quoted as projects, with an estimate you approve before work starts. That protects you from finding out at the end of the month that your hours went into something you did not know was expensive.
Hours That Expire
Use-it-or-lose-it hours reward the vendor for your quiet months. If a plan includes a change allowance, ask what happens to the unused part. If the answer is "it resets," you are prepaying for work that may never happen.
A Required Hosting Lock-In
Some shops will only maintain a site if they host it, and will only host it on terms that make leaving expensive. The founder of one news publisher described the feeling exactly:
It's like they got us, they literally got us right now.
A managed plan should include your data and your site files, available to you on request, and a clear process for leaving. If the software was built for you, it should belong to you in writing. The plan is a service agreement, not a hostage arrangement.
Emergency Coverage You Did Not Ask For
Around-the-clock coverage, with an engineer who answers at 2 a.m., is real work and costs real money. Most marketing websites do not need it. A member portal that processes renewals the week of a deadline might.
It should be something you choose, scoped to the systems that genuinely cannot go down, not something bundled into every plan and priced into everyone's bill. Ask whether it is available, what the response targets are, and what it covers. Then decide whether your site needs it.
Questions to Ask Before You Sign
- What exactly is included every month, in writing? Get the list. Vague is expensive.
- How are content changes handled, and how fast? This is the real difference between plans. Make sure it matches how often your site changes.
- What is quoted separately? A good answer names categories: custom features, integrations, e-commerce, major redesigns.
- When was a backup last restored, and how long did it take? An untested backup is a hope.
- Who do I talk to? A name, not a department.
- How do I leave? If there is no clear answer, that is your answer.
A Simple Rule of Thumb
A managed website plan should make reliability boring and changes predictable.
If you are still thinking about security updates, still wondering whether the backups work, or still surprised by the invoice, the plan is not doing the job you are paying for.
Final Thoughts
The best managed plan is the one you forget you have, right up until you need a change made, and then it is made the way you expected. That comes from a clear baseline, a clear arrangement for changes, and a clear line around everything else.
Buy the baseline without compromise. Choose the change arrangement that fits how your organization actually works. Keep custom work, integrations, and emergency coverage as separate, deliberate decisions.
Not sure how well your current site is being looked after? Run the free site audit. It checks security, speed, broken links, mobile layout and more across up to thirty pages, the same things a good plan keeps an eye on.
If you want to see how this looks in practice, our Managed Website plans are laid out side by side, and we are happy to talk through which one fits your site. Book a short consult.