What we do
Technical Translation and Localization Services
Translation is the core of what Techniwords does, and it rarely travels alone. Around it we operate a full set of technical language services: desktop publishing, software localization, terminology programs, post-editing, interpreting, and validation workflows, each run by specialists and each described honestly below.
Whatever the service, the ISO 17100-compliant backbone stays: specialist work, independent revision, and QA before anything leaves the building.
Translation memory, termbases, MT engines, and automated QA are tools we operate for your benefit, with savings shown line by line on every quote.
Every service page states its real turnaround math. When a date is on the quote, the date holds, including the rush jobs built around immovable deadlines.
Services Built Around How Technical Content Actually Moves
A translation request almost never arrives as plain text. It arrives as an InDesign catalog that needs multilingual page layout, a Storyline course that must be repackaged for the LMS, a batch of 400 drawings that would take weeks to handle by copy-paste, or a software repository that ships updates every two weeks. The services below exist because handling the container well is half the job of handling the content.
Techniwords has run these workflows for US industrial clients for 15 years, as a member of ATA and GALA. The translation itself, whether of a user manual, a safety data sheet, or a full technical document library, always runs on the same ISO 17100-compliant backbone. What changes per service is everything around it: the file engineering, the tooling, the deliverables, and the pricing model, which is exactly what each page below explains.
How to read this catalog: the document pages on this site tell you what makes each document type hard. The service pages tell you how the work gets done: pipelines, formats in and out, what you receive, and what it costs. Most projects combine one document type with one or two services, a catalog with DTP, a course with voiceover, a drawing set with batch CAD processing.
Localization Services
Adapting content for a market goes past language: units, standards, locales, interfaces, and search behavior all shift at the border. These services handle the shift.
Production & File Engineering
The services that turn translated text back into a finished, usable deliverable, in the same format your team started with.
Language Technology Services
The assets that make translation faster, cheaper, and more consistent over time. Built per client, owned by the client.
Quality & Assurance Services
Independent checks for when the stakes justify a second, third, or adversarial look at a translation.
On-Demand & Live Services
For the moments when the language need is happening in real time or the deadline was yesterday.
Combining Services Without Multiplying Vendors
Most real projects stack two or three of these services. A machinery manufacturer entering Mexico needs manual translation plus DTP plus a terminology baseline. A software company needs UI localization synchronized with documentation and release notes. Because one project manager runs the stack against one termbase and one translation memory, the pieces stay consistent with each other, and you brief one team instead of coordinating three vendors who never talk.
Every service is available across our 30 industries and 60+ languages, in both directions. If you are not sure which combination your project needs, send the files with a line about the goal; the quote will come back with the stack we recommend and why, itemized so you can strip out anything you want to handle in-house.
Services FAQ
Can I buy a service alone, without translation?
Yes. Companies bring us existing translations for third-party review, legacy TMs for cleanup and migration, or already-translated catalogs that only need multilingual DTP. Each service page states what the standalone version includes and costs. No bundling requirement, no pressure to move your translation work over, although the review often starts that conversation.
How do you decide when technology replaces human work?
By risk, openly. Machine translation with post-editing suits high-volume, low-risk content and we say so, with 40 to 60 percent savings. Safety warnings, patent claims, and regulatory text stay fully human, and we decline MTPE requests on those even when it costs us the argument. Every quote names the workflow so you always know what you bought.
Who owns the translation memory and termbase you build for us?
You do. Both are exportable on request at any time, in standard TMX and TBX formats, at no charge. We consider them your linguistic assets that we happen to maintain. It also keeps us honest: staying your vendor has to be earned by the work, not by holding your data.
Do these services cover all your languages and industries?
Nearly all, with practical limits we flag upfront. Voiceover talent pools are thinner in some languages than subtitling. CJK desktop publishing needs typography specialists we schedule ahead. Interpreting for rare language pairs may need more lead time. The quote states any constraint before you commit, never after.
How fast can a multi-service project start?
Quoting takes one business hour. Kickoff on standard projects usually happens within a day or two, the time to lock terminology and confirm the team. Rush work compresses that: the coordinated-team model can put translators on files the same afternoon, with the single-reviser structure keeping the output coherent.