The product still needs an owner after launch.

What post-launch support covers

The basics: keep the product current, fix what breaks, and watch that it is still up. Beyond that, the scope is written per engagement — not a public “up to N hours” placeholder.

Fixes. When something in scope breaks, it gets fixed without a new sales cycle for every small issue.

Updates. Dependencies and security patches on a cadence, not after an incident.

Monitoring. Uptime and error visibility so problems are not discovered by a customer screenshot.

Improvements. Small feature and content work can be included when it is scoped. Extra work in a given month is agreed, not assumed.

Taking over systems we did not build

Inherited products start with a review. We need to understand the codebase before promising support. Sometimes issues have to be addressed before a retainer makes sense. We will say so in plain language.

Terms

Retainers are typically monthly. A three-month minimum is the usual starting point so there is enough runway to actually know the product. After that, month-to-month with notice. Exact commercial terms are written per engagement.