Nobody sat down and designed the website your organisation has today.
Somebody designed the website you had in 2016. What you have now is that site, plus everything that has happened to it since: the plugin a contractor installed before they moved on, the donation form nobody dares touch because it works and nobody remembers how, the second analytics tag that duplicates the first, the Google Ad Grant account running quietly in the background on settings last reviewed two funding cycles ago. Somewhere there is a spreadsheet of passwords. It is probably called passwords.
Researchers at NiCE have a name for this: the Frankenstack. A technology stack that is not so much run as kept alive. The term was coined for corporate systems, but I have rarely seen a better description of the average community legal centre website. And the scale of the problem is not a community sector quirk. According to research quoted in a recent MIT Technology Review Insights report, only about a third of companies have anything resembling a unified data core underneath their digital operations. Well-resourced businesses with IT departments cannot manage it. It would be strange to expect a five-person CLC to.
The anatomy of an accumulated website
If you manage a community organisation’s website, some version of this inventory will feel familiar.
There is the platform itself, usually WordPress, installed during a rebuild funded by a one-off grant. There are between fifteen and forty plugins, of which perhaps eight are essential, a handful are abandoned by their developers, and at least one exists solely because a previous staff member liked it. There is a theme that was customised directly, which means updating it risks breaking something, which means it has not been updated.
There is content: some current, some describing programmes that ended in 2021, some duplicated across pages because it was easier to copy than restructure. There are forms connected to inboxes that may or may not still be monitored. There is an SSL certificate that renews automatically until the day it does not.
And around the website sits the wider estate. The Google Business Profile claimed by someone who has left. The Ad Grant account that must spend correctly to stay compliant, and is doing so unsupervised. The analytics property that was migrated to GA4 in a hurry and never checked.
None of this is visible from the homepage. All of it is real.
Why it happens, and why it is not a failing
It is worth being clear about this, because the people managing these sites often carry a quiet embarrassment about them. The accumulation is not a failure of diligence. It is the predictable result of how the sector is funded.
Project grants fund builds. Almost nothing funds maintenance. So websites get rebuilt when the accumulated problems become unbearable, then begin accumulating again the day they launch. Staff turnover compounds it: each departure takes institutional knowledge about why things are configured the way they are, and each arrival adds a new layer of decisions made without that knowledge.
The result is a website that works, mostly, but that nobody fully understands. Which is fine, until it is not: until a plugin update breaks the intake form, or an accessibility complaint arrives, or the Ad Grant is suspended for a compliance issue nobody was watching for.
Why it matters more now
There is a reason to take the accumulation more seriously in 2026 than in 2019, and it is not the reason you will hear from most vendors.
Every new tool your organisation adopts, and especially anything AI-assisted, amplifies whatever foundations it sits on. Search engines increasingly summarise your content rather than merely listing it, which means muddled or contradictory content produces muddled or contradictory summaries. Automated tools draw on your structured data, your analytics, your published information, and they do so with complete confidence whether or not that information is coherent.
The MIT Technology Review Insights report makes this point about customer experience systems, but it translates directly: intelligence layered on top of drift produces confident errors. A fragmented foundation does not stay quietly fragmented anymore. It gets amplified, summarised, and repeated back to the very people trying to find your help.
For a high-trust organisation, that is not a technical inconvenience. A person in crisis who finds outdated service information, or a broken referral form, does not file a bug report. They give up, and you never hear about it.
The two honest options
When an accumulated website becomes unmanageable, there are only two honest paths, and it is worth naming both plainly.
The first is another rebuild. Sometimes this is genuinely the right call: if the platform is beyond saving, if the information architecture no longer matches what the organisation does, if accessibility problems are structural rather than surface-level. A rebuild done well solves real problems. But it is worth understanding what it does not solve. A rebuild restarts the accumulation clock. It does not stop it. Without a plan for what happens after launch, you are scheduling this same crisis for four or five years from now, to be dealt with by whoever holds your job then. If you are weighing this path, I have written a web redesign checklist for community organisations that covers what a rebuild decision should actually be based on.
The second is stewardship. This means accepting the site you have, understanding it fully, documenting it, and then maintaining it deliberately: not as an emergency response when something breaks, but as a quiet ongoing practice. Stewardship stops the accumulation rather than resetting it.
Most organisations need some blend of the two over time. But the sector’s default, rebuild and abandon, is the most expensive possible pattern, because it pays full price for foundations and then lets them erode.
What stewardship actually looks like
Stewardship sounds abstract, so here is what it means month to month, in plain terms.
It means updates are applied on a schedule, with a backup taken first and a check afterwards, so the intake form still works on Monday morning. It means someone is watching security, uptime, and the accessibility of new content as it is published, not auditing it in a panic when a complaint arrives. It means the Ad Grant account is reviewed against compliance requirements before Google reviews it for you. It means there is documentation: what is installed, why, who has access, and what to do if something fails. It means a short report in plain English that a coordinator can forward to a board without translation.
Documented, deliberate maintenance is also what makes the single greatest risk of the accumulated website, dependence on one person’s memory, finally go away. When the knowledge lives in documentation rather than in someone’s head, staff turnover stops being a digital risk.
That is the work of my Digital Stewardship Programme: ongoing accountability for an organisation’s digital presence, handled quietly and consistently.
The accumulation is normal. Leaving it unattended is the choice.
If your website is an accumulation, you are in the company of roughly two thirds of organisations with far more resources than yours. There is no shame in it. But there is a decision in it.
You can wait for the next breakage, the next complaint, or the next suspension notice to force the issue. Or you can understand what you actually have, document it, and start maintaining it on purpose.
If you are not sure where your own accumulation stands, a Digital Capacity Diagnosis is the structured way to find out. We also have a free guide for purpose-driven organisations considering a website refresh or rebuild. It covers trauma-informed design, accessibility, content strategy, and how to choose a digital partner who understands your mission, not just your brief. Ultimately, if you’re ready, we’d love to help build and maintain your new website in the safest way possible. So if you’ve made it this far, Let’s talk.
