## Company enrichment pilot worksheet

This proposed worksheet helps scope a pilot. It is not a contract and contains no filled results.

### Scoping questions

- What is the supplied domain list, and how many domains are in scope?
- Which geographies and company types should be included or excluded?
- Which fields are required beyond `input_domain`, `company_name`, `source_url`, `observed_at` and `field_status`?
- What source types are permitted, and must each field retain a public URL?
- What refresh interval and observation-time format do you need?
- What output format should be reviewed: JSON, CSV or another agreed format?
- What expected volume and delivery boundary should be assessed?
- Which parent, subsidiary or trading-name relationships require manual review?
- What rules allow an accepted row to be considered for CRM overwrite?

### Acceptance worksheet

- [ ] Every output row maps to one supplied domain
- [ ] Every non-null record has a supporting source URL
- [ ] Every observed value has an observation time
- [ ] Ambiguous organization relationships enter a review queue
- [ ] Unobserved values remain null
- [ ] Only rows marked `accepted` may be proposed for CRM review
- [ ] Output format and field names match the agreed scope
- [ ] Exceptions and unknown records are listed separately

### Pilot output to agree

Proposed output: an enrichment file with the agreed fields, record-level source URLs and observation times, plus a review queue. ProxyLane must confirm feasibility, scope, price and these acceptance rules before any work or purchase terms are agreed.