Who maintains an automation after launch—and what affects support cost?

The business owns the process

Someone inside the business should know what the workflow does, where failures appear, which facts it uses, and who can pause it. The business should hold the primary accounts and data. An implementer may provide support, but should not be the only person able to access or explain the system.

Give external support staff individual, least-privilege access only for the time their work requires. Use business-owned administrator accounts, record access where the products allow it, and revoke consultant access promptly when the project or support period ends.

• Business owner: rules, approvals, priorities, and customer decisions
• Technical owner: integrations, failures, credentials, and releases
• Vendor owner: subscriptions, service incidents, and product changes

Support cost follows change and consequence

A workflow that drafts an internal note for review may tolerate a slower response. One that books service appointments, routes urgent calls, or affects payment needs faster detection and a tested fallback. More applications, custom rules, and third-party connections create more places where an update can require work.

Ask whether support is included for a defined period, purchased as a service, or handled only when requested. State normal working hours, response expectations, monitoring responsibility, and what qualifies as an emergency. Emergency availability should never be implied by a general promise to help.

Make maintenance visible before signing

Routine work may include reviewing exceptions, renewing credentials, responding to API changes, updating approved business information, checking notifications, and testing recovery. Documentation should identify the trigger, destinations, main rules, credential owner, alert location, fallback, and shutdown procedure.

The proposal should distinguish defect correction, ordinary maintenance, and new capability. At handoff, choose deliberately among internal operation, a defined support arrangement, or scheduled reviews. That keeps the relationship understandable and prevents every small change from becoming an open-ended dependency.