AI Vendor OversightYour vendor builds.
Your interests
stay visible.
Client-side technical review, milestone by milestone.
We review your vendor's proposal and architecture, test each milestone demo against agreed cases, and tell you what is evidenced before you sign off. We build AI systems ourselves, so we know where they fail.
Request vendor oversight
Our approach
A technical voice
on your side
of the table.
We sit in at four points of your vendor's project: the proposal, the architecture, each milestone demo and acceptance. At each one we put a written question to the vendor and check the answer against evidence, before you commit to the next stage.
Vendor's side · contract-review system · CT-0088
Technical proposal
01Proposal
Reviewed
We ask
Are the acceptance targets written into the contract, or left until after go-live?
Architecture document
02Architecture
Reviewed
We ask
Where are your contracts processed and stored, and does that meet the PDPL?
M2 demo · document understanding
03Milestone demo
In review
We ask
Does it hold on your own Arabic and English contracts, not only the demo set?
Acceptance file
04Acceptance
Next
We ask
What evidence supports sign-off, and who signs?
Your side · Rasikh Holding Group · Procurement & LegalIllustrative example
In practice
Evidence
at every
checkpoint.
The vendor says 90% accuracy. We ask for the test run, the log and the document, and mark what is missing.
Acceptance evidence
Milestone 2Document understanding · vendor build
2 of 4 evidenced
Illustrative example
Key deliverables
What you receive
after each milestone.
At each checkpoint you get a written review, the gaps and risks behind it, and a recommendation leadership can sign against.
- 01Documented checkpoint reviewsStructured assessment of the vendor's approach, design, and demonstrated capabilities.
- 02Requirement gaps and risksClear identification of issues, open questions, and potential impacts.
- 03Leadership recommendationsOne page per milestone: accept, accept with conditions, or hold, with the conditions and the risk behind it.
Milestone sign-off memoCT-0088 · M2
- For
- Group CFO · Head of Procurement & Legal
- Subject
- Milestone 2, document understanding: vendor demo and evidence
Our recommendation
- Accept
- Accept with conditions
- Hold
Conditions before M3 starts
- 1
Run the 50-contract test set and show accuracy of 90% or more. REQ-04
- 2
Document performance on the Arabic contracts in the set. REQ-02
RiskAccuracy is still a vendor claim. Signing M2 on the demo alone moves an unmeasured risk into production.
- Owner
- Head of Procurement & Legal
- Due
- Before the M3 kickoff
Independent reviewHow the engagement works
When to bring us in
Before you sign the vendor's proposal, or at the next milestone if the build has already started.
Who stays accountable
We review and advise. Your vendor stays accountable for delivery.
Testing in depth
Need the delivered system tested case by case? Add an AI Solution Evaluation.
AI Solution Evaluation
