Switching Web Agencies: How to Recognize Reliability and Good Support

By Edip Kilinc, founder of Webwavers. Published October 31, 2026. Last updated October 31, 2026. Reading time: about 17 minutes.

Short answer: A web agency is reliable when you have a fixed point of contact with a named backup, response and resolution times are agreed in writing, feedback rounds and approvals are documented, and it is clear who is responsible for hosting and outages. If two or more of these are missing and the agency does not improve after a clear conversation, switching is worth it. Before you do, secure your access credentials, your domain and the ownership of your website.

The key points in brief

• Reliability can be checked: against seven signals, not a gut feeling.
• When you ask about response time, always ask about resolution time too. A fast reply is not a fix.
• Before you cancel, secure the domain, hosting access, workspace or source code, and backups.
• A switch costs time and money. Sometimes a clear escalation conversation is the better choice.
• For business-critical sites (energy, aviation), monitoring and an emergency contact belong in the contract.

Table of contents

• When switching is worth it and when it is not
• The 7 signals of a reliable agency
• Support models compared
• Response time, resolution time and availability
• Feedback rounds and approvals
• How to check reliability before you hire
• Business-critical websites
• The switch step by step
• What belongs to you when you switch
• What a switch costs
• Handover checklist
• Common mistakes
• When staying is the better choice
• How we do it
• FAQ

When switching is worth it and when it is not

Most people who want to change agencies have already tried to fix a problem several times. The triggers are usually similar: The account manager keeps changing. Requests land in a ticket system and get answered days later. Changes that should take ten minutes take weeks. After an outage, nobody feels responsible. Or the project never clearly settled who is responsible for what, and each side points at the other.

Not every one of these is a reason to leave. A single bad month, a wave of sick leave or a staff change happens at every agency. A switch is worth it when the pattern persists after you have raised it clearly.

A simple rule of thumb:

Situation	Better option
One-time outage or error, agency responds, cause is explained	Stay and document the cause in writing
Recurring delays, but the contract contains no response times	Renegotiate response times, then decide
Rotating contacts, no overview of who is responsible for what	Escalation conversation with management, then set a deadline
Repeated outages, no accountability, no documentation	Prepare a switch
Breach of trust, unresolved invoices, refusal to hand over access	Switch and get legal advice

The most important sentence for the decision: Do not switch out of frustration, switch with a plan. If you cancel without secured access, in the worst case you lose control of your own website.

The 7 signals of a reliable agency

"Reliable" is a word every agency claims for itself. It becomes checkable when you translate it into concrete signals. These seven make a practical checklist.

1. A fixed point of contact with a named backup. You know who to turn to, and you know who steps in. This should be in writing, not just promised verbally. If your contact changes, you get a handover, not a new phone number.

2. Response and resolution times in the contract. Both times, separately, with channel and business hours. "We reply quickly" is not a commitment.

3. Documented feedback rounds. It is set how many rounds of revisions the project includes, who approves them and what happens afterward. Changes go through one fixed channel, not through WhatsApp, email and shouted requests in a meeting all at once.

4. Approvals with date and name. Every design approval and every acceptance is on record. That protects both sides when someone later says "that's not what we agreed."

5. Clear responsibility for hosting, updates and monitoring. It is stated who watches the site, who installs updates and who acts in an outage. "The agency" is not an answer. A person or a team with names is.

6. Regular reporting. You get feedback at a fixed rhythm: what was done, what was noticed, what is coming up. A short monthly report is enough. What matters is that it arrives without you having to ask.

7. Transparency about mistakes. When something goes wrong, you hear it from the agency, not from your customers. Reliable partners report problems early, explain the cause and say what they are changing.

Each signal has a counterpart you can see in the first weeks of working together.

Signal	Good sign	Warning sign	How to check
Point of contact	Name, role, backup in the contract	"The team takes care of it"	Ask for the name and the backup in the first call
Response time	Number of hours, channel, times	"As soon as possible"	Read the support section of the quote
Resolution time	Tiered by priority	Only response time mentioned	Ask: What happens after the first reply?
Feedback rounds	Number and process described	Unlimited or not mentioned at all	Read the project plan
Approvals	In writing, dated	Verbal only	Ask for a sample protocol
Hosting and monitoring	Responsible person named	Reference to a third-party provider with no accountability	Ask: Who notices when the site goes down?
Reporting	Fixed rhythm, example available	Only on request	Ask to see an anonymized report

