Fiund / Project pricing
Pricing follows the specification.
A useful quote for business 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.
Record definition
What one document, row, or case represents; how related records are grouped.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Coverage
Countries, languages, industries, date ranges, document families, and layout diversity.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Data dictionary
Field meanings, units, missing-value conventions, stable identifiers, and provenance information.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Sensitive information
Required removal or replacement of personal, confidential, financial, and account-level details.
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 genuine business documents?
Yes. State that authentic records are required, and identify acceptable origins and document types. Sourcing fit, permissions, confidentiality, and de-identification need review for each collection.
Should I ask for raw files or extracted tables?
That depends on the task. Layout understanding may need original documents; structured analysis may need normalized records. If you need both, specify how each extracted record must link back to its source.
Are all categories available in the same volume?
No volume is promised on this site. Send your required counts by category so Jaeden can discuss availability and sourcing options without treating a broad category label as confirmed inventory.
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.