Define what the quote counts
A price per image means little without a clear unit. Determine whether the count includes original photographs, derivatives, accepted images, or annotated instances. State required metadata and delivery processing alongside the images themselves. Ask which items are included and which are optional so proposals can be compared without silently changing the collection you are trying to acquire.
Identify the difficult requirements
Rare categories, distinct locations, specialized access, complex masks, and detailed review can change feasibility and effort. Separate mandatory constraints from preferences. A requirement that removes most existing archive material may make new collection worth discussing, but that decision needs representative examples and source review. Avoid treating a low nominal image price as evidence that every condition is covered.
Compare usable coverage
Review the number of independent subjects and source groups behind the delivered file count. Repeated crops and bursts may serve a purpose but should not be confused with broader coverage. Consider the effort your team would spend repairing annotations or reconstructing relationships. A proposal with clear documentation can be easier to evaluate than one with more files and unresolved assumptions.
Use a pilot to narrow uncertainty
Ask for project-specific options after the sample has clarified the specification. Compare changes in scope, review effort, and deliverable structure rather than inventing a universal market rate. Fiund does not publish a guaranteed inventory or fixed price here. Sourcing feasibility, permitted uses, samples, and commercial terms are reviewed for the actual project and proposed material.
Review checklist
- Define the counted unit in every proposal.
- Separate mandatory constraints from preferences.
- Compare independent coverage and repair effort.
- Request project-specific options after sample review.