Account structure
Define business units, buyers, approvers, project owners, languages, service levels and recurring workflows.
Individuals · Business · Government
Request a corporate language & events account
For organizations with recurring translation, localization, interpreting or event requirements. A corporate account can centralize departments, purchase orders, project codes, billing references, terminology, translation memories, approvals and reporting. In the Saudi edition, requests can carry SAR, Etimad/tender references, Saudi city/event details and local service or equipment requirements.
Secure intakeFiles stored outside the public web root
Procurement readyPO / Bon de Commande and cost-center fields
Multi-serviceTranslation, interpreting and events
MarketsMorocco · Saudi Arabia · Worldwide
LanguagesArabic · French · English + 100+ languages
Built around how the buyer works
Commercial controls
PO requirements, cost centers, monthly/consolidated invoicing preferences and rate-card discussions can be documented at onboarding.
Delivery governance
Agree the use of AI, confidentiality, data retention, terminology ownership, review levels and client approval points.
Send the request
Buyer checklist before approval
Before approving Request a corporate language & events account, define who owns the decision, which market and end-use apply, the required completion date, the documents or event inputs already available, the confidentiality level, and the commercial reference that should appear on the quotation. These details prevent avoidable rework and make it easier to select the right combination of professional linguists, project management, interpreting resources, event production, equipment, review and client approval.
For Request a corporate language & events account, procurement teams should also identify any purchase-order requirement, tender or RFQ reference, supplier-registration step, billing constraint, authorized requester, approver and final delivery format. Where the work is recurring, add terminology, translation-memory ownership, reporting expectations and an escalation contact. Where the service is local, confirm city, venue or delivery point; where it is remote, confirm platform, connectivity and access requirements before the formal proposal is accepted.
Ready to move forward?
Choose the route that matches how you buy: secure quote, consultation, corporate account or procurement request.