Company reportedLive since 2025Added Oct 2026

BlaBlaCar

BlaBlaCar rebuilds its translation workflow with AI and reports around 27% lower translation costs

BlaBlaCar's localization team redesigned its translation pipeline to use AI for translation, quality checks and automation across more than 30 markets. The team says AI-assisted workflows cut translation costs by around 27% in 2025 and improved average turnaround time by 22%.

Key figures

Copied exactly from the sources. Copy any figure with its citation.

around 27%

Translation cost reduction from AI-assisted workflows in 2025, per the content team's post1

22%

Improvement in average turnaround times from AI-assisted workflows in 2025, per the content team's post1

24%

Savings on translation costs reported by the localization manager for the automated system, in a November 2025 post2

over 6 hours

Manual processing time saved per month by the localization manager, in the same post2

What it took

CostNot disclosed
TeamBuilt by one localization manager, with AI as coding partner2
TimelineAutomation built in August 2025 with dozens of prompts, refinements and tests, after earlier spreadsheet versions from Q4 20242

The problem

BlaBlaCar runs in more than 30 markets and languages. Every product change, campaign or feature update has to be translated and adapted quickly. The old process had many manual steps, coordination across tools and back-and-forth to keep quality consistent. The team wanted to scale without raising complexity, cost or turnaround time.

What they built

The localization team redesigned parts of its pipeline to use AI for translation, quality checks and automation. The content team says the new setup takes over a large part of the repetitive work, with people still deciding on quality and language.

The localization manager's own post describes the tool. It started as a Gemini call from inside a Google Sheet. It grew into a Sheet with a glossary, style guide, examples of approved translations and a second set of prompts that checked the output. In Q3 2025 it became a script connected to Phrase, the company's translation management system.

How they did it

A person uploads new content to Phrase and adds two tags: one to request AI translation and one to pick the languages. A script then collects the content and the company's glossary, style guides and examples, translates the text and runs a quality-check prompt. It writes the result back to Phrase. Linguists find the text already translated and checked, and do the final review.

The manager built the script in August 2025 with AI as a coding partner, which took dozens of prompts, refinements and tests.

Results

The content team's post says that across 2025, AI-assisted workflows brought translation costs down by around 27% and improved average turnaround times by 22%. The localization manager's November 2025 post reports 24% savings on translation costs for the automated system and over 6 hours of manual work saved each month. It reports earlier translation savings of 11% (the first spreadsheet formula) and 22% (the larger spreadsheet tool). That 22% is a cost saving at one stage of the tool, not the 22% turnaround figure.

Localization experts now spend more time orchestrating workflows, defining language standards and checking quality across markets, and less time executing translations.

What to copy

Begin with a small tool, put your glossary and style rules into the prompts, add an automated check, and keep linguists as reviewers. Report savings at each stage so the business case grows with the tool.

Lessons for your project

  1. Start small and measure each step. The localization manager began with a spreadsheet formula, reported 11% savings, and then reached 22% and 24% as the tool matured.

  2. Put your rules into the prompt. Glossary, style guide and examples of approved translations were fed to the model with every request.

  3. Add an automatic quality check. A second set of prompts checked the AI translation for common errors before humans reviewed it.

  4. Keep linguists as the final reviewers. Translations arrive in the translation system already checked, for human sign-off.

  5. Rethink the workflow, not only the tool. BlaBlaCar says it redesigned parts of the pipeline rather than adding AI on top of existing steps.

Caveats

  • Both sources are BlaBlaCar's own Medium posts. No independent outlet confirms the figures.
  • The 27% and 22% figures come from the content team's post. They are for 2025 as a whole. The post does not define the baseline or the share of content covered.
  • The 24% figure comes from the localization manager's earlier post (5 November 2025), which also says the manager expected to clear 30% in Q4. Neither post explains how savings were calculated, and the two figures are not combined.
  • Only the localization manager's post names a model: Gemini, called from a Google Sheet. The later automated script reuses the same prompts and assets, but the post does not restate the model, and no version is given.
  • No go-live month is stated for the team-wide workflow. The localization manager's tests started in Q4 2024 and the automation was built in Q3 2025, so only the year is shown.
  • Both posts were read through Medium's feed, because Medium blocked the article pages. Dates come from the feed entries.

Sources

  1. How we built an AI-Powered content strategy at BlaBlaCar

    BlaBlaCar blog (Medium) · 2026-03-19 · Company blog · medium.com

  2. A Localization Manager's AI Toolkit: From Spreadsheets to Full Automation

    BlaBlaCar blog (Medium) · 2025-11-05 · Company blog · medium.com

Summarized in our own words from the sources above. Spotted an error? See corrections.