Most website quotes include a line for maintenance. Very few of them say what it is.
That is not usually dishonesty. It is that the word covers seven different jobs, some of which are genuinely invisible when they are being done well, and all of which are extremely visible the first time they are not.
Here is the honest version.
On a WordPress site, maintenance is these things
Updates, on a schedule, by someone who checks afterward. WordPress core, the theme, and every plugin. The applying is the easy part. The checking is the work, because an update that breaks a contact form does not announce itself.
Backups that somebody has actually restored. A backup nobody has ever tested is a folder. The question is not whether backups exist, it is when the last successful restore was and who did it.
A supported PHP version. Versions fall out of security support on a published schedule. Sites quietly keep running on unsupported ones for years, which is fine right up until it is not.
Certificates and DNS. SSL renewing on its own, and the DNS records the site depends on still intact. This is the one that bites hardest, because a website migration that rebuilds a DNS zone can silently drop the records that carry a company’s email.
Forms still arriving. Contact forms fail silently and often. Somebody should be sending a test through the form on a schedule and confirming it lands in an inbox a human reads.
Vulnerability watching for the plugins you actually run. Not general security news. The specific disclosures for the specific components on your site, which is where the real exposure lives.
Uptime and speed, measured rather than assumed. Not a dashboard nobody opens. A number somebody looks at and acts on.
None of that is interesting work. All of it is the difference between a site that is five years old and a site that is five years neglected.
The question that separates real maintenance from a line item
Whose job is each of those, and how would you know it happened?
If the answer is a monthly invoice and no report, what you have is a bill. A care plan should be able to tell you, without you asking, what was updated, what broke, what was fixed, and when the last restore was tested.
What this means on a page builder
If your site is on a hosted builder, the platform handles the platform. That is real value and worth saying plainly.
But the distinction that matters is not how much work gets done. It is who is able to do it.
On WordPress you own the files and the database. If your provider disappears, the work is portable to anyone. On a hosted builder you are renting the whole stack. The jobs the vendor does not cover are still not getting done, you cannot do them yourself, and you cannot take the site somewhere that would. Leaving means rebuilding.
That is not an argument that builders are bad. Plenty of businesses are well served by one. It is an argument that “maintenance” means something structurally different on each, and a quote that uses the same word for both is hiding the more important question, which is what happens to your site the day you want to change something the platform does not do.
What we do
diceSYTE builds so the client owns what we hand over. Most often that is Astro, with a headless CMS where you need to edit, and WordPress when that is the right fit. Every plan covers the list above, and if you ask what was updated, what broke or what got fixed, you get a straight answer.