Yes, every business website needs occasional attention. But "maintenance" can mean very different things, and the amount required depends heavily on how the site is built. A WordPress site with plugins has a different maintenance profile from a simple static website.
This distinction matters because maintenance is often sold as though every website has the same monthly requirement.
They do not.
Some websites genuinely need active ongoing technical work.
Others mainly need occasional content changes, account checks and attention when something changes.
The fee should match the work.
Technical maintenance is real
Software changes.
Security issues are discovered.
Third-party services change.
Browsers evolve.
Dependencies update.
Domains renew.
Forms need to keep delivering.
No website should be considered something you launch and literally never think about again.
But that does not mean somebody needs to log in every Tuesday and perform mysterious maintenance.
The architecture determines the workload.
WordPress has a visible ongoing update cycle
WordPress is a live content-management system.
WordPress core changes.
Themes can update.
Plugins can update.
Official WordPress documentation recommends keeping plugins and themes current for security and performance.
WordPress also provides automatic update mechanisms.
That ongoing software surface is one of the legitimate reasons managed WordPress maintenance exists.
A provider may monitor updates, test changes, manage backups, resolve plugin conflicts and handle security.
That is real work.
Static websites are different
A static site does not normally have WordPress core, a public database and a stack of runtime plugins generating the main pages.
That removes a lot of routine maintenance.
The site can still have dependencies.
Forms can fail.
Third-party integrations can change.
Content becomes outdated.
Domain and account security still matter.
But the public runtime is often simpler.
That is why WordPress vs static maintenance deserves its own comparison.
Content maintenance is not technical maintenance
This is an important distinction.
Changing prices.
Adding a staff member.
Uploading a new project.
Updating opening hours.
Adding a service.
Publishing a guide.
Those are content updates.
They can be valuable.
They are not the same thing as patching software.
A client may need frequent content work and almost no technical maintenance.
Or significant technical maintenance and rarely change the content.
Calling everything "maintenance" hides what is actually being done.
Monitoring can be a service too
Some businesses want somebody responsible for watching the site.
Uptime.
Forms.
Security alerts.
Backups.
Broken integrations.
Performance.
That peace of mind has value.
The provider is being paid for responsibility and availability, not merely the raw infrastructure cost.
I have no problem with that.
What I object to is pretending a vague monthly charge is technically mandatory when the service has not been explained.
Gavin's take
Maintenance should follow the architecture, not the sales model. A WordPress site with plugins, a database and frequent updates can create real recurring work. A straightforward static brochure site may create very little. I am comfortable with monthly support where somebody is actually monitoring, updating or helping the business; I am much less comfortable when "maintenance" is a vague label attached to every website regardless of what needs maintained.
Does a static website need a monthly maintenance package?
Not automatically.
For a straightforward static small-business site, I would usually expect the technical maintenance burden to be low.
That does not mean zero forever.
If the client wants ongoing support, frequent content updates or monitoring, a recurring arrangement may make sense.
If they do not, I would rather charge for work when meaningful work exists.
This connects directly to whether monthly website fees are necessary.
What about security updates?
Again, architecture matters.
A WordPress site may need CMS/plugin/theme updates.
A static site may use libraries that occasionally require attention, but there is less live application software involved in serving the ordinary page.
Third-party forms, analytics and external services may also evolve.
No architecture removes security responsibility entirely.
The useful goal is reducing unnecessary attack surface and keeping the things you do use managed sensibly.
Domains need maintenance in the broadest sense
The domain needs renewing.
Account details need to stay current.
DNS should not be changed carelessly.
Two-factor authentication should remain accessible.
This is not work that justifies a large monthly fee by itself.
But it is part of the ongoing health of the website.
Forgetting a domain renewal can create a much more serious problem than forgetting to update a paragraph.
Backups depend on the architecture
A WordPress site may need database and file backups.
A static site may be reproducible from source files and deployment history.
Third-party data may live somewhere else entirely.
The correct backup plan therefore depends on what can change and where the authoritative copy lives.
I will cover that properly in how website backups work.
Content can become stale even when the technology is perfect
This is probably the most common maintenance issue for small businesses.
Old staff names.
Old prices.
Services no longer offered.
Wrong opening hours.
Dead social links.
Outdated photographs.
The website still "works".
The business information is wrong.
That can damage trust more than a slightly old software version on an otherwise secure platform.
A business website should remain accurate.
Do you need to redesign regularly?
No.
A redesign is not routine maintenance.
If the website still represents the business, works well and remains technically healthy, there is no rule saying it must be rebuilt every three years.
Content and technical upkeep can extend the useful life significantly.
I cover redesign decisions separately because they should be based on actual problems, not a calendar.
What I'd do
If I were comparing maintenance plans, I would ignore the word maintenance and ask for the actual recurring tasks. What gets checked? What gets updated? Are backups tested? Are content changes included? What happens when something breaks, and how quickly? Once the work is described in plain English, it becomes much easier to decide whether the monthly price represents useful support or simply a permanent charge attached to the website.
What should a maintenance package tell you?
If somebody charges monthly, you should be able to understand the service.
What is monitored?
What gets updated?
How often?
Are backups included?
Are content edits included?
How much support time?
Are software licences included?
What happens if something breaks?
You do not need to audit every minute of work.
You should know what you are buying.
Parts of the industry blur maintenance and retention
Recurring revenue is attractive.
That is normal business.
But there is a temptation to package simple websites with monthly "care plans" regardless of whether the site requires that level of ongoing work.
Sometimes those plans provide excellent value.
Sometimes they are little more than a recurring invoice.
The difference is the service.
Transparency solves most of the problem.
Gavin’s perspective
Built by Gavin's approach
I prefer the maintenance requirement to follow the architecture.
If I build a straightforward static business site, one of its advantages is that there is less routine software maintenance.
I am not going to manufacture plugin updates that do not exist.
If the client wants regular changes or support, that is useful work and can be priced.
If the project needs a CMS with a genuine maintenance burden, that should be explained before launch.
The ongoing relationship should be based on value.
Not dependency.
The bottom line
Yes, websites need maintenance.
But there is no universal monthly maintenance workload.
WordPress and other dynamic systems may need regular software attention.
Static sites can require much less technical upkeep.
Every site still needs accurate content, secure accounts, domain renewal and occasional checks.
Pay for the maintenance your website actually needs.
Not a vague category on an invoice.
Want to know what your current site genuinely needs?
Send me the URL or see my website approach.
I can tell you whether the ongoing burden looks like real maintenance, content work or technical complexity the site may not need.
---