No business decides one morning that it has outgrown its web vendor. The realisation arrives in fragments, usually during a bad week, and by the time it is undeniable the cost has already been paid in downtime, workarounds, and hours your team should never have spent. After twelve years of inheriting systems in exactly this state, I can tell you the fragments are remarkably consistent. Here are the ones worth taking seriously.
1. Problems queue behind a ticket system
When your site goes down, you fill in a form. Someone you have never spoken to triages it. The person who eventually responds asks questions that make clear they are meeting your setup for the first time. Ticket systems are how support scales for providers with hundreds of clients, and that is exactly the problem: at that scale, nobody knows your business, so every incident starts from zero.
2. Nobody can say whose job it is
The hosting company says it is a site problem. The developer says it is a hosting problem. The person who set up the integrations left the agency last year. When infrastructure, website, data, and automation are bought from different vendors, the gaps between them belong to no one, and the gaps are where systems actually fail.
3. You are the integration layer
Someone on your team copies data from one tool into another by hand, every week, because nothing connects. Orders get re-typed. Reports get assembled in spreadsheets from three exports. If a human is doing repetitive transfer work between systems, your team has become the middleware, and you are paying salaries for work software should be doing silently.
4. Everything is a quote
Small improvements never happen because each one requires a scoping call, a proposal, and an invoice large enough to justify the overhead. So the site drifts: outdated content, slowing pages, that form nobody fixed. A healthy system improves in small increments continuously; a vendor relationship where every increment costs a procurement cycle guarantees decay.
5. The people who built it are gone
The final fragment, and the most common one I see: the build was fine, but the builders moved on. The freelancer is on other projects; the agency team rotated; the final payment marked the end of anyone truly caring. Your business now depends on a system that nobody alive fully understands. That is not an insult to the builders. It is what project-shaped engagements produce by design, and I have written about who actually owns systems after launch in more detail.
What replacing the model looks like
Notice that none of the five signs is really about a bad vendor. They are about a wrong shape: project engagements and scale-support models applied to businesses that need continuous, accountable ownership. The alternative shape is fractional engineering: one senior engineer who runs your infrastructure, site, data, and automations as one connected system, on a monthly retainer, for less than the cost of hiring in-house. What that month contains is documented in the retainer breakdown.
If you counted three or more of the five signs in your own setup, the pattern is already costing you. A free 45-minute diagnostic call will tell you what is actually causing the friction and what fixing it would involve. No pitch, and if the honest answer is that your current vendor is fine, you will hear that too.