A maintenance package is something often offered in a single sentence — “updates, backups, security” — and the client nods because they don’t want to look foolish. But in reality, it remains unclear what lies behind those words, how much work is actually done, and why it should be a monthly paid service rather than “we’ll call you if something breaks.” Website maintenance is one of the few expenses whose value becomes apparent primarily when it is NOT there — and by then, it is already many times more expensive than a year’s worth of maintenance fees. In this article, I will break down what actually fits into a base package, why I recommend the monthly model over “repair when broken,” and how to decide if the €35/month level covers your needs.
What actually fits into a base package
When I say that maintenance starts at €35 + VAT per month, there are five specific things behind it. Not “you get peace of mind” — that’s a sales pitch that doesn’t help you decide anything.
WordPress core, plugin, and theme updates. Every week, updates are reviewed. Core and critical security updates are installed immediately. Major changes (for example, a major plugin version) are first tested in a staging environment (a test copy that does not affect the live site) and only then implemented for real — so if something breaks, I can fix it before any visitor sees it.
Backups outside of your server. This is a detail where most “I do my own backups” answers stumble. If the copy is on the same server as the site itself, a server crash takes down both. A proper package means the copy is kept in a separate cloud — and it has been tested quarterly to ensure that restoration actually works.
24/7 security monitoring. Patchstack (a security monitoring service that tracks known vulnerabilities) constantly scans your plugins. If a security hole is discovered in the world that exists on your site, temporary virtual protection is often sent even before the official plugin fix is released.
Reliability monitoring. A check every five minutes to see if the site is working. If it goes down — I send myself a notification and can react before you even open your inbox in the morning.
A monthly report that isn’t nonsense. One A4 page with a message about what was done, what is pending, and what requires your decision. Not a 12-page PDF that nobody reads.
Why monthly, not “call us when it’s broken”
This is a fair question and I don’t mind it being asked. The logic is simple: a one-time restoration job after a problem often costs more than a year’s worth of preventive maintenance combined.
Simple calculation. Malware removal from €150. Proper restoration from a backup (which you have to buy first because you didn’t have one) €300–600. Removing a “dangerous site” label from Google takes a few weeks, during which the site essentially does not exist. One such crisis eats up the entire year’s maintenance budget and leaves you with reputational damage on top. A monthly package is preventive — you don’t pay to fix a disaster, you pay to ensure the disaster doesn’t happen in the first place.
Another thing often overlooked: maintenance is not just “updating.” It is also communication. If a question arises during the month like “how do I change this image” or “how do I block this contact form spam,” the base package usually includes 30–60 minutes of small changes. Having someone you can write to — without every email resulting in a new invoice — is a value in itself.
A typical maintenance month — what I actually do
To keep it from being abstract, I will describe week by week what happens to one client’s site during the month. Concrete, real.
First week. ManageWP (a tool that consolidates all my clients onto one panel) shows that two plugins have updates. One is a standard functional update, the other a security update. I check the changelog (list of update changes), make a backup, install, and check that the site is working. Twenty minutes.
Second week. Patchstack sends a notification — a vulnerability has been discovered in one plugin, and there is no official fix yet. The plugin receives automatic virtual protection. I review whether this plugin is even necessary for the client. If not — I remove it. Fewer plugins = less risk.
Third week. I check the site speed (PageSpeed Insights), review newly uploaded images (did someone upload a 4 MB file from their phone), and optimize them into WebP format. I take a look at Search Console — to see if Google is showing any errors.
Fourth week. Report to the client. “Seven updates were made this month, 23 brute-force login attempts were blocked, site speed increased from 78 to 84. Next month, I recommend looking at the contact form because it is sending spam.” Three lines of necessary information.
If you divide these hours by €35, you understand quite clearly that this is not a get-rich-quick model for me. It is a volume model — little from one client, sustainably from many.
When €35 is enough and when it is not
Honest answer: it depends on what your website earns for you.
If the site is essentially a business card — a few pages, contact info, some service descriptions, the client finds the info and then calls — then the €35 base package covers what is necessary. There isn’t high traffic, there’s no e-shop, and nothing major changes monthly.
If the site generates sales — an e-shop, booking system, rental-based service — then €35 is likely below the alarm threshold. For e-shops, monthly packages range between €60–120, and the reason is simple: WooCommerce involves more plugins, more risk areas, more testing after every update, and payment logic that must not break. One hour of downtime during peak orders can eat up an amount equal to the monthly fee.
If the site is an active content site or blog — where you write regularly, add images, and make changes yourself — then an intermediate package (about €50–70) gives you more volume for small changes per month. Reason: you are on the site more yourself and questions arise more frequently.
I wrote a separate maintenance price overview where the package levels are broken down — along with what is often missing from quotes (hidden costs that come as separate invoices).
How to understand where you stand right now
If you’re not sure whether maintenance is even active on your site or if there’s just a bit of a backup with your old hosting — here are a few things you can check yourself.
Log into WordPress. Look at the “Updates” number at the top. If it’s under five and the last updates are a month old, someone is likely doing it. If the number is over 20 and includes a core update — they are not.
See if you know where your backup is. Not “somewhere in the hosting panel” — exactly where, as of what date, and how you would restore it. If the answer is “uh, I have to check,” then essentially it doesn’t exist.
Read also the previous article why a website needs regular maintenance — it explains exactly what happens if you don’t do maintenance at all and in what order things start to break.
If you want me to review your site once and tell you honestly whether you need maintenance or not — send the site address to . I will answer specifically: what is in order, what is not, and whether the €35 base package covers your needs or if it’s worth looking at something larger. It is harmful to both parties if I sell you a package that doesn’t fit.
€35 per month is an amount where deciding usually takes more time than the value is worth. In the time you spend thinking “is this important for me,” you could have already paid for the first month and known for sure.
Frequently Asked Questions
Can I update WordPress myself and save on the monthly fee?
Technically, yes. But you should know in what order to install updates, how to make a backup beforehand, how to check the update in a test environment first, and how to restore if something breaks. If one restoration job costs €300–600, a monthly €35 is usually the cheaper path.
What is the difference between a maintenance package and a server service?
A server service (hosting) is the place where your site physically lives — disk space and database. A maintenance package is keeping the software itself — WordPress, plugins, and theme — in order on that server. Two different things, both are necessary.
Does the package also cover adding new content or major changes?
The base package usually includes 30–60 minutes of small changes per month — changing a new image, a short text change, updating contact info. Larger tasks (new page, new feature, design change) are handled as a separate project. The report states what was included within the month.
What happens if I already have a backup with my hosting provider?
It likely won’t help when you need it most. If the server itself crashes, the account is closed, or the site is hacked, the hosting backup often disappears along with it. A proper backup is located in a separate cloud and has been tested to ensure it actually restores.
Is there a long contract and a commitment fee for maintenance?
There is no long contract with me. The maintenance package is month-to-month and can be canceled at any time — in case of cancellation, I will perform one last backup and give you the access details so you can proceed with the site peacefully wherever you choose.