Support models compared

What support looks like depends on the model the agency offers. No model is better in general. What matters is that it fits what you need.

Model	How it works	Strength	Weakness	Fits
Ticket system	Requests go through a portal, handled by priority	Traceable, documented	Feels impersonal, urgent items get lost when priorities are missing	Larger teams, many small requests
Hours quota	Fixed monthly time budget for changes	Predictable costs	Unused hours often expire, overage is billed extra	Regular, small adjustments
Retainer with service description	Flat fee for defined services and response times	Clear responsibility	You pay in quiet months too	Business-critical sites
Billing by time spent	You get in touch, it is billed by the hour	You only pay when needed	No guarantee of availability	Small, infrequent changes
Self-maintenance with emergency contract	You maintain content yourself, the agency steps in for technical issues	Independence, low costs	Requires know-how on your team	Teams with an editorial team, see maintaining Webflow CMS yourself

If your main problem is that changes take forever, a pure ticket system is rarely the solution. You need priority levels and a fixed resolution time for urgent items. More on this in the guide Maintenance contract: services and response times.

Response time, resolution time and availability

These three terms often get mixed up in quotes. They mean different things.

Response time is the time until the first qualified reply. It only tells you that someone has seen your report.

Resolution time is the time until the problem is fixed. It is the number that helps you in an emergency. It is usually tiered by priority: site outage, error in an important function, minor display errors, change request.

Availability is the share of time the site is reachable. A simple calculation helps here. A year has 8,760 hours. At 99 percent availability, the site may be down for roughly 87.6 hours per year, at 99.9 percent roughly 8.8 hours, at 99.99 percent roughly 53 minutes. This is our own calculation, not a market figure. If your business loses revenue during an outage, the difference between 99 and 99.9 percent is no detail.

How to ask the right questions:

• What is the response time for a total outage, and at what times does it apply?
• What is the resolution time, and what is a target value and what is a commitment?
• Who monitors the site, and how is an outage reported?
• Is there an emergency contact outside business hours?
• What happens if the commitment is missed? A contract without consequences is a wish.

Commitments with concrete numbers are not automatically better commitments, but they are verifiable. That is exactly the point.

Feedback rounds and approvals

Many project problems that later look like support problems begin in the project. If feedback is not collected cleanly, the same topics come back in round three and four. A reliable process has these elements:

1. A fixed number of rounds. For example, two rounds of revisions per phase, after which the work is replanned or billed.
2. Bundled feedback. One person on your side collects it and passes it on in one batch. Ten individual emails from ten colleagues are not a feedback round.
3. A single channel. One document, one board or one tool where everything lands.
4. Written approval per phase. Concept, design, development, go-live. Work only continues after approval.
5. A protocol. What was decided, by whom and when.

What a brief should look like so that feedback does not go in every direction in the first place is covered in the guide Briefing a web design agency.

How to check reliability before you hire

When you choose a new agency, you have a good chance of seeing the warning signs early. These steps work without you being an insider.

Hold reference calls. Ask for two or three customers you may speak to, ideally one where the collaboration has been running for a while. Do not ask "Are you satisfied?", ask: How long did the last change take? What went wrong, and how did the agency handle it? Who was your contact, and how often did that person change?

Read reviews with caution. Review portals show tendencies, but not the details you care about. Look at whether reviews get specific (response time, communication, meeting deadlines) and whether the agency responds to criticism.

Have them show their process. A reliable agency can explain its project process in ten minutes, including roles, feedback loops and approvals. If the answer stays vague, the project will probably stay vague too.

Check the quote for support. Use the checklist from the guide Comparing web agency quotes. Whatever is missing there becomes a point of dispute later.

Put awards in context. Prizes and awards say something about design quality, but little about support. How to read them is covered in the guide Design awards when choosing an agency.

Test with a small task. Before the big project, award a small, paid package, for example an audit or a landing page. In four weeks you will see how the agency communicates when things get concrete.

Business-critical websites

For some companies, the website is not a marketing tool but part of operations. This includes energy suppliers with a customer portal, aviation companies with booking and information pages, and providers with product configurators or dealer portals. Stricter standards apply here.

What belongs in the contract for such sites in addition:

