The default reflex for agency builds is still to install a monolithic CMS, twenty plugins, and a complex admin dashboard for an organisation that updates three pages twice a year.
Six months after launch, security updates pile up, database queries drag down page load speeds, and the client pays a monthly retainer just to keep the server patched.
The CMS default
Most SME websites are brochures with contact forms. They do not have daily newsrooms or active community forums. Treating them as complex database applications introduces maintenance liability with almost zero commercial upside.
The fastest, most secure website is the one that has nothing to compute when a visitor asks for a page.
When static is honest
Static builds deliver instant page loads, zero database vulnerabilities, and trivial hosting requirements. But honesty requires acknowledging who will maintain it. If marketing needs to publish without technical friction, Git-backed content models or lightweight decapped interfaces keep the build lean without locking out non-technical editors.
Handover without fragility
The real test of a static architecture arrives six months after the developer leaves. If updating an office address or publishing a case study requires opening a terminal, checking out a Git branch, and running a local build, the architecture has failed the client.
A sustainable static handover separates content from code without reintroducing a database. Markdown files in Git paired with a decoupled editing interface give marketing teams a familiar authoring workflow, triggering an automated edge build whenever changes are committed.
For sites where updates happen only a few times a year, an even simpler pattern works best: structured Markdown files stored directly in a repository, with a two-page runbook documenting how to make text edits directly in the web interface.
The client gains complete ownership: their site can sit on a global edge network for years without degraded performance, expired plugins, or unexpected maintenance invoices.
