Skip to main content

Menu

What a brief is

How buyers describe custom data work and suppliers respond with a proposal.

What a brief is

A brief is a request for data work. The buyer describes the problem, the material they need, and how they will judge the result. A supplier can then respond with a scope, price, and delivery date.

A team might already know how many records it needs. It might instead have a single evaluation task and need help deciding which examples to collect. Both are useful starting points.

Brief lifecycle

A brief usually moves through three stages:

  • Draft — describe the project, delivery requirements, and open questions.
  • Open — share the requirements with potential suppliers and compare proposals.
  • Closed — stop accepting proposals and confirm the next steps with the selected supplier.

Tell sapien1 who may receive the brief. Include only information you have permission to share.

Briefs vs listings

ListingBrief
Who defines the workThe supplier describes existing material.The buyer describes a need.
What to compareScope, provenance, rights, and delivery.Approach, timing, price, and acceptance criteria.
Next stepAsk for a representative sample.Request a proposal.

Next steps by role

Buyers can send a brief to sapien1 by email. Suppliers responding to a specific brief should include its title, what they can deliver, and where they need more information.

Related pages

  • What buyers use this for — How AI teams source training data, evaluation tasks, and custom data work through listings, samples, and briefs.
  • Compare a data listing — Learn what to compare in a data listing and ask sapien1 about sourcing options for your project.
Language: English