Post a brief
Describe the custom data supply your team needs and collect vendor offers.
New to briefs? Read What are briefs for the overview — lifecycle, how they differ from listings, and how offers become projects.
When to post a brief
Post a brief when off-the-shelf listings are not enough. You define the custom data work — scope, deadlines, visibility, and terms — and vendors respond with priced offers.
Briefs complement catalog purchases: many buyer orgs browse listings and samples for ready-made supply, then post briefs for bespoke collection, labeling, or domain-specific work.
The posting flow
- Draft — compose scope, deadlines, visibility, and terms privately within your buyer org
- Open — publish to vendors; set visibility to public (listed in Project briefs) or invite-only
- Review applicants — vendors apply with priced offers on the brief detail page
- Accept offers — each acceptance creates a project, tracked separately from the brief
One open brief can spawn multiple projects if you accept several applicants.
Buyer access
Buyer orgs need marketplace portal access through organization setup and HUD review. My project briefs at /briefs/mine shows your project briefs as the same card grid as explore, with lifecycle filters (Open · Drafts · Closed), status, applicants, and overdue.
Related pages
- What are briefs — shared overview
- Browse listings — off-the-shelf supply
- What buyers use this for — how briefs fit alongside catalog buying
Get started
Post a brief — create a buyer account and open the brief composer.