Said once, applied everywhere
Approved terminology is applied whether a colleague pastes a paragraph or runs a full project.
Self-service · Built for business teams
Translate documents into languages your team doesn't read.
A simple tool anyone at work can pick up. Upload a file and get it back in minutes, formatting intact, your terminology applied, a product page and a service manual alike. No localization training, and nothing to configure before your first translation.
Segment 04812Live
en-GBSource
Check the pressure relief valve before every shift.
de-DEGerman
Prüfen Sie das Überdruckventil vor jeder Schicht.
·AI draftGlossary term applied
Made for the people who need translations, not the people who do them for a living
MarketingSales & exportHR & internal commsCustomer supportLegal & complianceProduct
The actual problem
The hard part isn't the translation. It's knowing how much this one mattered.
First
Some of what you send out is a product page. Some of it is a line in a service manual that a technician will follow with a wrench in their hand. In a language you don't read, the two look identical.
Then
So the tool decides instead of you. A chatbot treats both as disposable; an agency treats both as billable. You overpay for the harmless and under-protect the dangerous; and you can't tell which was which.
Later
Three teams each work out what to call the same component. All three answers are defensible. Nobody ever compares them, because nobody is in a position to.
en-GB · “pressure relief valve”de-DE
Marketing · product page · March
… mit integriertem Überdruckventil.
Support · service article · May
… das Druckbegrenzungsventil monatlich prüfen.
Compliance · declaration of conformity · June
… ein Sicherheitsventil nach EN ISO 4126.
Three departments, three defensible words. The third one names a regulated component class, and it is now in a declaration of conformity.
Every one of those calls was made by somebody who knew what they were doing. None of them was written down.
One system, four levels
How much this job is worth is your call, not the tool's.
Different people in the same company settle at different levels, and both are right. Support rarely leaves the first; compliance rarely leaves the last. Choose the level per job, not per account.
Nobody reviews itA person signs it off
TextFileTeam reviewHanded over
Level 03, run a project with your team
Somebody who knows the product signs it off.
- AI produces the first version using everything you've already approved
- The person who actually knows the terminology reviews it, not you, and not a stranger
- Assign reviewers, leave comments, track who signed off what and when
- Approved wording goes into your language data and comes back next time
Use it for
Specifications, instructions, anything a technician, an auditor or a regulator will act on. The jobs where being wrong has a price.
Constant across all four
Four different jobs. One language underneath all of them.
These are four ways of working, not four grades of the same one. What they share is one language layer underneath.
One voice, whoever wrote it
Formal, technical or marketing register stays consistent across people, teams and workflows.
The file survives the trip
Structure, tables and layout come back intact at every level.
One account, whole company
Most companies don't have a translation problem. They have six of them.
You saw three of them a moment ago. Every department solves it alone, with its own tool, and none of the answers ever meet.
How it usually works
Six standards, no shared vocabulary.
- Marketing has its own AI translation subscription
- HR pastes the handbook into a chatbot
- Sales asks the colleague in the Madrid office as a favour
- Support runs tickets through whatever is free
- Anything important goes to an agency and comes back weeks later
With one shared workspace
With one shared workspaceYour company's language becomes one thing, maintained by everybody who uses it.
- Everyone works on the same approved terminology, whatever they're translating
- New colleagues start without training, the same workspace covers a pasted paragraph and a full project
- Roles decide who can translate, who reviews and who approves
- One account instead of subscriptions nobody is tracking
- The colleague in Madrid becomes a reviewer, not a favour
What accumulates
Every correction is kept.
A fix that disappears into one department's email thread has to be made again next quarter by somebody who never saw it. A fix recorded here does not.
Someone corrects a term
A reviewer changes a product name, a unit or a phrase that reads wrong in-market.
The decision is recorded
Not as a comment. As an entry in your terminology and translation memory.
It comes back automatically
The next file, language pair and colleague benefit from the same approved wording.
There's less to review
Each round costs less time and less money than the one before it.
Your language dataEN-GB → DE-DE
pressure relief valve→Überdruckventil
Approvedintended use→bestimmungsgemäße Verwendung
Approvedresidual risk→Restrisiko
Approvedtorque setting→Drehmomenteinstellung
ApprovedThe first entry is the component from three paragraphs ago. It has one answer now, and nobody has to work it out again.
An agency keeps what it learns about your product. Here, it stays in your account.
Terminology, translation memory and approved wording belong to your organisation and can be exported. Change vendors, add markets, bring the work in-house; the language data goes with you, not with whoever did the last job.
Being honest about the ceiling
Where self-service stops being the right answer.
Everything above assumes a person decides when a document is good enough. Past a certain volume you need that decision made by the system instead, every time, without anyone remembering to make it.
The alternatives
What you give up with a chatbot, and what you give up with an agency.
Both apply a single level of care to every job. TextUnited lets you choose job by job.
| AI tools | Translation agency | TextUnited | |
|---|---|---|---|
| Level of care, set per job | One setting for everything | One process for everything | You choose, job by job |
| Speed | Fast | Days to weeks | Fast, and automated |
| Whole documents | Limited | Yes | Yes |
| Layout survives | Often breaks | Manual fixes | Always |
| Your terminology applied | Re-prompt every time | Manual, per project | Built in |
| Everyone in one system | A subscription per team | Everything through one gatekeeper | Shared workspace, roles per person |
| Your team reviews in the same place | No | No | Built in |
| Approved wording reused next time | No | Sometimes | Automatically |
| Who keeps what you approve | Nobody; it's gone | The agency | You |
| Hand the whole job over | No | Yes, after a quote | Yes, priced on screen |
Questions
Before you start
The practical questions teams ask before their first document.
Can I translate a PDF without breaking the layout?
Yes. TextUnited is built for document translation, so structure, tables and layout are preserved through the round trip.
Why isn't ChatGPT enough for translating documents?
Chatbots generate sentences, but they are not built around files, terminology memory or team review. Formatting and consistency usually require manual repair.
Which file formats can I translate?
PDF, DOCX, PPTX, XLSX, XML, InDesign IDML, JSON, SCORM and other common business formats.
How do I know which documents need human review?
If being wrong would cost money, safety or certification, put a person on it. Otherwise, automated translation may be enough.
Can the whole company work in one account?
Yes. Teams share approved terminology, while roles control who translates, reviews and approves.
What happens when my team corrects an AI translation?
The correction becomes part of your language data and is reused automatically in the next file.
Can I hand a project to TextUnited instead?
Yes. Upload the file and choose the level of professional review that matches the content.
Do I keep my terminology and translation memory?
Yes. The language data belongs to your organisation and can be exported.
Is there a minimum volume?
No. Start with a single document on a free account.
Do my colleagues need training?
No. It's built for people who need translations as part of another job, not for localization specialists. Pasting a paragraph and running a full document project happen in the same workspace, so somebody who has only ever done the first can do the second without learning a new tool.
Can several people review the same document?
Yes. You can assign reviewers, leave comments, track progress per file and language, and approve content in one shared workspace, without emailing versions around or chasing people for status.
What happens when a project needs professional handover?
You can hand the project to TextUnited and choose the level of professional review that matches the content.
Start with one file
Start with one file and see what comes back.
Upload a document, generate the first translation and hand it to someone on your team to check. You'll know within ten minutes whether this works for you.