Three notes we are willing to put our name on. They are not survey results and they do not cite a private client.
Write down which documents the assistant may read, how long prompts are kept, and who can turn the system off. A pilot that skips this becomes a production incident later. If you cannot name the boundary, you do not have an implementation yet. You have a demo.
The useful question after a workshop is who gets paged when the workflow is wrong on a Tuesday. If the answer is the vendor, the pilot is not finished. Give the workflow a service name, a log, a limit, and a person.
Hiring a DevOps engineer into a system with no pipeline, or building a pipeline with no one to run it, both stall. Decide whether the constraint is people, the platform, or the outcome. Then buy that.
