Whose job is it when something on your website breaks
What most owners assume, versus what was actually agreed
The contact form stops sending emails three months after launch, and both sides assume the other one is handling it. The owner figures the person who built the site is still responsible for it. The designer figures the project ended at handoff and this is a new, billable request.
Both people can be perfectly reasonable and still land on opposite assumptions. That's the actual problem, not that either side is acting in bad faith toward the other.
Neither assumption is wrong on its own. They're just two different defaults, and nothing in most conversations before the build ever settled which one applies once the site goes live.
The gap only becomes visible the first time something breaks. Before that, both sides can go months believing the same arrangement, without ever comparing notes.
By the time it does surface, there's usually some frustration mixed in. Nobody likes discovering, mid-crisis, that a shared assumption was never actually shared at all.
A short check-in a few weeks after launch heads this off. One email asking "who do I contact if something breaks" is enough to settle it before it ever becomes a dispute.
What's covered without a signed maintenance agreement
Without a written agreement covering post-launch support, the honest default is that nothing is automatically covered. A build contract typically ends at delivery. That's the whole scope, start to finish, unless something else was written down.
Anything after that — a bug fix, a broken plugin, a design tweak — is a new request. Whether it's free, discounted, or billed at full rate depends entirely on what the original contract actually said, if it said anything about this at all.
This isn't anyone playing a trick on you. It's just how project-based work tends to get structured unless someone specifically extends it in writing before the build even starts.
Most other project-based services work the same way. A contractor who renovates a kitchen doesn't automatically come back for free every time a cabinet hinge loosens a year later.
A quick fix offered out of goodwill once doesn't establish an ongoing arrangement, either. It's worth not assuming a first favor sets the pattern for every future request.
That's not a criticism of either side. A favor and a standing commitment look identical from the outside, right up until the second request arrives and one of you expects it to be free again.
The gap between building a site and keeping it running
Building a site and maintaining one are different jobs, even when the same person happens to do both. Building ends when the site goes live and the invoice gets paid in full.
Maintaining means someone keeps watching it after that — applying updates, catching breaks, fixing what stops working over time as software underneath it changes. A contract can cover one of these, both, or neither.
It's worth knowing which one you actually have before something breaks, not while you're staring at an error message trying to figure it out under pressure.
Some owners assume maintenance was included simply because the person who built the site also happens to be capable of fixing it. Capability and obligation are not the same thing, even when they live in the same person.
Getting this written down before you need the answer
The fix here is boring and effective. Before a project starts, get a plain sentence in writing about what happens after launch. Does support end at delivery? Is there a set number of free fixes in the early stretch after launch?
What counts as a bug versus a new feature request? That distinction alone prevents most of the arguments that happen later, once something has already gone wrong.
Vetting this question before you hire, rather than discovering the answer after something breaks, is the cheaper version of this conversation by a wide margin.
It's also a fair question to ask. Nobody should hesitate to raise it, and a designer who bristles at being asked is telling you something worth hearing before you sign anything.
What to do when it's genuinely unclear
If nothing was ever written down and something breaks now, the practical move is to ask directly, in writing: is this covered under our original agreement, or is it a new request?
Getting a clear answer, even an uncomfortable one, beats guessing and hoping it resolves itself on its own. A vague answer is itself an answer worth noting for next time.
Keep a copy of that reply, too. If this comes up again in a few months, you'll want the exact wording, not just your memory of the conversation.
Putting a maintenance plan in place is one way to make this explicit going forward instead of relitigating it every single time something breaks.
Telling a hosting problem apart from a builder problem
Not every break is a design or code issue. A site can go down because a hosting server has a problem, entirely separate from anything the builder did or didn't do.
Before assigning blame, check whether the site itself is broken or whether it's simply unreachable. Those point to different people, and conflating them wastes time arguing with the wrong party over the wrong thing.
A quick test settles this fast: if the site loads for other people on other devices but not for you, the problem is probably local, not the host or the builder at all.
Where the site is actually broken, versus simply unreachable, matters more than it might seem. One is a fix to the code. The other is a hosting issue that has nothing to do with anything the builder wrote.
How this sits next to hosting, backups, and updates in the full picture of upkeep covers where responsibility fits alongside everything else that keeps a site standing.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go