• Monitoring with alerting, not just "we check regularly"
• Emergency contact with on-call duty or clearly defined hours
• Priority levels for incidents, with resolution times
• Escalation path in case the first contact cannot be reached
• Regular security updates with documentation
• Staging environment, so changes are tested before they go live
• Recovery plan with a defined time in which the site is running again after an outage

Industry-specific requirements are on the pages for Energy and Aviation. Whether a retainer with on-call duty is necessary for your case depends on what an outage costs. You should run that calculation yourself before you negotiate.

The switch step by step

Switching agencies is a small project. This order helps you avoid the most common mishaps.

1. Inventory. List everything your website depends on: domain and registrar, DNS records, hosting, platform account (for example a Webflow workspace), email mailboxes, analytics, tag manager, consent tool, form connections, CRM links, fonts, image rights.
2. Secure access. Check whose name each account is under. Where it belongs to the agency, agree on the handover before you cancel. The domain should be registered to you.
3. Review the contract. Minimum term, notice period, form of cancellation, handover provisions. If anything is unclear, have a lawyer take a look.
4. Choose a new agency. Use the checklist below and the seven signals. Tell the new agency openly why you are switching.
5. Agree on the handover. Documentation, access, backups, source code, workspace transfer. Ideally both sides sign a handover protocol.
6. Plan parallel operation. The new agency takes over operation and support while the old one is still reachable. Plan an overlap that fits the complexity of the site.
7. Cancel. Only once the handover is complete and the new agency has access do you cancel formally.
8. Follow-up work. Check DNS, test tracking, set up backups, switch monitoring, revoke the old agency's access.

If the platform changes along with the agency, the steps from the guide CMS migration checklist apply in addition.

What belongs to you when you switch

This question decides how smoothly a switch goes. The answer depends on the system and the contract.

Webflow. According to the Webflow help center, a site belongs to the workspace it sits in. If it sits in the agency's workspace, the client has no automatic right to a transfer or duplication unless that has been agreed. If the agency becomes unreachable, Webflow can neither transfer its account nor export the site. If nobody pays for the plan anymore, the site is removed (Webflow Help: Site ownership). The clean way is a transfer into a workspace you control. Billing for the site plan can sit directly with you via Client Payments (Webflow Help: Client payments).

WordPress and TYPO3. Here it comes down to hosting. If the site runs on an agency server, you need the files, the database, the login credentials and a list of the plugins or extensions in use, including licenses. Without these, a move is costly and risky.

Domain and email. Both belong in your name. If the agency registered the domain for you, have it transferred to you and check the contact details at the registrar.

Design and content. Ask about usage rights to design files, fonts, images and texts. At agencies, design files are often not automatically part of the delivery, and that should be stated in the contract.

The most important thing: Do not clarify these points only when you switch. If you are planning a new project right now, take a look at the guide Comparing web agency quotes.

What a switch costs

Flat numbers are difficult here, because the effort depends on the system, the documentation and the scope. These are the items you should plan for:

• Onboarding of the new agency. The worse the documentation, the longer it takes. The agency usually bills the effort by the hour or as a one-time package.
• Possible rebuild. If the old site is technically hard to maintain, a refactoring or relaunch comes into play.
• Double running costs. During the handover you may pay for two support arrangements.
• Your own effort. Collecting access, making decisions, testing.

For the order of magnitude of hourly rates: The adfera report puts agencies in the website field at €80 to €120 per hour and freelancers at €60 to €90 (adfera, 2026). Tricks.de gives an average of €120 for advertising agencies (Tricks.de, 2026). For ongoing monthly costs at agencies (hosting, maintenance and small changes together), adfera gives €80 to €200. A switch pays off financially when the follow-up costs of poor support (outages, missed inquiries, your own effort) are higher than the cost of switching. It is best to run this calculation honestly and with numbers from your own business.

Handover checklist

Tick off these items before you cancel formally:

1. Domain registered in my name, access to the registrar in place
2. DNS records documented (A, CNAME, MX, TXT)
3. Hosting access or workspace transfer confirmed
4. Site plan or hosting invoice runs on my account or has been transferred
5. Licenses and plugins listed, owner clarified
6. Current backup in my possession
7. Source code and files handed over (for WordPress and TYPO3), export files (for Webflow, where possible)
8. Access to analytics, Search Console and tag manager transferred to me or my new agency
9. Forms and integrations documented (CRM, newsletter, appointment booking)
10. Documentation of the structure, CMS fields and special features received
11. Design files and usage rights clarified
12. Contact at the old agency named for the transition period
13. Handover protocol signed by both sides
14. Old agency's access revoked after the handover

