Submit a data proposal
Declare supply your org could deliver if buyer demand appears — without building a full marketplace listing first.
What a data proposal is
A data proposal signals inventory and capacity your organization could supply on short notice. It is lighter than a formal listing: you describe what you have or could produce, estimate rough capacity, and optionally attach a sample — without pricing, full asset packaging, or catalog review.
HUD uses proposals for buyer matching and supply analytics. High-value proposals may trigger internal outreach, but HUD does not promise review or feedback on every submission.
How it differs from a listing
| Data proposal | Listing | |
|---|---|---|
| Visibility | My listings → Proposals only | Public Browse listings catalog |
| Effort | Describe, capacity, optional sample | Full assets, pricing, review |
| Outcome | Matching signal | Direct purchase or sample |
You can publish a listing self-serve anytime — often pre-filled from an existing proposal if demand materializes.
The proposal flow
Submit through Add supply → Data proposal:
- Describe — title, data proposal asset type (broader than listing kinds: codebase, RL environment, taskset, raw dataset, audio, video, traces, enterprise documents), and a single description covering what it is, why it is valuable, and who would buy it
- Capacity — rough quantity deliverable within 2 weeks and within 6 months
- Sample — optional file upload (strongly encouraged; repo URL acceptable for codebases)
- Submit — appears in Proposals; no under-review queue or verdict in the product
Who should submit
Vendors exploring demand before investing in listing quality, or teams with latent inventory that could be packaged if a buyer appears. Distinct from asset estimation, which values supply you already hold.
Get started
Submit a data proposal — onboard as a vendor and open the proposal flow.