# AI development request for proposal — buyer brief

Version: [fill in]
Buyer owner: [fill in]
Decision date: [fill in]
Authorized initial commitment: [fill in]

## 1. Task and boundary
- User and current workflow:
- Incoming work and expected output:
- Receiving system:
- Permitted actions:
- Excluded actions:
- Simpler baseline to compare:

## 2. Buyer inputs and dependencies
- Approved data, source owners, access purposes and environments:
- Reviewer role, availability and acceptance authority:
- Integration access and system owners:
- Missing dependencies, consequences and next actions:

## 3. Supplier response
- Proposed engagement and finite deliverables:
- Named role coverage and availability:
- Architecture rationale and alternatives:
- Data flow, permissions, subprocessors and retention:
- Evaluation cases, rubric, held-out check and known limits:
- Integration failure and recovery behavior:

## 4. Commercial comparison
Separate discovery, data preparation, build, integration, evaluation and deployment.
List recurring runtime, human review, support and buyer labor assumptions.
State currency, taxes, workload, exclusions, change control and spending authority.
Do not treat an unpriced dependency as included work.

## 5. Handoff and operation
- Source, configuration, evaluation and documentation inventory:
- Background IP and third-party restrictions for legal review:
- Receiving-team transfer exercise:
- Support coverage, escalation, containment and exclusions:
- Exit, asset transfer, data disposition and access removal:

## 6. Evidence and next decision
Use Verified / Open / Reject with artifact version, reviewer, date and next action.
State the conditions for stop, further investigation or a defined implementation.
This template does not approve production access, spending or a legal agreement.
