FOUNDER-REVIEWED MANUAL PILOT · DIRECT-LINK EXPERIMENT
Which AI vendor claims can you actually verify?Before you trust it with important work.
A founder-reviewed manual pilot for a founder, CTO, operations lead, or small company deciding whether an AI vendor’s claims are supported by the evidence available to you.
One review scope · No account required · Fit confirmed before payment
Who this is for
A team considering giving an AI product access to code, data, hiring, customer information, operations, or a business process—without a dedicated procurement or AI governance team.
The trigger
You are about to trust an AI vendor and do not know which claims are evidence-backed, which are marketing language, and which questions still need an answer.
What Tyrone actually does
Read the vendor material and the specific claims you want evaluated. Map each claim to available evidence, scope, uncertainty, and the question to ask next.
What you receive
- · A claim-by-claim evidence review.
- · Supported, unsupported, ambiguous, and marketing-language distinctions.
- · Buyer questions and issues requiring independent assurance.
What this does not claim
- · It does not certify the vendor or guarantee security.
- · It is not a penetration test, legal advice, or regulatory-compliance guarantee.
- · It does not guarantee that you should buy the vendor.
The manual review
A bounded evidence review for one decision in front of you.
Tyrone reviews the material and scope you provide, then keeps support, uncertainty, and missing evidence visible.
01
Name the scope
Start with one vendor claim or one live agent workflow—not a promise to assess everything.
02
Map what exists
Separate claims, sources, permissions, approvals, logs, and context from interpretation.
03
Make the next question clear
Receive a concise evidence map, open gaps, and questions that belong with the vendor or your own team.
See the shape of the output before you ask for a review.
Claim: “Customer data is never used for model training.”
Available source
Fictional vendor privacy statement supplied for this example; its training-use scope is not defined.
Evidence status
UNCLEAR — the statement does not establish which customer data, products, regions, or retention paths are covered.
Question to ask the vendor
Which data types are excluded from training, under which product terms, and how are exceptions documented?
Stronger evidence
A precise contractual term with defined data scope, retention, exceptions, and an assurance artifact that covers the relevant service.
Illustrative, fictional, not customer data, and not a real vendor engagement.
Ask for a fit review
Have one vendor claim you want to test?
Send the smallest useful context. Do not send secrets, credentials, private keys, access tokens, or unnecessary customer data. Tyrone will confirm scope and fit before any payment.
Manual discovery only
This page tests whether the problem is worth building software for. It is not an automated control plane, certification, legal advice, or guarantee.