Clients,
regulators
and auditors
will read your content.
With us, it's
ready for all three.

In yours. We connect at the start of the collaboration, with permissions defined by you; purchase orders, deliveries and invoicing follow the process you already have in place. If you don't have a TMS, we work in ours and the data is identified as yours from day one.

You receive the dossier they want to see: the ISO certificates, the per-project records (who translated, who reviewed, with what qualifications, which version was accepted and when), the LQA reports and the log of terminology decisions.

It's written into the contract, before the first project. When we work in your TMS, the data lives in your house from the start; when we manage it, ownership and delivery format are defined at kick-off.

Never. Human translation (ISO 17100) and machine post-editing (ISO 18587) are distinct workflows, certified separately and declared in every project's report. MT runs on private engines with curated data (no public engines), and you decide which type of content may go through each workflow.

Both ways, with the same ruler: an error typology and acceptance thresholds agreed with you at kick-off, documented LQA per delivery and, in the pilot, a reviewer outside the translating team. Then shared KPIs and periodic reviews throughout the collaboration.

You hear it from us, not from your client, and in time to change the plan: reinforce the team, phase the delivery or reprioritise with you what ships first. On the other end there is always someone with a name (never a shared mailbox), with a direct line to whoever solves it, agreed at kick-off and a back-up team ready for the unexpected.

Yes: that's what the back-up team is for, in place from day one with the same glossaries and the same style guide. MTPE capacity is set up at kick-off and activates immediately, on request, without switching teams. What we never do is slip new linguists in mid-project without telling you.

On a one-off project, maybe. At scale, what you save per piece you pay in management, inconsistency and audit risk; and when a freelancer fails at 11 pm on launch eve, the problem is yours. In a collaboration with us, it's ours, and you have someone to call to fix it.

Yes to both. The NDA is signed on day one (yours or ours), the teams are bound by it, and if the programme requires your servers or a VPN, that's how we work. Always with encrypted transfers and GDPR-compliant protocols.

It depends on the service and volume, so we quote case by case, but always with the same logic: a closed price before we start. In translation, the value is set per word, with a rate table per language pair and per workflow (human or post-editing); repetitions and memory matches are discounted automatically. For the other services (multimedia, marketing, design), the quote is per project, with deliverables and deadlines in writing. Either way, the quote you approve is the invoice you receive: scope changes are quoted before we proceed, never charged afterwards.

250+ language pairs, with Portuguese in all three variants (Portugal, Brazil and Africa) as a house speciality. In every pair, native linguists from your sector, not generalists with a glossary at hand.

Kick-off is a short sequence: NDA and access, glossary and style guide preparation, a real 2,500-word pilot on your actual content with LQA by a reviewer outside the team, calibration and production. The exact timeline depends on your systems and approvals; we set it with you in the very first conversation.