Nobody knows how our website works anymore.

There is a moment when this particular problem stops being abstract. Someone asks a perfectly reasonable question, why does the price feed update overnight, where do the enquiry emails actually go, what is that scheduled job for, and the room goes quiet. Not because the answer is complicated, but because the person who knew it left in 2021, and it turns out the answer lived in their head the whole time.

The website still works. That is the strange part. It runs like a clock built by someone who has since emigrated: ticking away, keeping decent time, entirely opaque. Your team has evolved a practical wisdom around it that would be funny if it were not so precarious. Do not touch the settings on that form. Nobody is sure what that plugin does, but the last person who disabled something broke the newsletter for a week. There is a password in a spreadsheet called passwords final v3, and half the credentials in it belong to people who no longer work for you.

So a quiet paralysis sets in. Small improvements do not get made, because nobody can predict what a small change touches. Bigger projects get deferred, because every scoping conversation runs into the same fog. New suppliers come, look, and either walk away or quote defensively high numbers for anything involving the parts nobody understands, and you cannot even tell whether those quotes are fair. The website has become something your organisation works around rather than with: load-bearing, unknowable, and slightly resented.

Underneath sits the risk you try not to dwell on. Institutional memory does not fail gradually; it fails all at once, on the day something breaks in the part nobody understands. And there is a subtler cost you may already have noticed: not knowing your own website makes every decision about it a decision made blind, from renewals you cannot evaluate to security questions you cannot answer. If this is where you are, be assured of two things. This state is extremely common; knowledge leaks out of every organisation, and websites, which are maintained occasionally rather than daily, leak fastest. And it is entirely reversible, because the knowledge was never magic. It is written in the system itself, waiting to be read by someone fluent in it.

How we rebuild the knowledge

A website's code, database and configuration are a complete description of how it works; what your organisation lost is the ability to read them. That is a skills gap, not a permanent condition. Our audit service is the reading exercise: we go through the site as built, not as remembered, and produce the missing map in plain English. What exists, what talks to what, where the enquiries really go, what that scheduled job does, which of the mystery components matter and which are dead weight from projects past. Alongside it goes the practical housekeeping that fog always hides: credentials inventoried and secured, the spreadsheet retired, lapsed updates identified, and anything genuinely risky flagged with its actual severity rather than a guess. We have been reading other people's Umbraco builds since 2011, across more than 200 sites; the code that intimidates a generalist is usually a Tuesday for a specialist, a point our FAQ makes about taking over sites other agencies built.

Reading the map back is only half the fix. The other half is making sure the knowledge cannot evaporate again, and that is a structural choice, not a document. Documentation alone decays the day it is written; knowledge stays alive when the people who hold it stay involved. That is what a support retainer actually provides beneath the service levels: the same small team touching your site month after month, from £500 a month, accumulating exactly the familiarity your organisation lost. With us that team is deliberately small and senior, an Umbraco MVP and an Umbraco Certified Master among three named people, so the knowledge concentrates instead of diffusing through a rotating cast; our FAQ on who will actually work on your website names them. The paralysis lifts faster than clients expect: changes stop being frightening once someone can predict their consequences, and the backlog of small improvements everyone was afraid to touch finally starts to move.

You do not need to assemble anything before starting; the whole point is that we start from what exists. Get in touch and tell us the honest version, including the passwords spreadsheet. It will not be the worst one we have seen, and mapping the unknown is considerably cheaper than continuing to steer around it.