Fiund / Project pricing
Pricing follows the specification.
A useful quote for photo datasets separates source fit, preparation work, permission review, and acceptance. Start with a brief so the scope can be discussed.
Project shapes
Choose the conversation your project needs.
For teams exploring what could fit.
Source review
Describe the use case and acceptable source characteristics. Discuss feasibility and the evidence needed to assess a proposed collection. A sourcing inquiry does not reserve inventory or commit either party to a transaction.
Scope a projectFor a bounded collection and acceptance brief.
Defined dataset project
Specify categories, volume units, formats, annotations, and review criteria. Separate source access from preparation work and identify assumptions that change the quote. Review scope and commercial terms before treating the project as agreed.
Scope a projectFor requirements that need a tailored sourcing plan.
Collection or ongoing scope
Discuss whether new capture or continuing sourcing is appropriate for the task. Define milestones, permissions, review stages, and change handling in the proposal. Feasibility and timing depend on the actual collection requirements.
Scope a projectQuote factors
The details that change the work.
Coverage plan
Class list, counts per class, environments, geographic scope, and real versus synthetic requirements.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Image properties
Dimensions, orientation, file format, compression tolerance, and whether originals are required.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Annotation rules
Label taxonomy, box or mask conventions, ambiguous cases, and quality-review criteria.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Source relationships
Burst sequences, near duplicates, photographer groups, and separation of evaluation examples.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Before agreeing a scope
Make the proposal reviewable.
Coverage and units
Define the count being priced, accepted output versus source volume, and any category-level minimums. Identify exclusions and limits of the proposed source.
Preparation and review
List file preparation, annotation, quality review, and correction work. Agree what evidence demonstrates acceptance and how exceptions will be handled.
Use and delivery
Document intended uses, restrictions, delivery format, review milestones, and commercial terms. Confirm each in the project agreement rather than inferring them from a website category.
Common questions
Before you source.
Can I request real photographs rather than generated images?
Yes. Make that distinction explicit in your brief, including whether edited, composited, or synthetic examples are excluded. The collection should be reviewed against that requirement.
Do all computer vision projects need annotation?
No. Some use image-text pairs, image-level labels, or unlabeled source images. Tell us the learning or evaluation task so the annotation discussion matches the actual need.
Can a sample prove class balance for the whole collection?
A sample can help assess style and labeling, but complete class counts and source documentation are needed to evaluate the proposed collection. Ask for the full coverage plan before deciding.
Where are the per-hour or per-record rates?
No fixed public rate is quoted because source requirements and preparation work vary. Email the project brief to Jaeden for a discussion of scope and a project-specific proposal.