Fiund / Project pricing
Pricing follows the specification.
A useful quote for call 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.
Source and scenario
Real or staged; inbound or outbound; industry, date range, and interaction types.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Audio channels
Mono mixture, stereo separation, or independent tracks; source encoding and sample rate.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Transcript scope
Verbatim or normalized text, timestamps, speaker labels, overlap, and non-speech conventions.
Include the required coverage and acceptance threshold in the quote request so this work can be scoped explicitly.
Permission and privacy
The specific proposed training uses, relevant source permissions, and de-identification requirements.
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.
Is stereo audio necessarily separated by speaker?
No. A two-channel file should be inspected to establish what each channel contains. If agent and customer separation is required, state it explicitly and request samples that demonstrate the channel layout.
Can I request authentic calls instead of role-play?
Yes. Make authenticity a required property and identify acceptable scenarios. Source documentation, permissions, and privacy handling need project-specific review.
Can I send a short inquiry without a complete specification?
Yes. Start with language, approximate volume, scenario, and intended use. Jaeden can follow up on the missing details before discussing suitable sources or samples.
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.