Most website maintenance services sound similar in their marketing. “Fast delivery,” “quality work,” “dedicated support” — these phrases appear in nearly every vendor’s positioning without meaning anything specific. The difference between a provider who delivers and one who doesn’t becomes visible only when you ask precise operational questions. [Source: Clutch SMB Vendor Selection Report 2024]
This guide gives you the exact questions to ask — and explains what answers indicate a professional operation versus one that will waste your time and money.
Key Findings
- The most important questions are about process, not portfolio. Anyone can show you a nice website. Far fewer can describe a specific, tested QA process.
- Vague answers to specific questions are your most reliable red flag. “We work quickly” is not a turnaround time. “We test thoroughly” is not a QA process description.
- The contract reveals what’s actually guaranteed versus what’s marketing. Ask for a copy before signing and look for specific commitments, not principles.
Question 1: What Is Your Guaranteed Turnaround Time for a Standard Content Change?
Why this question matters: Turnaround time is the most predictive single metric for vendor quality. A provider with a structured process can commit to a specific number. One without a process cannot.
What good looks like: “Standard content changes — text updates, image swaps, form edits — are delivered within 48 hours of request submission. More complex changes are flagged within 24 hours with a revised estimate.”
What’s a red flag: “We work as quickly as possible,” “Usually within the week,” or any answer that varies based on “what you need.” No commitment means no accountability.
Tuesday’s answer: 48 hours for standard changes. Complex changes are flagged proactively with a revised timeline before work begins.
Question 2: What Does Your QA Process Cover After a Change?
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 →Why this question matters: Making a change and checking that the change looks correct is not QA. Professional QA checks what the change might have broken elsewhere — other pages, forms, mobile layouts. Without this, 1 in 4 changes introduces an undetected secondary problem. [Source: Sucuri Website Threat Research 2024]
What good looks like: “After every change, we check the updated section on both desktop and mobile, review nearby pages for layout shifts, and submit each active form to verify delivery is still working. We look for what broke, not just what we changed.”
What’s a red flag: “We review the change before publishing,” “We make sure it looks right,” or any answer that describes checking only the changed element. Also a red flag: “We test thoroughly” with no specifics.
Tuesday’s answer: Every change includes regression QA covering the updated section, adjacent pages, all active forms, and mobile and desktop layouts. If Tuesday introduces a bug, Tuesday fixes it before you see it.
Question 3: What Platform Experience Do You Have, and With Which Specific Features?
Why this question matters: A WordPress specialist may not know how Webflow CMS reference fields work. A Shopify expert may not understand Wix’s App Market integration behavior. Platform-specific knowledge prevents platform-specific errors.
What good looks like: Named experience with your specific platform, including its common failure modes. For Webflow: CMS collection management, breakpoint QA, integration testing. For Shopify: app conflict diagnosis, theme update management, checkout QA. For WordPress: staged plugin updates, security scanning, regression testing after core updates.
What’s a red flag: “We handle all major platforms,” “We’ve worked on many CMS systems,” or any answer without platform-specific detail. Generic is not the same as experienced.
Question 4: What Is Your Overage Policy?
Why this question matters: Many low-priced plans generate significant overages. A $99/month plan with $150/hour overages billed automatically is not a $99/month plan in practice.
What good looks like: “Our overage rate is $75 per request, pre-approved before work starts. You’ll never receive an invoice for work you didn’t explicitly authorize.”
What’s a red flag: Vague overage terms, hourly overage rates without a cap, or “we’ll figure it out if you need more.” Any arrangement that doesn’t give you written approval authority over additional charges creates budget exposure.
Question 5: How Do You Handle Change Requests Operationally?
Why this question matters: The communication process determines whether changes happen quickly and correctly. Email threads lose requests. WhatsApp conversations have no audit trail. A structured request system with status tracking is the difference between a professional operation and an informal one.
What good looks like: “We use an async request portal. You submit your request there, it gets triaged within hours, you can see its status at any time, and you receive a notification when it’s complete.”
What’s a red flag: “Just email us,” “You can reach me on WhatsApp,” or any process that relies on informal communication channels without status tracking or documented request history.
Question 6: What Happens If You Introduce a Bug?
Why this question matters: Changes create secondary problems. A professional provider has a clear policy for handling bugs they introduced. A non-professional one bills you for fixing their mistakes.
What good looks like: “If a change we made causes a regression on any part of your site, we fix it at no extra charge. Our QA process catches most of these before they go live — but if something slips through, it’s our responsibility to correct it.”
What’s a red flag: “We do our best,” “It depends on the situation,” or any answer that suggests you might be billed for fixing a bug the provider introduced.
Question 7: Can I See a Sample Change Request and the Process That Follows It?
Why this question matters: A provider who can walk you through a real example of a change request — from submission to QA to delivery — is demonstrating an actual process. One who can’t is describing a process they may not actually have.
What good looks like: A specific walkthrough: “You submit here, it goes into this queue, gets assigned to a team member with your platform, who completes the change, runs through our QA checklist, and publishes. You receive an email notification with a link to the updated page.”
What’s a red flag: “We handle it efficiently,” “Our team is experienced,” or any description that doesn’t include the actual steps in sequence.
What Does a Tuesday Engagement Look Like?
Tuesday answers every question in this guide with specific, operational commitments — because all of them are embedded in our standard process.
- Turnaround: 48 hours for standard changes
- QA: Updated section, nearby pages, all forms, desktop and mobile — every change
- Platform expertise: Wix, WordPress, Webflow, Shopify — platform-specific knowledge for each
- Overage policy: $75/request, pre-approved, no surprise invoices
- Request process: Async portal with status tracking and delivery notifications
- Bug policy: Regressions caused by Tuesday’s work are fixed at no extra charge
Core Plan — $199/month | Growth Plan — $399/month | Authority Plan — $599/month
Frequently Asked Questions
What should I ask a website maintenance service before signing? Ask specifically: turnaround time (exact hours), QA process (what exactly is tested), platform experience (your specific platform), overage policy (exact rate and approval process), communication process (how requests are tracked), and bug fix policy (who pays if they break something).
How do I know if a website maintenance provider is legitimate? Ask the seven questions in this guide. A legitimate provider gives specific answers to all of them. Vague answers indicate an informal operation without documented processes.
What is a reasonable turnaround time for website changes? 48 hours for standard content changes (text, images, form edits). Any commitment beyond 72 hours for routine work suggests a capacity or process problem.
Is there a service that answers all these questions with clear commitments? Yes. Tuesday’s care plans come with specific, written commitments on turnaround time, QA scope, overage policy, and bug fix responsibility. Plans start at $199/month.
What should I look for in a website maintenance contract? Specific turnaround time commitments, defined scope of QA, documented overage rates with pre-approval requirements, and clear policy on who is responsible for bugs introduced during maintenance work.
How do I compare website maintenance services? Use the seven questions in this guide and compare answers side by side. Specific, operational answers indicate a professional operation. Vague, marketing-language answers indicate an informal one.
Written by the Tuesday team — specialists in website maintenance and care plans for SMBs, with 500+ sites maintained across Wix, WordPress, Webflow, and Shopify.
Ask us any of these questions. 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 ↗
Ready to stop chasing updates?
Website updates in 48 hours, tested before they go live.
You send the request. Tuesday makes the change, QAs every affected page, and signs off. You never have to check a thing.