# AI Hardware Product Reference Brief

Use this brief to tell a supplier what should stay, what may change, and what is still unknown. Replace the prompts with your own information.

## 1. Project context

- Working product name:
- One-sentence target outcome:
- Target user and use environment:
- Target market or country:
- Current stage: idea / software demo / reference product / prototype / sample / existing quote
- Target sample date:
- Expected first quantity:
- Possible annual quantity, if known:

## 2. Reference product

- Reference link or model:
- Why this reference is useful:
- What must not be copied:

## 3. Keep

List the parts of the reference that should remain similar.

| Item | Requirement | Why it matters | How it will be checked |
|---|---|---|---|
| Product function |  |  |  |
| Physical size or form |  |  |  |
| User interaction |  |  |  |
| Connectivity |  |  |  |
| Other |  |  |  |

## 4. Change

| Item | Requested change | Required or preferred | Evidence or reference |
|---|---|---|---|
| Branding |  |  |  |
| Enclosure |  |  |  |
| Firmware or app |  |  |  |
| AI feature |  |  |  |
| Packaging |  |  |  |
| Other |  |  |  |

## 5. Unknown

| Open question | Who should clarify it | Deadline | Decision status |
|---|---|---|---|
|  |  |  |  |

## 6. First sample goal

- The first sample must prove:
- The first sample does not need to prove:
- Known test method:
- Pass or fail decision owner:

## 7. Commercial and compliance context

- Target price range, if known:
- Required certifications or target-market standards, if known:
- Files available now:
- Files the supplier is expected to provide:
- Sensitive information that must not be shared before an NDA or NNN agreement:

This template helps structure supplier discussion. It is not engineering, certification, legal, or commercial advice.