Look for workflow evidence

Useful signals include repetitive manual transfer, document triage, inconsistent reporting or a backlog that has a clear decision rule. Ask whether automation is necessary or whether a simpler process change would solve the issue.

A buyer may ask for an autonomous agent when the task needs deterministic rules and approvals. Diagnose the workflow before selecting a technology.

A feasibility matrix

DimensionQuestion
InputsAre the required data and formats available?
ExceptionsWhat happens when an input is missing or ambiguous?
ConsequencesWhich mistakes would be costly?
ReviewWhere is human approval needed?
IntegrationWhich systems and access are involved?
EvaluationWhat baseline and acceptance criteria will be used?

Do not infer implementation feasibility from the popularity of a technology label.

Propose a bounded pilot

Hypothetical request: a team wants to automate incoming document sorting. A useful first step maps document types, exceptions and the review process. A pilot can compare outputs against agreed examples before broader deployment.

Do not promise labor savings without measuring the current process and the review work the system adds. Describe assumptions and failure handling.

Qualification and exclusions

Reject projects that lack necessary access, ownership or a safe review path. Clarify privacy and security requirements within the actual delivery process rather than collecting sensitive data in a public thread.

Track viable pilot scopes and why inquiries fail feasibility. Those outcomes help refine your offer toward problems you can actually solve.