AI Data · For vendor managers

An Asian-language production vendor
for your AI data supplier pool

Written for vendor and supply managers at multilingual vendors and AI data companies. What we have delivered as a subcontractor, how a batch runs inside your workflow, and what we can return when you send an onboarding pack.

Send us your supplier onboarding pack →
Delivered as a subcontractor
Four kinds of AI data work,
delivered inside another vendor's program

Our AI data production to date has run as a company-to-company subcontract under a global language-services provider, feeding major AI programs. We do not name the programs or the parties. This is the work itself.

Transcription validation

Rolling weekly batches across seven locales — Mandarin (Mainland), Taiwan Mandarin, Cantonese, Korean, Japanese, Tagalog and Turkish, each including code-switched English. Billed by effort hour, with per-file logging.

Speech recording

Cantonese and Cantonese–English recording in Hong Kong, including hundreds of two-speaker service-call scripts recorded on separated tracks.

Annotation and scoring

Proofreading and quality scoring of Korean–Chinese song-lyric data against a client rubric.

In-market testing

Ongoing on-device testing in Hong Kong with local testers, reported month by month.

From a live line
What a vendor manager actually sees

Dozens of batches, an internal deadline ahead

A multi-month program in seven Asian language directions, each batch on a short deadline, with our internal deadline six hours ahead of the client’s to leave room for review. We recruited on demonstrated, everyday code-switching rather than declared native language, and by the second month time per task had fallen below half of the first month’s in most languages.

Rework once, then first-pass

On the two-speaker Cantonese–English recordings, the first batch came back for headphone bleed and unsynchronised tracks. The fix went into the recording specification (a counted sync, in-ear monitoring with a level rule, a merged-track check before delivery), and later batches passed first time.

Inside your workflow
How a batch runs when we are your vendor

Your tooling or ours

We work in the client platform when the program requires it, or on our own task platform with per-file effort logging and an export that matches your schema.

A written locale guide

Your specification becomes a locale guide covering orthography, verbatim policy, code-switch tagging, written-form numbers, segmentation and PII handling — amended after every correction cycle so the same error does not come back.

Scored QA with gates

Error categories with pass gates and sampling. For Traditional Chinese, every file passes an automated Simplified-character check before a reviewer sees it; word timestamps are checked against the waveform when the spec asks for them.

Intake check first

Audio and reference text are aligned before work starts. Re-cut files or revised scripts are flagged back to you rather than found after hours of validation.

A yes or no on rush jobs

On a short-deadline job we answer with a yes or no first and ask clarifying questions after accepting. We learned that a list of questions before a commitment is how a job goes to someone else.

One local team and team lead per locale

The same local team and team lead stay on a locale from batch to batch, so context builds up instead of resetting — that is where the effort-per-unit drop came from.

Supplier onboarding
What we can return when you send the pack

Entity and certification

Contracting entity Translia Limited (Hong Kong), with operations in Beijing through 北京传为文化有限公司. ISO 17100 and ISO 18587 certified.

Agreements

We review and sign your NDA and MSA on your paper, and work through your e-signature and supplier-portal steps.

Capacity form, locale by locale

We complete capability and capacity forms per locale, mark each figure as firm or an estimate, and leave a row blank when we cannot field people for it. See our Asian-language capacity by locale.

Consent, provenance and a scored sample

Participant consent and provenance records per recording, and (under your NDA) a sample locale guide with a scored transcription sample.

Pricing is per effort hour for validation and per accepted unit for collection. If your target rate sits below what the speaker screening costs, we tell you that and why rather than accept and miss.

Common questions
Vendor onboarding,
answered

Do you work as a subcontractor under another vendor's client?

Yes. All of our AI data production to date has been company-to-company work under a larger vendor's program. We report to you, do not contact the end client, and do not name the programs we have worked on.

Which Asian locales can you staff today?

Seven locales have delivered production batches: Mandarin (Mainland), Taiwan Mandarin, Cantonese (Hong Kong), Korean, Japanese, Tagalog and Turkish, each with English code-switching. Seven more are ready to activate with a pilot. The capacity page lists what each locale has delivered.

Do you have datasets available for immediate licensing?

No. We have no off-the-shelf dataset to license. We record, transcribe and validate to your specification, starting with a pilot batch.

How quickly can a new line start?

A Cantonese–English recording line went from pilot to hundreds of scripts within three weeks. A new line starts with a pilot batch on your specification; volume follows once the pilot passes your review.

How do you price?

Validation and transcription by effort hour with per-file logging; collection per accepted unit. Invoicing follows your supplier terms.

Adding an Asian-language vendor to your pool?

Send the onboarding link, capability form or a pilot spec — we'll return it locale by locale.

Contact our data team →