When we built PitchFlow, the most important decision we made was refusing to treat language support as a feature to add later. Multilingual generation is not a translation layer sitting on top of an English product. It is a fundamentally different engineering and editorial challenge — and getting it wrong insults the very users you are trying to help.
The language barrier in global freelancing
English is the dominant language of online freelancing. The biggest platforms — Upwork, Fiverr, Freelancer.com — operate primarily in English, and the majority of high-paying clients post jobs in English. This creates a structural disadvantage for the vast majority of the world's freelancers.
A software developer in Casablanca who is fluent in Arabic and French, technically excellent, and charging fair rates, is competing against freelancers for whom writing professional English is effortless. That disadvantage has nothing to do with their ability to do the job. It has everything to do with presentation.
PitchFlow's language support exists to remove that specific disadvantage. Not to help people avoid learning English — but to ensure that while they are building that skill, or in cases where they are pitching to clients in their own language, they can present their work at the level it deserves.
Translation vs. localisation: why the difference matters
The standard approach to multilingual AI is to generate in English and translate. We do not do this. The reason is simple: translated proposals do not sound like proposals written by a native speaker. They sound like translated proposals — and that is a tell that undermines the entire purpose.
Localisation means generating the proposal natively in the target language, accounting for the cultural norms around professional communication in that language. This is a different problem from translation, and it is the harder problem.
Arabic: right-to-left and cultural directness
Arabic was one of the most technically demanding languages to support correctly. Beyond the right-to-left text rendering — which requires specific HTML attributes and CSS direction rules — Arabic professional communication has its own conventions around formality, relationship-building language, and how expertise is expressed.
In Arabic business communication, a proposal that is too transactional or abrupt can read as disrespectful. The appropriate level of relational language before getting to specifics is higher than in English. PitchFlow accounts for this in how it structures Arabic proposals — they follow a slightly different arc than English ones, not because the AI does not know how to be direct, but because the cultural expectation is different.
Arabic users
When you select Arabic in PitchFlow, the output text automatically renders right-to-left in the proposal preview and copy interface. The copy button captures the text with correct Unicode directionality, so it pastes correctly into Upwork and similar platforms.
Swahili and the East African freelance market
Swahili is spoken by over 200 million people across Kenya, Tanzania, Uganda, Rwanda, and parts of the Democratic Republic of Congo. The East African tech and freelance sector is growing rapidly, with strong concentrations of talent in Nairobi, Dar es Salaam, and Kampala.
Swahili support in PitchFlow is primarily used for two purposes: generating proposals for regional clients and platforms where Swahili is the preferred language, and giving freelancers a starting draft they can personalise in their strongest language before translating to English for international submissions.
Spanish, French, Portuguese, Italian: the Romance language cluster
The four Romance languages we support cover an enormous portion of the global freelance market: Spain and Latin America (Spanish), France and Francophone Africa (French), Brazil and Portugal (Portuguese), and Italy (Italian). Despite the structural similarities between these languages, professional communication norms differ significantly.
Brazilian Portuguese proposals tend to be warmer and more relational than European Portuguese. French proposals in a business context are often more formal than Spanish equivalents. Italian business communication varies significantly between northern and southern regions. PitchFlow accounts for these regional variations based on the user's profile settings.
German: where directness is a feature, not a bug
German business communication is notably more direct than English — particularly American English. What reads as blunt in an English proposal reads as refreshingly clear and trustworthy in German. PitchFlow's German output is structured accordingly: shorter, more factual, and with less of the softening language that English proposals typically use.
What is coming next
We are actively working on adding Dutch, Polish, Turkish, and Hindi to PitchFlow's language roster. We prioritise languages based on the density of freelance activity in those markets and direct requests from our users.