Service
Multilingual Data Collection in India
Parallel programmes across several Indian languages at once, run to one specification so the resulting datasets are comparable rather than a set of incompatible deliveries.
- Turnaround
- 6-12 weeks for a multi-language programme, depending on the smallest-pool language in scope.
- Languages
- 14 Indian languages + Indian English
- Delivery
- Per-language datasets in one schema
What you get
- Per-language datasets in one schema
- Cross-language coverage report
- Consolidated QA summary
Technical specification
Every parameter below is written into the statement of work before recording begins. If your pipeline needs different values, they replace ours rather than being converted after delivery.
| Parameter | Standard |
|---|---|
| Languages | Up to 14 Indian languages plus Indian English in one programme |
| Consistency | One spec, one manifest schema, one QA standard across all languages |
| Balance | Per-language quotas set independently to match your deployment mix |
| Reporting | Single consolidated progress view across languages |
How the work runs
- Master specification written once and localised per language
- Per-language linguistic review of prompts and guides
- Parallel fielding across studio cities
- Central QA applying identical thresholds
- Consolidated delivery with per-language reports
Quality control
The hardest language sets the timeline. Low-resource languages such as Assamese and Odia should start first.
QA failures are remedied by re-collection, not by editing the delivered files. Repaired audio introduces artefacts that survive into your model.
Speaker and contributor sourcing
Each language is fielded from its own home region, not from a single metro with mixed speakers.
Consent is captured per participant and mapped to file IDs, so provenance survives an external audit of your training data.
Timeline
6-12 weeks for a multi-language programme, depending on the smallest-pool language in scope.
Staged delivery is available: first batches ship while later batches are still recording, so training can start early.
The numbers we hold ourselves to
- 100% of delivered files pass automated technical QA for SNR, clipping, duration and silence
- 5-25% of files pass a second native-speaker content review, stratified by city, dialect and transcriber, and escalating to 100% on any batch that fails the agreed threshold
- Accepted yield runs 85-90% for scripted speech, 60-70% for spontaneous, 55-65% for conversational and 50-60% for telephony
- Default cohort quotas: 50/50 gender, with age bands at 30% (18-25), 40% (26-40) and 30% (41-60)
- 48 kHz / 24-bit capture, delivered as 16-bit PCM WAV, with studio sessions held below a -50 dBFS noise floor
- First response within one working day; a scoped, fixed quote within two to three
These are the figures a delivery is measured against, not aspirations. A batch that misses them is re-recorded at our cost rather than repaired.
Commonly used for
- Multilingual ASR
- Multilingual LLM data
- Pan-India voice products
Frequently asked
What is the minimum volume for multilingual collection?
Programmes typically start around 50 hours or equivalent units per language. Smaller pilots are accepted when they lead into a larger build, because most of the setup cost is in specification and recruitment rather than recording time.
Can you work to our schema instead of yours?
Yes. Manifest fields, file naming, directory structure and label schema are set by you. Working to your schema from the start avoids a conversion pass that usually loses metadata.
Who owns the delivered data?
You do. Deliverables come with a perpetual, transferable licence and participant consent that covers model training and distribution of the resulting model.
How is pricing structured?
Per delivered hour or per unit, quoted against a written specification. Quotas, recording conditions and QA thresholds all move the price, which is why we quote from a spec rather than from a price list.
Get a quote for multilingual data collection
Send the specification you already have, or the rough shape of it, and you get a scoped quote with a timeline.