Contact

Home / Fields / Translation & language services

Translation & Language Services: Get Paid for Being Genuinely Bilingual

Businesses expanding across languages pay for text and media that reads native on the other side: documents, websites, product listings, subtitles, app strings. You are paid per word, per audio minute, or per project — for judgment, not typing.

How the money flows

Step in the chainWhat actually happens
A client has content and a marketA seller entering a new marketplace, a creator subtitling for a second audience, a company localizing its site. The content exists; the trustworthy version in language B doesn't.
You quote in the unit of the tradePer source word for documents, per minute for audio/video, per project for localization with strings, formatting and review rounds. Unit pricing makes you comparable — and professional.
Machine translation drafts, you deliver qualityClients know raw MT is cheap and risky. What they buy from you is the pass machines can't be trusted with: terminology consistency, tone, cultural landmines, numbers and names checked.
Delivery includes QA, visiblyA second pass, a glossary you maintain for the client, a short note on choices you made. Visible QA is how a translator becomes a retained vendor instead of a one-off gig.
Retainers follow productsSellers and creators publish constantly; the translator who holds their glossary and voice becomes the default for every new batch — recurring work without re-selling yourself.

Who this fits — and who it doesn't

Good fit

You write genuinely well in the target language (this is a writing job wearing a language costume), you notice register and tone, and you're meticulous with names, numbers and terminology. Domain knowledge — e-commerce, tech, legal, medical — multiplies rates, because clients pay for not having to explain their own industry to you.

Bad fit

You're 'pretty fluent' conversationally but can't write publishable prose in the target language — clients will find out in the first delivery. Also a bad fit if you plan to pass off raw machine output as your work: clients check, platforms test, and one exposed delivery ends the business.

Zero to first payment

  1. Pick your pair and direction honestly: most professionals translate INTO their strongest written language. Write that sentence at the top of your profile.
  2. Choose a first domain where you have vocabulary depth (e.g. e-commerce listings, tech docs, video subtitles) and build a personal glossary for it as you work.
  3. Produce proof: translate one public sample in your domain and present source/target side by side; subtitle one short video with timing. Buyers judge samples, not claims.
  4. Set your unit rates in writing (per word / per minute / per project) with a minimum fee — tiny jobs cost the same admin as big ones, and professionals price that in.
  5. Pitch where the content flows: cross-border sellers (see the e-commerce field), creators expanding channels, agencies that subcontract overflow. Offer a small paid sample batch, never free full work.
  6. Deliver with the QA ritual: self-review pass against a checklist (numbers, names, terms, formatting) and a shared glossary file the client keeps. Invite the next batch explicitly in the delivery note.
  7. Collect repeat clients into a light retainer or priority arrangement — in this field, the second order from the same client is worth five first orders from strangers.

Platforms & tools

Work arrives via freelance platforms (see the Freelancer playbook), localization agencies, and direct relationships with sellers and creators. CAT tools and glossaries live in your toolbox; payment runs through the same payments chain as every field here. Language skill also multiplies other fields: it's the entry ticket to remote services at better rates and the quality layer on content for a second-language channel.

Worked example (illustrative math, not an earnings promise)

Formula: A mixed week (illustrative) = words × per-word rate + minutes × per-minute rate
Assumptions, stated out loud: a 10,000-word document batch at an assumed $0.06/word → 10,000 × 0.06 = $600. Plus 60 minutes of subtitling at an assumed $3.00/minute → 60 × 3.00 = $180.
Total for the batch: 600 + 180 = $780 before platform/payment fees — priced in units the client can verify, which is why unit pricing closes deals.
Result on these assumptions: $780 on these assumptions. Note what the units do for you: the client compares a number, not your life story — and your speed improvements (glossaries, MT-draft workflows) raise your effective hourly rate without raising the client's price. Every input below is an assumption we state out loud, not a market average and not a promise. Change the inputs to your own quotes and fee pages before you rely on any of it.

Week one

How people fail at this

FAQ

Has machine translation killed this field?
It killed the bottom of it — raw conversion of low-stakes text. It expanded the top: more content gets produced in more languages, and every serious use needs a human QA layer. Position as that layer and MT becomes your draft engine, not your rival.

Per word, per minute, or per project?
Match the unit to the medium: words for documents, minutes for audio/video (timing and spotting are real work), projects for localization where strings, layout and rounds blur the units. Always with a minimum fee.

Do I need certification?
For sworn/legal work in many markets, yes — those are regulated niches with their own entry rules; check your market's requirements. For commercial content (listings, sites, subtitles), samples and reliability are the credentials clients actually check.