Most business owners don’t know what professional website maintenance looks like because they’ve never experienced it. They’ve experienced slow agencies, unreliable freelancers, and DIY maintenance with no process. Good maintenance feels different. Here’s what it actually includes.
Key Findings
- Good maintenance has a defined process for every change — not just the change itself. Before, during, and after the change, specific things happen. The client can describe this process and so can the vendor.
- The client’s time involvement should be minimal. Submit a request in plain language. Receive a completion confirmation. That’s the ideal interaction. Any process requiring more client involvement is a process problem.
- QA is the defining characteristic of professional maintenance. A vendor who makes changes without testing is not doing maintenance — they’re doing editing. Maintenance includes responsibility for the post-change state of the site.
What Good Maintenance Looks Like at Each Stage
Receiving the request
Good: The client submits a request in plain language — “Update the pricing on the services page to reflect our new rates” or “Add Sarah Johnson to the team page with the attached photo and bio.” The vendor acknowledges receipt with a completion timeline.
Not good: The vendor asks for a brief, a project plan, or a video call before starting simple changes. Back-and-forth about scope before implementation.
Implementing the change
Good: The vendor makes the change on the live site (or a staging environment), implementing exactly what was requested without substituting their judgment for the client’s unless the request would break something.
Not good: The vendor “improves” the design beyond what was requested, delivers something different from what was asked, or requires multiple revision rounds for a simple change.
Testing after the change
Good: After implementation, the vendor:
- Verifies the updated element is correct on desktop
- Verifies the updated element on mobile (375px minimum)
- Checks that surrounding sections and adjacent pages are unaffected
- Tests all forms on the updated page by submitting a test
- Verifies all CTAs on the updated page link correctly
- Notes whether any regression was found and either resolves it or flags it
Not good: The vendor looks at the change on desktop, confirms it looks correct, and marks it done.
Delivering the result
Good: The vendor notifies the client that the change is live with a link to the updated page. Any issues found and resolved during QA are noted. If a regression was found that the vendor introduced, it’s already fixed before the notification.
Not good: The vendor sends a link and waits for the client to check and provide approval before closing the task.
What Good Maintenance Looks Like on a Monthly Basis
From Tuesday
Get website updates done in 48 hours — tested before they go live.
You send the request. We make the change, QA every affected page across desktop and mobile, and sign off before anything goes live. No follow-ups needed.
Book a free 15-min call →Beyond individual change requests, good maintenance includes a monthly baseline:
- Form testing. Every form on the site is submitted and delivery is verified. Any form failure is resolved before the monthly report.
- Mobile check. Key pages are loaded on a real mobile device and checked for layout issues.
- Performance monitoring. Page speed is checked against the previous month’s baseline. Degradation triggers investigation.
- Proactive issue reporting. If the vendor finds an issue during routine maintenance — a broken link, an expired promotion, a plugin with an outstanding security patch — they flag it to the client with a recommendation.
What Good Maintenance Does Not Include
For clarity: good maintenance at $199/month does not include full website redesigns, custom feature development, paid advertising management, large-scale content production, or full-scale SEO campaign management. These are separate engagements with separate scopes. Knowing what’s included and what’s not is part of what makes good maintenance predictable.
What a Tuesday Engagement Looks Like
Tuesday’s process matches the description above: async request submission, 48-hour delivery, full regression QA before notification, and monthly baseline testing.
Core Plan — $199/month:
- 10 change requests per month
- 48-hour standard turnaround
- Full regression QA on every change — updated section, adjacent pages, forms, mobile
- Monthly form testing protocol
- Works on Wix, WordPress, Webflow, and Shopify
Frequently Asked Questions
What should I expect to do as a client in a good maintenance engagement? Submit requests in plain language. Review completions when notified. That’s it. Any maintenance engagement that requires more ongoing involvement from you has a process problem.
How do I know if my current vendor is doing QA? Ask them to describe their testing process after a recent change. If the answer doesn’t include forms, mobile, and adjacent pages, they’re not doing regression QA.
What should the change completion notification include? A link to the updated page, confirmation that QA was done, and any issues found and resolved. If the vendor found a regression they introduced and fixed it, that should be noted.
Is there a service that provides this level of maintenance? Yes. Tuesday’s Core Plan at $199/month delivers this process on every change request.
Written by the Tuesday team — specialists in website maintenance and care plans for SMBs, with 500+ sites maintained across Wix, WordPress, Webflow, and Shopify.
Experience maintenance done right. Get Your Free Website Audit →
"There's almost never a need for rework. They understand what you need and deliver it right the first time."Lucas Schneider, HR · Growthnova · 5.0 ★ on Clutch ↗
Rank locally. Get cited by AI. Win more clients.
We handle your local SEO and AEO every month — so you show up in Google and in AI answers when your next client is searching. You focus on your clients. We make sure new ones find you.