You provide
A bounded, controlled document set inside your boundary; a workstation you control; the success criteria; and an engineer with the authority to adjudicate findings. No document leaves your estate.
The pilot
The pilot is not a demonstration — it is an evaluation you design. It runs on your hardware, behind your firewall, on a bounded document set you choose, and it ends with an evidence pack and a clear decision. No production commitment is required to run one.
A fixed-scope, paid engagement led by the Audit capability: Cortessa cross-references a bounded, controlled document set you select and hands your engineers cited, adjudicable findings. Everything happens inside your boundary — the software deploys onto a workstation you control, and nothing sensitive needs to leave it. Ask runs alongside on the same corpus, so your engineers can question the estate directly.
Success criteria are agreed before anything is deployed, so the pilot ends in evidence measured against your bar — not ours. A pilot converts to a licence only if the evidence earns it.
You choose a bounded, controlled corpus — the estate, or the slice of it, where a stale or conflicting figure costs you most.
What counts as a genuine finding, what precision is acceptable, what the pilot must demonstrate to be worth continuing. Agreed in writing before deployment.
A single executable on a dedicated workstation you control, behind your firewall. No server, no cloud, no internet dependency — disconnected operation is the default, not a concession.
Audit cross-references the corpus and surfaces conflicts, supersession, broken references and stale content as cited findings. Your engineers adjudicate each one; every disposition is recorded to the ledger.
Findings are checked against the sources by your engineers, not marked by us. The measurements are yours: recall and precision against your definition of a genuine finding.
The findings, the dispositions, the measurements against the agreed criteria, and the run artifacts — the material a decision, and an internal case, is made from.
A bounded, controlled document set inside your boundary; a workstation you control; the success criteria; and an engineer with the authority to adjudicate findings. No document leaves your estate.
The software as a single executable, deployment support, the audit run, and the evidence pack — findings, dispositions, measurements and artifacts, assembled for your internal decision.
Handling Pilots are structured so that evaluation happens inside your own boundary. Please do not send controlled, classified or export-controlled material when enquiring — the pilot design means nothing sensitive needs to leave your estate at any stage.
The pilot ends at a decision point, on the evidence. If the measurements clear the criteria you set, the conversation becomes a licensing one — per-seat or site, activated offline with no account and no phone-home. If they do not, you keep the evidence pack and the findings your engineers adjudicated, and the decision is equally clear. Either way, the pilot pays for itself in what it finds.
One email starts the scoping discussion: your estate, your criteria, your boundary.