Give the assistant a bounded job

"Help us sell more" is too broad a brief for a dependable automated workflow. It contains research, judgment, communication and commercial commitments, each with different consequences when something goes wrong.

Choose a bounded job with clear inputs and an inspectable output. Preparing a draft account brief from approved public sources is easier to evaluate than autonomously managing a relationship. A draft can be checked before it affects the buyer.

Define what the system may not assume. Missing budget information should remain missing. An inferred priority should not become a confirmed need. A suggested follow-up should not become a sent message without the intended approval process.

Set escalation conditions. Uncertain identity, conflicting sources, unusual commercial terms or a request involving sensitive information should route to a responsible person. The workflow needs a useful way to stop rather than a bias toward completing every task at any cost.

Keep a record of inputs, outputs and corrections sufficient to understand errors. Without that record, the team may repeatedly fix symptoms without learning where the workflow fails.

Expand only after the bounded job performs acceptably under ordinary and difficult cases. Reliability in a demonstration does not establish reliability across the messy work of a real pipeline. The purpose of a narrow scope is to make quality visible enough to improve.