Pilot scoping
Tell Us Where the Model Falls Short.
Start with the target task, deployment environment, missing evidence, and the result that would make a pilot worth continuing.
How We Qualify the Brief
- 01
We review the model objective, task coverage, constraints, and evidence required.
- 02
We identify unanswered questions and define the smallest useful pilot.
- 03
If there is a viable fit, pilot scope separates acceptance criteria, assumptions, dependencies, rights, and release gates.
You do not need a finished specification.
If modality, scale, or format is still unknown, describe the model failure and the environment where it matters. Those unknowns become part of the scoping decision.
What a pilot proposal should define.
Scope, representative tasks, planned deliverables, acceptance evidence, rights, dependencies, timeline, and the scale decision. A proposal may include a capture protocol, sample tranche, QA results, rights summary, schema, or loader test; only written deliverables are commitments.
Copy a blank pilot brief Buyer tool
Use this structure with your model, data, legal, and procurement teams. Paste only a non-confidential summary into the inquiry form.
Briefs are sent to EGXO’s Slack inquiry channel. A short technical summary is enough; do not include datasets, passwords, API keys, or other secrets.