
Home
A translation brief needs the purpose and context of the content, not just a language pair.
View the screen ↓
We built the agency presentation around parallel-language layouts and an editorial localisation record.
The visitor can see the kind of work being discussed before describing a translation requirement.
A translation brief needs the purpose and context of the content, not just a language pair.
The brief brings audience, tone and review context together. These questions establish the intended use before quotation and connect the service pages to a useful translation brief.
The typography pairs Libre Baskerville with DM Sans. The opening imagery establishes the identity, while the collection, detail and planner keep a consistent hierarchy for choices, supporting information and the next action.
The collection introduces “Editorial localisation”, “Document translation” and “Language systems”. The detail page develops “Editorial localisation”, and “Build a language brief” turns those interests into a prepared brief.

A translation brief needs the purpose and context of the content, not just a language pair.
View the screen ↓
Introduces “Editorial localisation”, “Document translation” and “Language systems”, with the information needed to decide which option to explore.
View the screen ↓
Adapt web pages, campaigns and editorial content with a clear tone reference and local reader in mind. Brief. Translation. Editorial review.
View the screen ↓
Brings selected interests together with “Content type”, preferred timing and notes. The brief can be downloaded or cleared.
View the screen ↓
Provides a focused enquiry route for the selected interests, with contact details and the context prepared in “Build a language brief”.
View the screen ↓Explore the website, from the first impression to the finer details.
Choose a view to enlarge ↓Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.