Who Fixes Your Website When It Breaks?

Most conversations about a website are about building it. Almost none are about the Tuesday two years later when the contact form stops sending and nobody notices for a month.

That gap is where most of the real cost of a small business website lives, and it never appears in the quote.

What actually breaks

Sites do not usually break dramatically. They break quietly, in a handful of predictable ways.

The form stops sending. An email provider changes an authentication rule, or a spam filter starts eating the notifications. The form still says "thank you." Nobody finds out until a customer asks why their message went unanswered.

The certificate expires. Browsers put a full-page warning in front of your site. This one is loud, at least.

A plugin update conflicts with another plugin. On platform sites, this is the common one. Something looks wrong on a page nobody visits often, so it stays wrong.

The domain or hosting renewal fails. An expired card on a service the owner set up years ago and forgot. This takes the whole site down, and recovering a lapsed domain is significantly harder than renewing one.

Nothing breaks, and that is the problem. Hours change, a service is dropped, prices move, staff leave. Two years pass. The site is now confidently wrong about the business, which costs more than being down.

The three situations businesses end up in

Someone built it and moved on. The most common one. A relative, a former employee, an agency that stopped answering. The site works until it does not, and then there is a scramble to find out who holds the domain, where the hosting is, and whether anyone has the login. That archaeology usually costs more than the fix.

A platform handles the updates. The subscription builders do keep the platform patched, which is real value. What they do not do is notice that your form is silently failing or that your hours have been wrong since May. And when you want something the platform does not do, the answer is no.

Nobody, and everybody knows it. The site sits there. It is out of date, mildly broken, and quietly costing calls. This is the situation most of the small business sites we look at are actually in.

The question to ask before you build

Ask the person quoting you what happens in year two, and listen for whether the answer has numbers in it.

Then ask these:

• Where do the domain and hosting live, and whose name is on them? They should be in your name. If a developer holds your domain, you do not own your business's address.
• How would I know if the contact form stopped working? If the answer is "you'd notice," that is not monitoring.
• Can another developer take this over? Ask to see the code, the credentials, and where it deploys. Portability is the only real protection you have.
• What does a small change cost, and how long does it take? Not the big rebuild. The Tuesday change: new hours, a new service, a staff photo.

The honest options

There are three, and none of them is free.

Do it yourself. Genuinely viable if the site is simple and you are willing to check it. Put a calendar reminder every quarter: submit the contact form and confirm the email arrives, check the certificate, read the site as a stranger would and fix what is now false.

Pay per incident. Call someone when something breaks. Cheapest until it is not, because the person you call has to reconstruct how everything works before they can help.

Pay a monthly retainer. Someone watches it, keeps backups, and handles the small changes. This is what our Covered plan is: technical maintenance, backups, and a change request each week. It is maintenance, not marketing, and we are careful not to sell it as anything else.

Which one is right depends entirely on what the site does for you. A brochure that never changes is fine on option one. A site that takes bookings or quotes is not.

If you already have a site and no idea what state it is in

That is a normal place to be, and it is worth finding out before something forces the issue. We look at existing sites and say what we would keep, what we would fix, and what it would cost, including sites we did not build.

If you are earlier than that and still deciding what to spend, we broke down what a small business website actually costs in Connecticut, and what to ask any developer before hiring them.