Changing agency is disruptive and expensive, so people put it off well past the point of sense. Here are the signals that mean it is time and the ones that mean have a conversation first.
Change agency when work is consistently late without explanation, when you cannot get a straight answer about what you own, when the same problems recur, or when they cannot show what their work achieved. Have a direct conversation first, since many problems are caused by unclear scope rather than incompetence, and a rebuild you did not need is expensive.
Signals worth acting on
- You cannot get a straight answer on ownership. Ask who owns the domain and code. Hesitation is the answer.
- Results are never measured. If nobody can say what the last twelve months achieved, nobody was aiming at anything.
- The same problem recurs. Fixed, returns, fixed again, and nobody has asked why.
- You only hear from them at invoice time.
- Every request becomes a change order, including things any reasonable person would consider in scope.
- They will not let you talk to whoever does the work.
Signals that mean talk first
| Symptom | Often actually |
|---|---|
| Work feels slow | Scope grew without the timeline being renegotiated |
| Results plateaued | Budget or market changed, not effort |
| Communication dropped off | Your account manager left and handover failed |
| Costs rising | Genuine cost increases, or scope you added incrementally |
| Design not what you expected | Brief was thinner than both sides assumed |
Most of these improve after one honest conversation. Switching agency resets the relationship and also resets all the context they had built, which has real value.
Before you leave
- Read your contract for notice period and termination terms.
- Confirm you have domain registrar access in your own name.
- Get a full backup of files and database, and verify you can open it.
- Collect design source files, not only exported images.
- List every third-party account and whose name it is in.
- Export your analytics history before access changes.
- Document any custom functionality nobody else understands.
Do this while the relationship is still civil. It becomes considerably harder afterwards.
Choosing the next one
Ask the new agency the questions the last one failed. Who owns the code. What happens if we leave. What will you measure. Who does the work day to day. What is explicitly out of scope.
And be honest about your own part. Agencies underperform for clients who never approve anything, change direction repeatedly, or brief by committee. If that pattern was present, changing agency alone will not fix it.
Frequently asked questions
How do I know if my web agency is doing a good job?
Ask what changed. Traffic, enquiries, conversion rate, page speed, whatever was agreed as the goal. An agency doing good work can answer with numbers. One that responds with activity reports listing hours spent is describing effort, not outcome.
What should I get when I leave an agency?
Domain registrar access, hosting access, full code and database, design source files, content and images with licences, analytics and Search Console access, and documentation of anything custom. Get it in writing before you give notice.
Can my agency hold my website hostage?
If they own the domain or the hosting account, effectively yes, at least for a while. This is why domain ownership is the first thing to check. If the domain is in your name you always have a route out, even if it means rebuilding.
Should I tell my agency I am leaving before getting my files?
Get your access and backups first, then give notice. This is not underhanded, it is prudent. Most agencies behave well, and the ones that do not are exactly the ones you cannot identify in advance.
Is it better to fix the relationship or switch?
Usually try fixing first, with one direct conversation about what is not working. Switching costs money, time and all the accumulated context. Switch when the conversation does not happen, or happens and nothing changes.