Vendor selection
Hiring a asr training data company in India
What to look for when you hire a asr training data vendor in India, the questions that separate a delivery partner from a reseller, and how engagement usually works.
- Engagement
- Fixed-scope or retained capacity
- Start
- Pilot within one week
- Coverage
- 14 Indian languages, 20 cities
- Contract
- NDA, MSA, per-project SOW
What good looks like
A capable vendor can describe every step above without hedging, name who performs it, and show you the artefact each step produces.
- Style guide authored per language, covering numerals, loanwords, script and disfluency rules
- Transcriber calibration round with inter-annotator agreement measurement
- First-pass transcription
- Second-pass native review
- Automated consistency checks against the style guide
- Split generation with speaker-disjoint partitions
Vendor evaluation checklist
| Check | What a strong answer sounds like |
|---|---|
| Who does the work | Named in-house teams and directly contracted studios, not an unnamed partner chain |
| Quota enforcement | Enforced at recruitment intake with live dashboards, not reconciled after delivery |
| QA model | Agreement is measured, not assumed |
| Failure handling | Re-collection at vendor cost, never editing delivered files |
| Consent | Per-participant written consent mapped to file IDs and retained for audit |
| IP | Perpetual licence with full transfer, stated in the SOW |
| Data security | Access-controlled transfer, defined retention and deletion, DPDP-aligned handling |
Engagement models
Transcription adds roughly 1-2 weeks per 100 hours after recording, per language.
- Fixed-scope project priced against a written specification
- Retained monthly capacity for continuous data needs
- Paid pilot converting into a production run
- Managed overflow alongside an existing vendor, delivering into their schema
What you receive
- Audio plus aligned transcripts (JSON/TSV, or your schema)
- Style guide as delivered documentation
- Inter-annotator agreement report
- Speaker-disjoint train/dev/test splits
How we recruit
Transcribers are native speakers of the target variety, not of a related standard language.
Typical reasons buyers switch vendors
- Delivered dialect mix did not match the quota that was agreed
- Transcripts normalised code-mixed speech into a single script, destroying the signal
- No traceable consent, blocking the model from commercial release
- Account layers between the buyer and the people doing the recording
- Rejected material re-delivered after editing rather than re-recording
Frequently asked
How do I choose a asr datasets vendor in India?
Run a paid pilot with two shortlisted vendors on an identical specification and compare quota compliance, transcription accuracy against a blind re-transcription, metadata completeness and how each handled a failure. Three weeks of pilot beats any questionnaire.
What contracts are involved?
An NDA before specification exchange, a master services agreement, then a per-project statement of work carrying the specification, acceptance criteria and price.
How fast can work start?
Specification and quote in one working day, pilot in recruitment within a week, first recorded batch typically in week two or three.
Do you work with overseas buyers?
Most of our work is for AI teams outside India. Invoicing in USD or EUR, asynchronous reviews and delivery into your storage are all standard.
Related pages
Shortlist us for asr datasets
Send the requirement and we will come back with a scope, a price and the names of the people who would run it.