Team works in their home language
Workstream leads, project managers, and consultants can switch UI locale per user. Same project data, presented in each user's language. No translation handoff.
Feature · Multilingual
Teams work in their home language. Stakeholders stay updated in theirs.
16-language cross-border collaboration. Same project data, every team member in their own language, every stakeholder briefed in theirs. Translation is built into the delivery surface, not a manual handoff.
16 languages · GDPR-compliant by architecture · Per-project data residency on Enterprise.
16 languages out of the box
UI, project data, meeting intelligence, voice, and deliverables.
en-USEnglish (US)en-GBEnglish (UK)deDeutschnlNederlandsfrFrançaisfr-CAFrançais (Canada)esEspañolcaCatalàitItalianoptPortuguês (Portugal)pt-BRPortuguês (Brasil)daDansknbNorsksvSvenskaplPolskicyCymraegja日本語ko한국어zh-HK繁體中文（香港）
Cross-border by design
Six capabilities that turn multilingual from a checkbox feature into a deal-execution capability.
Stakeholders briefed in theirs
Per-stakeholder briefings translated into the stakeholder's preferred language at generation time. Ground truth stays in the project's working language; the briefing localises automatically.
Deliverables in any locale
PowerPoint, PDF, Excel, and Word outputs render in the chosen output locale — for the full deck, per-slide, or per-section. Useful for cross-border decks where different stakeholders need different language versions of the same content.
Voice in your language
Voice questions work in English, German, French, Spanish, Italian, Portuguese, Dutch, Swedish, Danish, Norwegian, Polish, Japanese or Korean, and answers are read aloud. Brief the German subsidiary CFO in German and the US sponsor in English. Voice on every plan.
Cross-border meeting intelligence
Meeting transcripts auto-translated. Action items, decisions, and stakeholder commitments captured in the speaker's language and surfaced in the project's working language. No 'lost in translation' gap between English steering committee and German workstream lead.
Region-aware compliance
GDPR / UK GDPR / CCPA / region-specific data-handling variants. Data residency in the US or UK on Enterprise, or in another AWS region on request. Cross-border deal compliance tracked alongside operational integration.
Common questions
We use AWS Translate for general content, layered with a custom integration glossary so terms like 'TSA exit', 'synergy realisation', 'Day 1 cutover', 'RAID log', and 'RACI' translate to the right counterparts in each locale. Glossary expanded continuously based on deal-specific terminology.
Ground truth lives in the project's working language (set per project). Other locales render translations on demand. Edits to translated content are merged back to the working language so there's a single source of truth.
Yes. The 16-language interface is included on every plan, and so is cross-border meeting intelligence, including auto-translation of transcripts. Translation of dynamic content (briefings, transcripts, AI outputs) is fair use that grows with each project you add. Data residency in the US or UK, or in another AWS region on request, is on Enterprise.
Yes — that is the headline use case. Each user sets their own UI locale; the project data is shared. Workstream leads in Munich, London, and New York can co-author the same integration plan in their respective languages.
RTL not yet supported in the current 19-locale set. On the roadmap for an Enterprise customer-driven request, so talk to sales if this is a near-term requirement.
Brief the Munich CFO in German. Brief the New York sponsor in English. Same project.
14-day free trial. 16 languages on every plan. SOC 2 Type II observation underway · 75 patents filed.