Evaluation / Scope first
Have a workflow worth investigating?
Start with one workflow and one specific verification question. Discuss whether Outcome Check is suitable for the available records, define supported checks and acceptance criteria, and agree on an appropriate evaluation scope.
NO PUBLIC PRICE · NO AUTOMATIC APPROVAL · DO NOT EMAIL SENSITIVE PRODUCTION RECORDS
01 / Proposed scope
One workflow. A defined verification question.
In scope, subject to agreement
- One workflow and one verification question.
- Synthetic or explicitly authorized, appropriately sanitized input records.
- Agreed supported checks and acceptance criteria.
- Findings and evidence outputs supported by the implementation.
- Interpretation memo and a defined retest, if agreed in scope.
Not included by default
- Production access, credentials or live writes.
- Direct database/API integration.
- Monitoring, alerting or automatic remediation.
- Security certification or guaranteed detection.
- Unlimited iterations or custom connector development.
This is a proposed evaluation scope, not a claim that an evaluation is already booked or commercially validated. Scope, deliverables, price, data handling and acceptance criteria must be agreed before work begins.
03 / Data handling
Agree the boundary before sharing data.
Start with synthetic examples or a description of the data schema. Do not send API keys, passwords, payment-card data, access tokens or unrestricted production exports. Any use of confidential or personal data requires an agreed transfer, access, retention and deletion process and appropriate review before processing.
The public website is static. The request link opens an email draft; it does not upload files, create an account or automatically grant diagnostic access.