LSPs · Translation Agencies
Pre-translation for LSPs. Your reviewers stop translating from scratch.
Bulk SDLXLIFF, MQXLIFF, Phrase TXLF, and Wordfast files run through Fily's 12-step pipeline before your in-house reviewers touch them. Post-edit time drops 60–80%. Your PM team scales without growing.
Who uses Fily for lsps & translation agencies
Mid-size language service providers, certified translation agencies, and localization consultancies that process bulk CAT-tool files from end clients. Our customers handle batches of 10K–1M words/week across Trados, memoQ, Phrase TMS, and Wordfast.
What hurts today
- Translators spend 70% of their time editing mediocre MT output instead of translating.
- Tag preservation in SDLXLIFF, MQXLIFF, and TXLF is brittle — generic AI tools drop, duplicate, or renumber tags, breaking on Trados/memoQ import.
- TM 100/101 matches get "improved" by AI tools, destroying client-approved content and breaking your TM analytics.
- Client-specific glossaries and forbidden-term lists need to cascade across orgs, clients, and sub-clients without manual re-attachment per job.
- Batches arrive overnight — humans can't keep up without growing the PM team proportionally.
- Margin pressure from declining per-word rates means you need to deliver more volume per existing translator.
How Fily fits this workflow
Native CAT-tool pipelines per format
Dedicated pipelines for SDLXLIFF (Trados), MQXLIFF (memoQ), TXLF (Phrase / Wordfast). Tag count repair, locked-TU handling, xid normalization — all verified across Studio 2019–2026, memoQ 9.x–11.x, Phrase 6.x–8.x.
Hard TM 100/101 pass-through
Matches marked 100% or 101% never go to the AI. Byte-for-byte copy to target. Your TM stays clean, your client's review filters work, your analytics survive.
Glossary cascade org → client → subclient → job
Define a term once at organization level, override at client level, override again at subclient. Glossary enforcement mutates output — forbidden terms get replaced automatically.
Batch ZIP delivery
Upload a ZIP of 50 SDLXLIFFs from a client project. Get a ZIP back with all 50 translated, QA report per file, ready to import into Trados Studio.
Dedicated Account Manager
Real human accountability when something needs judgment. AI speed of a tool, human accountability of a vendor — only Fily has both at this price point.
Volume discounts
Pricing scales down with volume. LSPs processing 200K+ words/week get pricing that makes outsourced AI translation cheaper than growing the translator team.
Shipped, not roadmapped
Pipelines we built for work like this
Real lsps & translation agencies workflows that didn't fit a standard pipeline — so we built one.
docx_tracked_delta_v2
Tracked changes that survive translation
An LSP had already translated v1 of a Word doc to Spanish. The client edited the English with tracked changes and wanted v2 in Spanish with the same redlines applied — not a fresh re-translation.
We built a delta-aware DOCX pipeline that ingests EN + redlines + ES_v1 and emits ES_v2 with the equivalent insertions and deletions in Spanish. The reviewer keeps the audit trail — hours instead of days per round.
4-layer cascade
Multi-tenant glossary cascade
An LSP with 40+ end-clients needed org-level terms, client-level overrides, and sub-client (brand) overrides to all stack — without re-attaching glossaries to every job.
A 4-layer cascade: system → org → client → sub-client → job. Forbidden terms inherit and override, style guides cascade, and every future job picks up the right rules automatically.
docx_pair_review
Two Word docs in, a reviewed delta out
A client sent the original DOCX plus a reviewer's corrected copy and asked, in effect, 'what did we actually change, and can you apply the same corrections going forward?'
A pair-aware pipeline aligns both files, extracts the human corrections as tracked changes, and surfaces them in the browser review editor — billed only for segments that actually changed.
Golden TM · auto-build
A translation memory that builds itself
Clients wanted TM leverage but didn't want to maintain a TM — exporting, cleaning and re-importing TMX after every project is a job nobody has time for.
Every confirmed segment is promoted into the organization's Golden TM automatically, scoped per client and language pair, and reused on every future job. Reviewer edits in the dashboard feed straight back in. Exact matches then cost $0.
Got an edge case your current vendor can't handle?
Talk to our Account Manager teamFormats this industry usually translates
All ship through the same 12-step QA pipeline.
Ready to test it?
Upload one file. See it come back. No card. No demo form.