The five fragments that show up during a bad week, and what replacing the model looks like.
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. The fragments are remarkably consistent from one business to the next. Here are the ones worth taking seriously.
1. Problems queue behind a ticket system
When the site goes down, you fill in a form. Somebody 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 works for a provider with hundreds of clients, and that is exactly the problem: at that size 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 four different suppliers, the gaps between them belong to nobody, and the gaps are where systems actually fail.
3. You are the integration layer
Somebody on your team copies data from one tool into another by hand, every week, because nothing connects. Orders get retyped. Reports get assembled in spreadsheets from three exports. If a person 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 needs 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 relationship where every increment costs a procurement cycle guarantees decay.
5. The people who built it are gone
The last fragment, and the most common one. The build was fine, but the builders moved on. The freelancer is on other projects, the agency team rotated, and the final payment marked the end of anyone caring what happened next. Your business now depends on a system nobody alive fully understands. That is not an insult to the builders. It is what project-shaped engagements produce by design, and who owns your systems after launch goes into it properly.
What changing 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 volume-support models applied to a business that needs continuous, accountable ownership.
The other shape is one engineer holding infrastructure, site, data and automations as a single connected system, on a monthly retainer, with nobody left to point at. There are two ways into it and neither of them is a rescue. Either the system is built here and then run here, or the system you already have is adopted as it stands and, from a fixed date, one person is answerable for it. The second is the usual one at this stage, because a business that has outgrown its vendor has generally already paid for something it intends to keep. What a month of that contains is set out in the retainer breakdown.
I do not take salvage work, meaning a system somebody else broke, handed over to be rescued. That is a different job with a different failure rate, and pretending otherwise would move the next bad week onto a different invoice rather than remove it.
If you counted three or more of the five in your own setup, the pattern is already costing you something. Working out what it is costing, and what changing it would involve, is the audit: €450, fixed before it starts and credited in full against a build or a retainer if one follows. The document is yours whether anything follows or not. Before that there is a free conversation of about twenty-five minutes, to establish whether this is a problem I can solve and which of the two routes applies. It does not diagnose anything, and if the honest answer is that your current vendor is fine, you will hear it there. The contact page sets out what the audit covers.