# Localize every client's product from one place

> A project per client, a glossary and tone per brand, AI drafts reviewed on the client's own screens, and a clean hand-off to Crowdin or to the developers.

- **Set up:** One project per client or brand
- **Per brand:** Glossary and style guide for each language pair
- **Hand-off:** Crowdin sync both ways, or JSON, CSV and ARB files
- **Languages:** 82
- **Price:** Free during the beta

Agencies design for many brands at once, and each brand has its own words, its own tone and its own way of shipping. Mondoword keeps each client apart in its own project, so terms and tone never leak from one brand into another.

## How it works

1. **Create a project per client.** A project holds one product's keys, its source language and its target languages. Switch between clients from the menu in the plugin.
2. **Teach the AI each brand's words.** Write the glossary and style guide for each language pair: product names that stay untranslated, terms with a fixed translation, formal or informal tone. Or let **Run style guide** draft them from the keys and translations the client already has.
3. **Link and translate in the client's file.** Select a frame, run **Auto-link**, and translate. The AI reads the screen, the nearby text and that client's glossary, never another client's.
4. **Review on the real screens.** Preview a frame in German or Japanese right on the canvas, catch overflow, and accept the drafts before the client sees them.
5. **Hand off the way the client works.** If the client's team or translators use Crowdin, connect their Crowdin project and sync both ways. Otherwise export **JSON**, **CSV** or **Flutter ARB** files for their developers.

## A prompt to start with

If you work with an AI agent, connect the Mondoword MCP connector and give it a brief per client:

```
In the Mondoword project "Acme Money":
1. Read the project guide, the glossary and the style guide.
2. Find keys in the checkout.* screens that have no German
   or French translation yet.
3. Translate them as a dry run and show me the list.
   Keep "Acme Pay" untranslated.
```

## What works today

- **Projects, glossary, style guide, Crowdin sync and export** work in the Figma plugin today.
- **Agent access is per project**: you can let an agent edit one client's project and keep another client's view-only or off.
- **Team roles are not there yet.** Today a project belongs to the person who created it. Inviting teammates and clients with a role per project comes with the web app, which we are building now.
- **No human translators and no translation memory.** If a client needs professional translators, hand off to their Crowdin project and let their vendor review there.

## FAQ

### Can one client see another client's project?

No. A project is visible only to its members, and today that is the person who created it. Glossaries and style guides are stored per project.

### Do I pay per client or per seat?

Nothing during the beta. After the beta, paid plans are priced by keys, not seats, and a free plan stays. We announce prices before anything changes.

Source: https://mondoword.com/use-cases/agencies · Updated 2026-10-29
