# Edxperimental Labs Benchmark Intake Template

Use this before a diagnostic or benchmark sprint. A strong intake keeps the first call focused on evidence instead of generic AI discussion.

## Workflow

Describe one workflow, the owner, user journey, current process, monthly volume, and what a wrong answer costs.

- Notes:
- Files / links:
- Open questions:

## Evidence

Attach representative documents, tickets, prompts, screenshots, policies, expected outputs, and known failure examples.

- Notes:
- Files / links:
- Open questions:

## Constraints

List latency target, budget boundary, data sensitivity, approved vendors, deployment environment, and compliance requirements.

- Notes:
- Files / links:
- Open questions:

## Decision

State the decision this benchmark must unlock: buy, build, switch, ship, pause, redesign, or run a deeper pilot.

- Notes:
- Files / links:
- Open questions:

## Candidates

List model/provider/agent routes to compare and the baseline process they must beat.

- Notes:
- Files / links:
- Open questions:

## Acceptance

Write the minimum evidence required before the team would trust the workflow in production.

- Notes:
- Files / links:
- Open questions:


## Contacts

- Sanjay Prasad (Benchmark design and technical delivery): sanjay@edxperimentallabs.com
- Saujas (Sales engineering and client solutions): saujas@edxperimentallabs.com