We find out before you do.

More than the plans you will find advertised, and deliberately so. What sets it is how much the site does. A brochure site with a contact form is the smallest version of this; a site running a store, a booking flow or an integration other systems depend on sits higher. What we will not sell is the cheap end of the market, where a plan covers an update and a backup and includes nobody who knows your site. Taking over a site we did not build starts with a health check.

An incident is acknowledged within two hours during business hours and eight outside them, and urgent issues are resolved within twelve. High-priority work is two business days, medium is a week, low is two weeks. Anything you send us is acknowledged within one business day. Those are the numbers in the agreement, not an average. Most of the time the alert reaches us before you have noticed anything, because detection sets the urgency automatically.

That depends on what the site is built on, and the three answers below say so plainly. Everywhere: off-site backups with restores tested instead of assumed, malware scanning and security patching, monitoring for uptime, SSL expiry and whether your forms are actually delivering, and a set allowance each month for the small changes that would otherwise queue up for a quarter — copy edits, image swaps, a new link, a price change. On WordPress that also means core, plugin, theme and dependency updates, staged before they touch the live site.

The full patching surface, because WordPress is the platform with one. Core, plugins, themes and dependencies all get updated on a staging copy first, and a plugin list is something we keep arguing with rather than let accumulate — it is where almost every vulnerability in the ecosystem lives. Same standard we hold a build to; see WordPress development.

Less patching, because there is nothing to patch. Webflow has no core, no plugins and no dependencies of ours, so a Webflow plan is monitoring — uptime, SSL, form delivery — plus the work that actually moves on a Webflow site: CMS and class-structure changes, integrations that break when either end changes, and the monthly change allowance. It is improvement rather than maintenance, and it is priced as its own thing rather than as a WordPress plan with the updates removed. See Webflow development.

Theme and app updates, staged on a duplicate theme rather than the live one. Beyond that the watching is commercial: apps and integrations, inventory and POS staying in step, and the checkout path itself, because that is the part where an hour of breakage has a number attached to it. See Shopify development.

Anything that is a project instead of a change. New page templates, new sections, design work and rebuilds get scoped and quoted separately. Absorbing them into a monthly plan is how a plan quietly stops covering the maintenance it was bought for. Ranking work belongs with SEO & AEO, workflow automation with Automation & AI, and a rebuild with website redesign.

Yes, and it starts with a health check. We go through the platform and its version, the plugins and dependencies, what is out of date, what is insecure, how it is hosted and who actually holds the accounts. Then we tell you what you have and what it costs to keep. If the codebase is not safe to maintain we will say so, and that answer is worth the health check on its own.

WordPress, Webflow and Shopify, plus anything we built ourselves. We do not maintain Squarespace, Wix or other hosted site builders. They do not give an outside team the access that makes real maintenance possible, so anyone selling you a maintenance plan on one is selling you content edits. You will hear that on the first call instead of three weeks in.

We can, and it is billed separately from maintenance. Sites we host run on Kinsta: the account is ours, your team holds administrator access to it, you pay us and we pay them. The plans are published on our hosting page. If you already have hosting you are happy with, keep it. We maintain sites on hosting we do not provide all the time, and if the hosting itself turns out to be the problem you will hear that too.

No. Managed hosting keeps the server patched and usually applies core updates. It is priced accordingly, and that is roughly what it is worth. It does not test that a plugin update broke your booking form. It does not notice that your contact form stopped delivering three weeks ago. And there is nobody on the other end who knows how your site was built. Those are the failures that actually cost you something.

Yes, if you have one and this is genuinely part of their job. It stops working when it is nobody’s job in particular. Maintenance is invisible when it is being done and expensive when it is not, so it is the first thing to lose a fight with a deadline. The honest test: could anyone on your team tell you today which plugins are out of date and when the last restore was tested?

We clean it up, and on a plan it is treated as an incident under the response times above. Cleanup gets quoted separately when it is a site we have not been maintaining. A one-off cleanup buys you a clean site, not an explanation of how it happened. On a maintained site we know what changed and when, which is usually the difference between an afternoon and a week.

No. Plans are month to month with 30 days’ notice. The domain, the repository where there is one and the logins are yours throughout. Where we also host the site, the Kinsta account is ours and your team holds administrator access to it, so nothing about your own site is hidden from you and nothing has to be prised back. If you leave, we stop. A maintenance plan that depends on you being unable to leave is not a maintenance plan.

No. This covers the site itself. Search and answer-engine work is a separate retainer, and so is workflow automation. Clients pair two or three of them when it makes sense, and plenty run just this one. We would rather you bought the one you need than a bundle you do not.