Programs that need 30 languages don't run on one vendor's roster.
We staff, coordinate, and ship across 250+ languages.
That includes the uncommon and refugee-resettlement pairs that aren't on
a standard LSP roster. One accountable program manager from Orlando,
every engagement. Documented QA on every batch.
Five regions. 250+ languages. Every major writing system.
Coverage indicators reflect active sourcing across regional desks.
Rare-pair availability is sourced on demand and confirmed in scope return.
38+North American Navajo, Haitian Creole, Nahuatl
Latin · Inuktitut · Cherokee · ASL
31+South American Quechua, Guarani, Aymara
Latin · Indigenous syllabaries
42+European Romani, Sami, Kashubian
Latin · Cyrillic · Greek
64+African Tigrinya, Wolof, Hausa, Oromo
Latin · Geʽez · Tifinagh · N'Ko · Vai
75+Asian Meitei, Dari, Karen, Sylheti
CJK · Devanagari · Arabic · Thai · 30+ more
Coverage · Matrix
Thirty rare languages, by status and script.
A sample of pairs teams have brought to this desk in the last 18 months.
Active = on roster, scoped from Orlando.
On-request = sourced from vetted bench, with lead time confirmed before scope lock.
Multilingual annotation, GenAI evaluation, speech transcription, data collection. Domain-tested annotators matched to data type; structured QA on every batch.
Software, web, and marketing localization with multilingual rollout coordination. RTL, CJK, and complex-script handling. TMS integration with Phrase, XTM, MemoQ, Smartcat.
Subtitling, dubbing, voice-over, transcription for media platforms and enterprise content. SDH captioning, audio description, multi-format coordination.
200+ langs · 3,000+ voice talents · 100+ studiosSDH · AD
Operations · Flow
How a program moves through this office.
Six checkpoints from intake to close. Timing markers below reflect a typical
4-week program; rare-language sourcing or compliance-heavy work extends the
early phases and is scoped explicitly on intake.
Co-branding or named-subcontractor disclosure is the more common arrangement
Deliverables, communications, and outputs carry your brand; subcontractor disclosure coordinated per your client agreements and applicable ISO traceability
When you're already in a client relationship, overflow capacity needs to align with your existing disclosure terms.
Multi-language coordination
One PM per language pair is common; cross-pair coordination falls to the client
One Orlando PM coordinates linguists, QA, deadlines, and deliverables across all pairs in a program
A 12-language rollout shouldn't require 12 separate vendor relationships.
Documentation deliverables
Translated files; QA log and edit history typically scoped as an add-on or omitted
QA log, edit history, glossary delta, and a compliance summary mapping to applicable ISO clauses on request
Procurement, legal, and audit teams need provenance, not just deliverables.
ISO scoping
ISO 17100 is common; 27001 and 9001 coverage varies by provider
ISO 9001:2015, 27001:2022, and 17100:2015 are all active; scope return names which standard applies to which deliverable
Compliance-sensitive work (healthcare, public sector, finance) typically requires all three standards together.
Triggers · When teams call
What usually triggers a brief.
Five patterns account for most engagements that land here. They tend to
surface during a quarterly program review, after a vendor RFQ comes back
wrong, or in the week before a regulatory deadline.
A current vendor cannot cover the language pair: particularly rare, indigenous, or refugee-resettlement languages.
Timeline is compressed beyond standard vendor sourcing: multilingual launches, regulatory deadlines, public-safety releases.
Multi-language rollout needs one coordination point: instead of routing through five separate LSPs.
Compliance-sensitive work needs documented controls: ISO certifications, NDA coverage, audit-ready QA logs.
Overflow support for LSP partners: white-label delivery without client-facing exposure.
Intake · Sample brief
What a one-page program brief looks like.
No sales-cycle form, no scoping call before a scope. Seven fields,
sent by email or pasted into the form. We return a scope, timeline,
sourcing plan, and risk notes after review.
Program brief · Sample intakeBRIEF-2026-0421-RR
Program
Customer-support knowledge base for a multilingual rollout at a refugee-resettlement nonprofit
200 articles · ~85,000 source words · Notion export
Volume
~640,000 target words (estimate, expansion factors applied per language)
Deadline
Rolling delivery over 8 weeks; active-roster languages (Pashto, Dari, Burmese, Tigrinya) within 21 days; on-request languages (Karenni, Rohingya) confirmed at scope lock
Compliance
NDA before scope; ISO 27001 controls applied; final QA pack required
Notes
Source written in plain English (Grade 8 reading level). Tone calibrated for newly-arrived caseworkers; preserve that register. Glossary not available; build from scratch.
ISO 9001:2015 across all service desks. Per-program QA gates documented in delivery logs.
Information security
ISO 27001:2022. NDA coverage applied before any linguist receives source material.
Translation services
ISO 17100:2015 for translation production. Reviewer step on every TEP engagement.
Documentation
QA log, change history, and compliance summary available on request after delivery.
FAQ · Procurement questions
What teams ask before sending a brief.
Questions we hear most often during scope conversations. If yours
isn't here, send it in the brief and we'll answer in the scope return.
Can you cover a rare language pair on a short-deadline brief?
Active-roster languages may be viable after intake. Rare and on-demand languages (Tamazight, Bambara, Hanifi Rohingya, K'iche', etc.) require a sourcing window, with bench-depth verification before scope lock. We will tell you in the written scope return whether your pair is active or sourcing.
Do you sign an NDA before scope discussion?
Yes. Mutual NDA on engagement is standard; we'll countersign yours or send ours during intake. Linguists working on your program receive program-specific NDAs that bind to your source material before they see any content.
How does pricing work — per-word, per-hour, or project?
Translation, localization, and AI data work are typically per-word or per-unit with volume tiers. Interpretation is per-hour with minimums. Multimedia (subtitling, dubbing, voice-over) is per-minute of source duration. Project-based pricing available for sprints with defined scope. Scope and pricing are returned together in the written scope reply.
What does white-label delivery mean for LSP overflow?
Your client signs with you. We staff, produce, QA, and deliver under your brand. Deliverables, communications, and final outputs carry your identity. Subcontractor disclosure follows your client agreements and applicable ISO 17100 traceability requirements; we coordinate disclosure language in scope so your existing terms are honored. Used by LSP partners who hit a coverage gap, a capacity ceiling, or a request they can't fulfill internally.
Is ISO 17100 in scope for all services?
ISO 17100:2015 specifically governs translation production. It applies to our human translation and review work (TEP). It does not extend by definition to interpretation, AI data annotation, transcription, or evaluation; those operate under ISO 9001:2015 and ISO 27001:2022. We name which standard applies to which deliverable in scope.
Can you coordinate across five or more language pairs in one program?
Yes. This is the most common reason teams bring us in. A single Orlando program manager coordinates linguists, QA, deadlines, and deliverables across all pairs. You receive one batched delivery per cadence (rolling weekly, milestone-based, or final), one consolidated QA report, and one invoice, not five separate vendor relationships.
What does your QA documentation deliverable look like?
On request, every program ships with: per-batch QA log (reviewer, gate results, change counts), full edit-history file, glossary delta (terms added, terms changed), and a compliance summary mapping deliverables to applicable ISO clauses. Useful for audit prep, procurement sign-off, and downstream regulatory submissions.
How do you handle compliance escalations during a program?
Compliance-sensitive issues (data residency, source provenance, reviewer credentialing, regulated content) escalate to the Orlando PM during intake or production review. We don't reassign without your sign-off. If we identify a compliance risk in your source material before delivery, we flag it in writing and pause production until you confirm direction.
Contact · Program brief
Send a brief. Get a scoped reply from the desk.
Tell us the program, the languages, the volume, and the deadline.
We return a scope, timeline, sourcing plan, and risk notes within
intake review. No sales cycle to clear before we engage.