For engagements on site, read-only access on Your own infrastructure; the Estimate Read works from documents. The contract and its schedules, including the annexes nobody prints. The supplier's raw test evidence, not its test report. Time with engineers on both sides, without Their managers in the room. One executive sponsor who can unlock access when someone declines to give it.
How the work runs
Five things a buyer usually has to ask for. They are here instead.
What I need from You
What I take away
Nothing. No copies of data leave Your environment. You see the final text before it is issued and decide what confidential material it may quote. The conclusion is mine.
Where AI is used
I use AI to review documents at volume and help build tools for comparing evidence. Raw data and telemetry stay in Your environment; I use only models Your organization has approved for that data.
I check the underlying evidence, speak to the people involved and sign the conclusion. The engagement letter states where AI is used and can set out the sub-processor position for Your security team.
What the report looks like
The conclusion comes first, followed by the supporting evidence, what could not be established and why. Where the conclusion is “not yet”, the report names the conditions that would change it.
It is written for the decision in scope: a payment, change request, notice or board paper. You also receive the evidence ledger.
How a conclusion can be checked
You receive the evidence ledger so the conclusion can be retraced. Any follow-up support is agreed in the engagement terms.
Describe the decision and deadline.
Tell me what You need to decide, when You need to decide it and what is at stake. I’ll reply within two working days with whether I can help and what it would cost, or what I need to clarify before quoting.
A short summary is enough to start. Confidentiality terms are agreed in writing first, and we then agree how Your project documents will be made available.