I have heard some version of this sentence probably forty times: “We knew something was off, but we kept giving them the benefit of the doubt.”
That sentence always comes from a founder, always in the past tense, and always with the same slightly exhausted energy of someone who waited three months longer than they should have.
Here is what I have noticed about failing agency relationships: the signals are consistent. They show up in almost every broken engagement I have ever seen. The problem is not that founders miss them — they notice. The problem is that they talk themselves out of acting on them.
So here are the five signs, plainly stated.
You are sending “any update?” messages
If you are the one initiating status updates more than twice a week, stop. That is a signal, not a workstyle difference. A functional agency has a cadence. You should receive a standup before you have to ask for one. If that is not happening, it means there is no process — or the process is producing output they are not confident showing you yet. Either way, you have a problem.
Demos keep getting pushed “just one more week”
This one I take seriously immediately. Weekly demos exist for one reason: to catch the gap between what was asked for and what is being built before that gap becomes expensive. An agency pushing demos is an agency that does not want you to see something. It might be quality. It might be that very little was actually built. But they are not pushing because the demo is going to be amazing and they want more time to polish it.
You cannot answer basic budget questions without emailing them
At any point in an engagement, you should be able to say: here is what was delivered this sprint, here is how many hours were used, here is what is left. If you need to send an email and wait a day to get those numbers, your agency is running a black box. You are paying for visibility you are not getting.
Scope changes happen silently
Every project has scope changes. That is fine and normal. What is not fine is finding out about them on the invoice. A good agency flags every change immediately, gives you a rough estimate, and gets your written confirmation before proceeding. A bad agency absorbs changes quietly, builds whatever they interpreted, and invoices accordingly. The second model is how you end up with a product that is technically “done” but not what you wanted.
You feel anxious when an invoice arrives
Your stomach should not tighten when you see an email from your agency. If it does — if you are opening invoices wondering what the number is going to be this time — the relationship is already broken. That anxiety is information. The budget should never be a surprise.
How to actually switch without losing three months
The fear that makes founders stay too long is usually this: “If we switch now, we lose momentum and have to start over.” In most cases, that fear is overblown.
Before you give notice, get everything. Every credential, every repository access, every piece of documentation. Do this quietly and first. Once you have that in hand, the leverage shifts.
Then do a one-week technical review with the new agency before you commit. Ask them to assess the codebase, document what they find, and tell you honestly what they are inheriting. A good agency will not sugarcoat this. You want their honest read, not reassurance.
If you can afford it, run a one-sprint overlap. Pay the old agency for maintenance-only work while the new one ramps up. It costs extra. It saves you far more in risk.
The clients I see switch fastest are the ones who stop treating the decision as a reflection of their judgment and start treating it as just a business problem to solve. You made a choice. It did not work out. Now you make a different choice. That is it.