Support after launch: why "handed over and forgotten" breaks a site

A release feels like the finish because the invoice is closed and the page opens. Ordinary life starts after that: marketing asks for a block, a form fails on one phone, a plugin closes a vulnerability. Without maintenance this piles up until it becomes an outage. "Handed over and forgotten" is not a saving. It moves the payment to the worst day.

What is worth naming in the agreement

• Reply time on business hours, and separately what counts as an urgent incident at night.
• What the pack includes: updates, small fixes, a watch on copies. A new feature does not hide in there.
• A link to backups and monitoring. Support without copies repairs something there is nothing left to restore.
• Who accepts tasks. A chat of ten people with no owner is not a channel.

Someone else's product can be taken on too, but after a short look: what it is built on, whether access exists, whether a copy restores. Otherwise maintenance becomes archaeology. We leave our own projects on support immediately, so updates do not wait for the next contract.

If a site hangs with no owner, Lexora gives it a process back: a task queue, a clear reply and a boundary between a fix and new development.