Knowledge Center · 5 answers

Collaboration

Working together long term: framework agreements, dedicated teams and terminology ownership.

01How do I get started?▾

Prepare a quote request through the contact page or email the team. The current form prepares an email draft: you must send it in your mail application and attach files yourself. Website estimates are budget references, not formal quotes. We acknowledge requests within 4 hours and issue a formal quote within 24 hours.

View scope and related guidance →

02Can you support ongoing long-term translation relationships?▾

Yes. A recurring engagement can maintain approved terminology, Translation Memories and product references under agreed ownership and reuse terms. Actual cost and lead-time benefits depend on content reuse; this page does not establish an average relationship duration or automatic savings.

View scope and related guidance →

03Can I have a dedicated team for my account?▾

A recurring account can agree project management, reviewer continuity and terminology responsibilities in an MSA. Team availability and substitution arrangements should be confirmed rather than treated as a guarantee that named individuals will always be available.

View scope and related guidance →

04Do you integrate with our content management or localization systems?▾

Send your CMS, TMS, repository and transfer requirements for a feasibility assessment. Integration scope, security, testing and support are agreed separately. This page does not establish a ready-made API or connector for every platform.

View scope and related guidance →

05How do you handle version control for documents that update frequently?▾

Agree a source baseline, version identifiers and change scope. Translation Memory can support reuse, while affected references and surrounding content still need review. Translating changed segments alone is not always enough for a controlled regulatory or software release.

View scope and related guidance →

Ready to start?

Acknowledged in 4 hours, quoted in 24. Discuss confidentiality before sharing sensitive files.