Said once, used everywhere
Approved terminology is applied whether a colleague pastes a paragraph or runs a full project.
Self-service · Built for the whole company
Your company translates every day. Put it in one place.
Marketing, HR, training and support use their own tools. One solution gives them a more secure way to translate, with your terminology and style, and nobody needs training.
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
How it happened
Nobody chose the tools your company uses to translate.
A subscription
Marketing pays for its own translation tool. Nobody else in the company knows the account exists.
A free tool
A trainer pastes a module into a chatbot. Support runs tickets through a free website.
Traditional solutions
Sales asks a colleague in Madrid as a favor. Important projects go out to an agency and come back days later.
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.
Each of those choices made sense at the time. Together they leave the company with different terminology in every department and no style guide behind any of it.
Centralising translation usually makes you the help desk.
That is the real reason companies leave translation scattered. Whoever brings the tool in answers the questions about how to open a file, decides what a word should be, and gets blamed when anything goes wrong.
None of that happens here. Our support answers your colleagues directly.
One system, four tasks
Different tasks carry different risks.
The colleague who sends the file decides how much this one matters.
InternalCustomerInstructionsLegally binding
Instructions
Somebody will follow it at work.
- Approved terminology, the same term in the manual, the module and the label
- Someone who knows the product signs it off before it goes out
- You can see who approved what, and when
What it covers
A training module, a service manual, a safety instruction, an onboarding pack. If a word is wrong here, somebody acts on it, and you find out from the person it happened to.
Choosing a way to translate does not require a new contract or a separate budget. It is a decision made per job, inside the account you already have.
Constant across all four
Four different tasks. 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.
Files keep their formatting
PowerPoint, PDF, InDesign, SCORM or XML come back with structure, tables and layout unchanged.
One account, whole company
No one can actually control how your company speaks in other languages.
Every department solved it alone, and each solution works (kind of). What is missing is transparency.
What that costs you
Each department picked its own tool.
- Nobody can say which German word the company uses for its own components
- The same correction is made again every few months, by someone who never saw the first one
- A new colleague copies whatever the last person did
- You hear about a bad translation from the market, not from your own team
- Nobody knows what the company spends on translation in total
With one shared workspace
With one shared workspaceEveryone works in the same account.
- Everyone works on the same approved terminology and the same style guide
- Roles decide who can translate, who reviews and who approves
- New colleagues start without training
- Single sign-on, so colleagues use their company login
- The colleague in Madrid checks the Spanish inside the account, instead of by email
What accumulates
Every correction is kept.
A correction saved in one department's email thread is lost. Next quarter a colleague who never read that email does the same work again.
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, the next language and the next colleague get the same approved term.
There's less to review
Each project costs less time and 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 style guide belong to your organisation, you can export them, and your content sits in your own tenant. Change vendors, add markets or bring the work in-house, and the language data goes with you.
Start with one file
Start with one file and one department.
Translate one document, give the result to a colleague who reads that language, and within a day you will know whether to make this your company standard.
The alternatives
What each option gives you and what you give up
| AI tools | Translation agency | TextUnited | |
|---|---|---|---|
| Marketing content | You re-prompt for brand voice all the time | You send the style guide and the linguist follows it | Your style guides are applied to every translation automatically |
| Manuals and instructions | A different word for the same part in each document | The agency keeps the data and uses it while you stay with them | Terminology is stored in your account and all teams use it |
| Regulated documents | No record of who approved what | Each update is a separate project, and the previous version stays with the agency | Every language version and every correction stays in your account |
| Whole company access | A subscription per team or insecure free usage | Every request goes through account or project managers | One account, roles per person |
| Company terminology | Nothing is saved after you close the window | Held and managed by the agency | Stays in your account, edit or export at any time |
| Support for your colleagues | None | Depends on the contract | Handled directly by us |
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.
Is there a point where this stops being enough?
Yes. At high volume a person cannot check every document, and the decision has to be made automatically. Our team can tell you where that line runs for your content.
Before you decide
Tell us what your setup looks like.
If your situation is not covered above, we will tell you what it takes to run it in one account, from user provisioning to getting your existing terminology in.