Common mistakes

Canceling before access is secured. This is the most expensive mistake. After cancellation, the willingness to cooperate often drops noticeably.

Looking only at the new agency's price. If you switch because the old agency was expensive and then again look only at the price, you end up switching again.

Changing everything at once. Switching support, design and platform at the same time increases the risk. Separate what can be separated.

Not asking for documentation. A new agency is only as fast as the materials it receives. Ask early.

Avoiding the conversation with the old agency. Sometimes the problem is a misunderstanding that a clear conversation can resolve. Say specifically what is not working, set a deadline and put the outcome in writing.

Treating the switch as a fresh start with no requirements. The new agency needs to know what went wrong at the old one. Write down the three most important points and require that the new contract covers them.

When staying is the better choice

A switch is not an end in itself. Stay with your agency if:

• the problems can be clearly named and solved through contract adjustments (for example fixed response times),
• the agency reacts constructively to criticism and commits to measures that it then actually carries out,
• the site is technically clean and a new agency would simply take it over anyway,
• a larger relaunch is coming up and you are better off combining the switch with that project.

And if you are missing a support model that your agency does not offer, a split can work: The current agency stays on for design and further development, another provider takes over hosting and maintenance. This needs clean agreements, but it can be a good interim solution.

How we do it

Webwavers is a premium agency for branding, web design and web development with locations in Günzburg and Munich. We work with Webflow as our focus and also build with WordPress, TYPO3 and headless systems. If you are thinking about handing a website over to us, the seven signals apply to us as well: Ask about the point of contact, the backup, response times and handover. You can find our project process on the Process page. It states that every client gets a fixed project lead and a dedicated Slack channel, and that every phase includes a feedback round with approval. Support is described under Maintenance and support, where the response time depends on the package you choose. We collect reviews from other clients on the Reviews page.

FAQ

How do I recognize a reliable web agency? By seven signals: a fixed point of contact with a backup, written response and resolution times, documented feedback rounds, dated approvals, clear responsibility for hosting and monitoring, regular reporting and open communication about mistakes. The more of these you have in writing, the more dependable the collaboration.

When is switching agencies worth it? When problems such as rotating account managers, long wait times or unclear responsibility persist after you have raised them clearly and set a deadline. A single mistake is no reason. A pattern is.

What do I need to secure before canceling the old agency? Domain, hosting or workspace access, backups, access to analytics and tag manager, a list of licenses and the documentation. Cancel only once the handover is settled, ideally with a handover protocol.

Do I own my Webflow site if it sits in the agency's workspace? Not automatically. According to the Webflow help center, the site belongs to the workspace it sits in. Without an agreement, you have no claim to a transfer. Have the transfer to a workspace you control settled in the contract.

How quickly should an agency respond in support? There is no uniform market value. What matters is that response and resolution times are agreed in writing by priority. For a total outage, you should ask for a short, concrete number, and for business-critical sites, one with on-call duty. Ask about response and resolution time, not just reply time.

How long does an agency switch take? That depends on the documentation and the system. Expect several weeks for the inventory, handover and parallel operation. For simple sites it goes faster, for complex integrations or a simultaneous platform change it takes longer.

Can I arrange just maintenance and hosting with an agency? Yes, many agencies take existing sites into support even if they did not build them. They check the state of the site first, because legacy issues make support harder. Ask for an audit before signing a contract.

Conclusion

Reliability is checkable: through the point of contact, response and resolution times, feedback rules, approvals, responsibility for operations and reporting. If you have that in writing, you rarely need to switch. If you cannot get it, even after a clear conversation, you should switch, but with secured access, a handover protocol and parallel operation. That way the website stays reachable, and you stay the person who decides about it.

Support with the switch: If you want to hand over an existing site or have it reviewed, get in touch via the contact page.

Sources

1. Webflow Help: Site ownership
2. Webflow Help: Client payments
3. adfera: Website-Kosten-Report 2026 (website cost report 2026)
4. Tricks.de: Website-Agentur Kosten und Preise (2026) (web agency costs and prices)