A map of jobs, systems and control
We read dated supplier documentation and identify the product, edition and limits each statement covers. We separate those statements from our analysis and buying questions. We label information supplied directly by a company. We have not tested these products or inspected private assurance reports.
This order favors assisted delivery of work across systems. It is an editorial preference, not a score for every AI purchase. A tool that cannot meet your required task should leave the shortlist.
Evidence types
- Public documents
- Material that readers can open is cited with the date it was checked.
- Company statements
- Information supplied by a company is attributed and is not treated as public verification.
- Recorded observations
- Observations are included only when a dated record shows what was checked.
What this method does not cover
- Consumer chatbots and a complete directory of every AI supplier.
- Hands-on product benchmarks, verified customer returns or a legal assessment of a deployment.
What we look at
The job it does
Does the product answer, find, analyze or act?
Evidence requested: Show one request, the information it needs and the finished result. Mark each step the product owns.
Finding the right source
Can it find the records this job needs without exposing restricted material?
Evidence requested: Use a current document, an outdated copy and a restricted record. Check the source links and access rules.
Changing a record
Which systems can it change, and when does it need permission?
Evidence requested: Name each read and write operation, the connected account and the approval step. Ask to see a refused action.
Accounts and access
Do employee and agent permissions stay clear across products?
Evidence requested: Trace the user, agent and connection through one task. Remove access and check what happens next.
Who runs it
Who builds, maintains and pays for the service after the first demo?
Evidence requested: Get named customer and supplier responsibilities, a launch plan, support terms and a quote for the intended use.
Revision log
Added comparisons by task, source access, actions, identity and delivery, plus guides to mapping AI tools, resolving overlapping purchases and assigning workflow ownership.
Editorial scope, Comparison criteria, Recommendations, Provider reviews, Buying guides, Sources and correctionsAdded a planning diagram that follows a request from the employee’s conversation to the business record and the person responsible.
Page designCorrections
Send the page address, the disputed statement and supporting evidence through the contact route. Corrections should identify the changed statement and the date. A supplier’s preference alone does not justify removing a sourced limitation.
Please include: Publication name, Page URL, Statement to review, Supporting source, Date checked.
Request a correctioncontact@gpt.nexus