Maintenance and Support

Start with the Consequence

A founder is clarifying who controls the product and how the company will respond when something goes wrong.

The immediate question is maintenance and support. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.

Turn the Term into Evidence

Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.

For this decision, the useful standard is that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.

• Make the decision explicit: Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.
• Ask what evidence would show that the chosen approach works.
• Name the person or provider responsible when the approach fails.
• Record the result in the security, ownership, and handover record.

Match the Control to the Consequence

Define included work, response targets, update cadence, monitoring, escalation, ownership, and exit before launch.

The principal risk is that every issue after launch becomes an unpriced emergency with no accountable responder. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.

1. Describe the user or business outcome that must be protected.
2. Identify the most credible failure and its consequence.
3. Compare the simplest adequate approach with one realistic alternative.
4. Set a review point for when the decision may need to change.

Evidence Compared with Assumption

Warning Signs

• Nobody can explain how maintenance and support changes a user or business outcome.
• The proposal does not address this risk: every issue after launch becomes an unpriced emergency with no accountable responder.
• The only evidence is a successful demonstration of the easiest path.
• The decision has no named owner, boundary, or review point.
• A provider-specific feature is being mistaken for a permanent product requirement.

Questions to Ask a Consultant

• What decision are we making about maintenance and support?
• Which user or business outcome does the recommendation protect?
• How have we reduced or accepted this risk: every issue after launch becomes an unpriced emergency with no accountable responder.
• What evidence can I review without relying on the original implementer?
• What is deliberately deferred, and when will it be reconsidered?
• Who owns the accounts, data, documentation, and recovery process?