> For the complete documentation index, see [llms.txt](https://knowledge.magicworksitsolutions.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.magicworksitsolutions.com/knowledge/ai-consultation-and-readiness/vendor-evaluation.md).

# AI vendor evaluation

How to evaluate AI vendors without relying only on demonstrations or model claims.

AI vendor evaluation should test the product against the client's workflow, not against a polished demo.

Useful criteria include:

* fit to the target process,
* integration requirements,
* data handling and retention,
* security and access controls,
* evaluation methods,
* model and infrastructure dependencies,
* human-review options,
* portability and exit risk,
* operating cost,
* and the vendor's ability to support the implementation.

A proof of concept should use representative tasks and known edge cases. A vendor that performs well on a generic demo may still be a poor fit for the real process.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.magicworksitsolutions.com/knowledge/ai-consultation-and-readiness/vendor-evaluation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
