Product · Context
Give Localizethat the knowledge your team already has.
Set it up once. Use it when you localize. Your brand shouldn’t start from zero with every project.
Your Context is ready when the work starts — nothing to pick or configure per project.
Global Master Voice
Localization
Q4 Product Launch
- Swedish
- German
- French
What lives in your Context.
The knowledge your team already has, in one place — added by the people who own it.
Define how the company communicates.
Give Localizethat guidance on how your brand should sound across markets — as a core brand voice, and as channel-specific variations.
Voice & style · Brand voices
Company ruleName
Global Master Voice
Tone
Confident, plain, never hyped
Avoid
Superlatives, jargon, exclamation marks
Keep important words consistent.
Store preferred terms, product names and language-specific terminology so teams don’t have to solve the same questions repeatedly.
Language assets · Glossary
Swedish- Company contextDo not translate
- localization runkörning
- creditkredit
- approved language memorygodkänt språkminne
Language rules capture what changes per language.
Give localization the information behind the words.
Add the product information Localizethat needs to understand what the content is actually describing — including how each content type should be handled.
Localization defaults
Applied automaticallyReuse what has already been decided.
Approved claims and cleared wording stay available, and approved language from finished reviews is kept for similar content later.
Claims & governance
ApprovedApproved language memory
Grows as reviewers approve localized content. Everything else stays under your control.
Set it up once. Use it when you localize.
Context isn’t a checklist you work through before every project. It is already there when the work starts.
Build your Context
The people who own the brand, the terminology and the product add what they know. Once.
Localizethat makes it available when you localize
Start a localization and the relevant parts of your Context come with it. No settings to pick, no prompt to write.
Approved work supports later work
When a reviewer approves a language, that approved wording is kept as language memory and can be reused when similar content comes back around.
Context is why the rest works.
Localization uses your Context. Review gives people the final say. You maintain the knowledge, not the process.
Context
Company knowledge
Localization
Uses that knowledge
Review
Human control
Your Context is ready when the work starts.
Build it once with the knowledge your team already has, then localize without explaining your company again.