Voice-data searches surface broad data-service providers, speech-focused firms, dataset marketplaces, and open repositories. Those labels do not establish source quality, language reach, rights, or delivery capability. This guide turns names such as Appen, Defined.ai, Shaip, TELUS Digital, Sama, Sigma.ai, Spirelight, and Mozilla Common Voice into a diligence shortlist rather than a ranking.
Provider ownership and services change. Verify current official evidence and compare every candidate against one written brief covering speakers, conditions, annotations, provenance, rights, QA, sample evidence, capacity, schedule, and price.
Who provides voice training data
Buyers commonly encounter four supplier categories: broad managed providers, speech-focused providers, dataset marketplaces, and open repositories. Marketplaces may list data from multiple publishers, while managed suppliers may collect directly or through partners. A provider may also span more than one category.
Names buyers may consider include Appen, TELUS Digital, Sama, Defined.ai, Shaip, Sigma.ai, Spirelight, and Mozilla Common Voice. Inclusion here is not a claim about current capability, quality, ownership, or fit. Check current official materials, the exact publisher or collection partner, and a project-specific proposal. The Appen alternatives guide and AI training data company guide provide related procurement frameworks.
Seven fields to compare
| Field | Evidence to request |
|---|---|
| Language and dialect | Target variety, recruiting channel, screening method, speaker cells, subcontractors, and feasibility assumptions |
| Recording conditions | Device, microphone geometry, environment, channel layout, speech type, and deployment match |
| Volume and capacity | Usable-hour definition, pilot size, recruiting capacity, dependencies, schedule, and rejection assumptions |
| Collection status | Finished inventory, third-party listing, custom collection, or feasibility target; version and sample availability |
| Rights and privacy | Publisher and source chain, permissions, license, applicable lawful basis and notices, retention, transfers, and consent records when relied on |
| QA and annotations | Guidelines, reviewer qualifications, agreement method, sampling, thresholds, rework, and sample evidence |
| Engagement and commercials | Named roles, subcontractors, change control, security, minimums, included work, currency, taxes, schedule, and final price |
Supplier category does not predict the answer. Verify publisher identity, source chain, permissions, speaker coverage, subcontractors, recording method, and QA for the exact delivery rather than inferring them from category.
Rights, privacy, and provenance
Start with the intended use, not a universal consent checklist. Ask what rights the supplier or publisher actually holds, what the license permits, and which privacy records apply. For personal data, the relevant lawful basis, notices, roles, retention, transfers, and data-subject handling are project-specific. If consent is relied on, request the applicable evidence and withdrawal process.
Exclusivity, redistribution, model-related rights, territory, term, retention, and risk allocation are contract-specific. The speech data licensing guide explains the questions to put in the diligence record.
Low-resource and multilingual sourcing
A headline language count does not establish dialect coverage or recruiting capacity. Ask for the named variety, recruiting locations, screening method, target speaker cells, reviewer qualifications, subcontractor disclosure, pilot evidence, and schedule assumptions. See the low-resource language guide for a detailed brief.
Finished license or custom collection
A finished asset may shorten lead time when its source, speakers, conditions, annotations, rights, and QA match the use. A custom collection may fit a narrower brief, but its feasibility, pilot design, capacity, schedule, and price still need confirmation. Compare both routes against the same acceptance test; do not assume one is faster or cheaper by category. The custom collection guide covers the workstreams to specify.
Where Spirelight may fit
Spirelight can assess a voice-data brief. Required sourcing, protocols, reviewers, permissions, privacy and provenance records, licensing terms, annotations, QA, sample evidence, capacity, schedule, and price must be confirmed in writing. Collection configuration pages are planning references, not proof of finished inventory or a universal documentation package.
Send the languages, speaker cells, recording conditions, intended use, volume, and acceptance criteria through the written project brief. The response will state whether the scope can be assessed and what evidence is available.