Software rots while you are not looking
A website is not a printed brochure. It sits on top of a stack that keeps moving underneath it — browsers, servers, plugins, payment providers, mail relays, certificate authorities. Doing nothing is not a neutral act. It is a decision to fall behind at the speed the rest of the internet moves.
The four things that break, in order of frequency
1. The contact form stops delivering. Almost always silently. The form still submits, the success message still shows, and nothing arrives. Usually a mail provider tightened its rules, a domain record expired, or the sending address lost its verification. Businesses routinely lose months of enquiries before noticing, because a broken form looks exactly like a quiet week.
2. The certificate expires. Modern certificates auto-renew — until the renewal is tied to a service nobody is paying for any more. Visitors then get a full-page browser warning telling them your site is unsafe.
3. Plugins drift apart. On plugin-based platforms, each component updates on its own schedule. Eventually two of them disagree, and the site either breaks visibly or, worse, breaks only on mobile, only on checkout, only for logged-in users.
4. Content goes stale. Not a technical failure, but it costs more than the others combined. Old prices, staff who left, a “2024” in the footer. Nothing signals a business is not paying attention quite like it.
Why the agency is gone by then
The economics are simple. Project work is paid on delivery, so the incentive is to finish and move to the next build. Maintenance is unglamorous, unpredictable and hard to price by the hour — so most agencies do not sell it, and the ones who do often sell it as a retainer you forget you are paying.
The result is a website with no owner. You do not have the skills, and the person who built it has no obligation.
What actually prevents it
Nothing exotic: someone checking. Certificates and domains monitored before they expire rather than after, the contact form tested on a schedule rather than by a customer complaining, dependencies updated deliberately, and a person to email who already knows how your site is built.
That is the whole idea behind our contract. We build it, then we stay on watch for 365 days — in writing, so it is an obligation rather than a promise.