The best arrangement depends on who wants to operate the workflow after it is configured.

## Compare the responsibilities

| Arrangement | Typical scope to discuss | Decision to make |
| --- | --- | --- |
| Guided configuration | Help selecting tools and working through setup. | Which tasks will you complete yourself? |
| Setup and handoff | Configure the agreed workflow, test it and document operation. | Who owns accounts, credentials and maintenance afterward? |
| Setup and management | Configure the workflow and provide a defined ongoing service. | What is monitored, maintained and included in the service? |
| Standalone tool usage | Use a particular available tool under its published terms. | What are the actual limits, units and access requirements? |

These are scoping options, not a published rate card or a promise that every tool is currently available.

## Put ownership in the plan

List the owner of each provider account, the people who can access the workflow, where data lives, and how the service can be handed over or ended.

## Define “done”

A handoff should include a usable operating path, an example of successful work, a demonstrated failure or retry path, and instructions for recovering the relevant data.

For management, agree on routine responsibilities and how change requests are handled. Avoid assuming that “managed” includes every possible future feature.

Use the [estimate guide](/hc/productpat/articles/productpat-en-estimates-and-value) to separate setup, recurring work and provider usage.
