The real cost of ignoring post-launch support
Most teams know this matters. Fewer have decided who owns it. Nobody bills you for neglecting post-launch support. The cost shows up somewhere else.
The projects that go badly are rarely the ones with the hardest technical problems. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Launch is the beginning of the maintenance period
- Rework, once the problem is finally visible
Decide who owns fixes before you need them. The reasoning matters more than the rule, because the rule has exceptions. Assume whoever inherits this will have half your context and none of your patience.
Turning this into a decision
Budget for it or it comes out of goodwill. It is worth being explicit about, because assumptions differ quietly. Assume whoever inherits this will have half your context and none of your patience.
In practice
Clear scope protects the client at least as much as it protects the agency. Three things worth confirming about post-launch support before you move on:
- Someone can say what the current setup is without going to look
- Launch is the beginning of the maintenance period — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Most of the value here comes from doing the first two things, not all of them.