Website Maintenance Packages

A one-page agreement. New plans start with an initial term that covers onboarding and the first stretch of maintenance; after that, plans run month to month and you can change or cancel with 30 days’ notice. Prefer to skip the term? We can estimate onboarding as a project up front and run month to month from the start. Most clients change plans at some point, up for a campaign, down for a quiet stretch. That’s expected, not a renegotiation.

Anything beyond the baseline maintenance: content changes, bug fixes, small features, design tweaks, landing pages, integrations, performance polish, and consulting on what to do next. It’s a monthly budget of attention; you direct it, and on the higher tiers we also spend it proactively.

Because the site doesn’t need it. Monthly updates with security patches applied within a business day or two is the right cadence for nearly every WordPress site; more churn adds risk, not safety. The higher tiers buy attention: more developer hours, and a developer who looks for problems instead of waiting to hear about them.

Most of the time, an update really is as simple as hitting the button. The difference is what happens around it. When DD9 runs updates, they go onto a local and a staging copy of the site first. We QA them there, deploy precisely the same updates we just tested, then QA again on the live site.

You can probably hit the buttons yourself for a while without anyone watching. Eventually one of them brings the site down, or worse, quietly breaks something critical: a form that stops sending, a checkout that stops charging, and nobody notices for weeks. And the update screen only tells you about plugins that still ship updates. The abandoned ones look fine right up until a vulnerability lands.

So the secret is: you can do it yourself for a while, and you will very likely get into trouble at some point. The plans exist so that point never comes.

No. That’s the point of a monthly budget. Send the request, we do it, and you can see where the hours went any time you ask. We only stop to talk when something is clearly bigger than the month, and then you get a straight answer: add hours, estimate it as a project, or move up a tier.

On Support and above, recovery is included for any site that has been in our maintenance routine. We take it seriously and we take it personally. In fifteen years no site under our active maintenance has been compromised, which is the real reason the baseline looks the way it does: current software, hardened logins, monitoring, and someone actually watching.

We tell you before starting. You can add hours at your plan’s rate, have us estimate it as a small project, or move up a tier if it keeps happening.

No. We work with the site wherever it is hosted. We do have preferred environments that integrate tightly with our Git-based workflow, so we are more efficient on some hosts than others, but we never force a move. If hosting is part of the problem we’ll say so.

Yes. Access and account recovery is part of onboarding on every plan, including registrars, DNS, hosting and WordPress admin.

Yes, on a Custom plan. Those systems have more moving parts than a marketing site, so we scope the plan around them rather than squeezing them into a flat tier. Our WordPress development page covers the kinds of systems we build.

DD9’s own developers in Boulder, Colorado. The same team that builds our client sites handles maintenance, so there is no hand-off to a separate support tier.

Yes. Maintenance clients get priority scheduling on larger projects, and the audit from onboarding usually tells us exactly where a redesign would pay off.