Signs It's Time to Replace Your Digital Agency
Most organizations wait too long to switch agencies. Here's how to tell when it's time, and what to do about it without getting stuck.
You’re three weeks into a six-week project and nobody at your agency has answered an email in four days. The account manager got reassigned last month and the new one hasn’t introduced themselves. The dev lead left the company and took context with her. Your project plan has three change orders attached to it now, each one more expensive than the last.
You know what you want to do. You just don’t know if you’re allowed to want it.
I get this call about once a month. Usually from a nonprofit or a municipal team. Sometimes from a growing company that outgrew their first web shop three years ago and hasn’t gotten around to dealing with it. The pattern is always the same. A long, slow erosion of trust that nobody wants to name out loud.
Here’s when it’s time to make a change, and what to do about it.
You can’t get a straight answer on scope or budget
Good agencies tell you when something is out of scope before they build it. Bad ones build it, then send a change order, then explain why it was always necessary.
If you’ve had three change orders on a project in six months, that’s not you changing your mind. That’s your agency scoping for comfort, not accuracy. That’s a pricing model showing up as scope churn.
A real partner gives you a straight answer. Sometimes the answer is “we can do that, it’ll cost more.” Sometimes the answer is “we won’t do that, and here’s why it’s a bad idea.” The change order should be rare. When it becomes the operating model, you’re being billed for their mistakes.
The people who know your project keep leaving
Agency turnover is normal. The people who sold you the project leaving six months in is a red flag. The developers who built your platform leaving and not being replaced is a different problem entirely.
Try this. Try to find someone at the agency who can describe the architecture decisions made on your project last year. If no one can, you don’t have an agency. You have a billing relationship with a company that used to have your people.
This is especially brutal in government and nonprofit work, where the systems are long-lived. A website you built in 2019 should still make sense to whoever is maintaining it in 2026. If the agency that built it can’t explain the code anymore, you’re paying a premium for amnesia.
Your roadmap is their sales funnel
Watch what happens when you ask for a roadmap.
A good agency asks about your organization’s goals, your users, your operational constraints, and builds a plan around those. A bad one pitches you a package. The difference is whether the recommendation starts with your needs or their capacity.
If every quarterly review ends with a proposal for something they already wanted to sell you, you’re the product. I’ve seen this play out with dozens of clients and it always looks the same. The agency has a new service line, suddenly that service line is exactly what your organization needs, and the case study will practically write itself.
You want a partner who tells you when you don’t need to buy anything.
The work is getting worse, not better
A long agency relationship should compound. Your platform should be more stable after three years of partnership, and your team should be filing fewer tickets than they did at launch, not more.
If the trend is going the other direction, something is wrong. Either the agency is assigning junior staff to your account because they’ve taken it for granted, or your platform has accumulated enough duct tape that every new feature breaks something old. Both are fixable, but not by continuing the same relationship.
Pull the numbers. How many open bugs do you have today versus a year ago? How many features have shipped in the last six months versus the six months before that? If the velocity is dropping and the bug count is climbing, you’re watching a slow-motion failure.
They can’t explain your own systems to you
This is the one I see most often and it makes me angry every time.
You call your agency about a change to your donor portal. You get a 40-minute meeting scheduled three days out. Someone you’ve never met joins the call and asks you to walk them through the system. They’re billing you by the hour to learn what they were supposed to have documented five years ago.
A healthy agency has institutional knowledge about your systems. They maintain documentation. They have a lead who can answer a question in under 24 hours. If every conversation starts from scratch, you’re paying for the same orientation over and over again.
What to do when you see the pattern
Don’t panic. Don’t fire them in a fit on a Friday. And don’t sign anything new with them while you’re figuring this out.
Here’s the sequence that works.
Get your stuff. Before anything else, make sure you own your code, your domains, your hosting accounts, your design files, and your content. If you don’t, fix that first. I’ve watched organizations get held hostage by agencies that control the DNS and stop returning emails. Don’t let that happen to you.
Document what you know. Write down the decisions you’ve made over the years, the vendors you work with, the integrations that exist, and the workflows your team depends on. You’ll need this for anyone who takes over.
Get a second opinion. Not a replacement agency with a pitch deck. A technology advisor who doesn’t have a dog in the fight. Someone who will tell you whether your platform is worth rebuilding or worth walking away from.
Plan the handoff. Good transitions take 60 to 90 days. Bad ones take six months and a lawyer. Agree on what gets transferred, who owns what, and when. Get it in writing.
Don’t replace like-for-like. The reason you’re in this situation is that you bought an agency the last time, and agencies are structured to keep selling. The next engagement might look different. It might be a fractional CTO plus a smaller build team. It might be bringing one role in-house and retaining a partner for strategy. It might be a nimble shop that actually hands you the keys when the work is done.
The quiet version of this problem
Most of the time, organizations don’t switch agencies when they should. They stay another year, and another, and another, because the alternative feels like too much work. The tech debt compounds, the team loses faith, and the original problems never get solved.
I’d rather have an honest conversation than a comfortable one. If you’ve been reading this and recognizing your situation, it’s probably time. The work of moving is real, but the cost of staying is bigger than it looks.
If you want a gut check, we’ll give you one. Book a free intro call and we’ll tell you whether switching is worth it. If it’s not, we’ll tell you that too.