- We read
- Your en.json, .strings, .xml or .xliff export, every key
- Including the keys marked “deprecated,” until you tell us they are
- Every {variable}, so “{count} seats” doesn’t become “1 seats”
- You get back
- Translated files in your original format, keys untouched
- Truncation, plural and variable report, sorted by screen
- LQA log from the second linguist
- Glossary, up to 60 terms
- We need from you
- The export, unedited
- A staging login, or a screenshot of every screen
- A yes or no on translating your product name
- Not in this one
- Lifecycle emails
- A tone memo. We follow your English and ask once, in writing, if it’s ambiguous
- Help-center articles
Services & rates · revised October 2026
zipper & thread, itemized.
Three packages, three languages, nine prices. Each one is charged once, per language, and each one already includes a second linguist reading cold and a glossary that leaves with you. The rest of this page is the small print, printed large.
The rate card
nine prices, one grid, no asterisks hiding below it
Rows are packages. Columns are languages. Pick a cell; that is the number. Japanese runs 22% higher because it gets an extra review pass and a meeting about katakana.
| Package | Spanish | Portuguese (BR) | Japanese | Word cap | Glossary | Days · rush |
|---|---|---|---|---|---|---|
| string passProduct UI strings | $1,140 | $1,140 | $1,391 | 2,500 | 60 terms | 7 · 4 |
| onboarding flowSignup to first value + 6 emails | $2,680 | $2,680 | $3,270 | 6,000 | 150 terms | 10 · 5 |
| help-center moveUp to 40 articles + macros | $6,350 | $6,350 | $7,747 | 24,000 | 300 terms | 15 · 8 |
- Over the cap
- $0.21 per word for Spanish and Portuguese, $0.29 for Japanese. Counted by our tool and yours; the lower count wins.
- Rush
- Half the business days, rounded up, for +30%. Booked only if both linguists are free that week.
- Invoicing
- USD, per project. 50% to start, 50% the day the glossary lands. ACH, wire or card.
Not sure which row your file belongs in? Send it. We’ll name the row, and the cheaper one if it fits.
Email the exportPackage specs
what each package reads, returns, and leaves out
Four headings per package, the same four every time, so you can compare them without a call. The “not in this one” column is there because somebody always asks.
- We read
- Signup, verification and welcome screens
- Tooltips, checklists, empty states, the confetti modal
- Six lifecycle emails, with subject lines and preheaders
- You get back
- Everything the string pass returns
- A one-page tone memo per language: tú or usted, você, です・ます — with examples lifted from your own copy
- Screenshot LQA on every onboarding screen
- Glossary, up to 150 terms
- We need from you
- A test signup path that doesn’t need a real credit card, or one we can cancel
- Email templates as HTML, or an export from Customer.io, Braze or Iterable
- Twenty minutes with whoever wrote the English
- Not in this one
- The pricing page. Currency and tax wording get their own conversation, and their own string pass
- Email number seven onward (add-on, $95 each)
- We read
- Up to 40 articles in Zendesk, Intercom or Help Scout
- Macros and canned replies your support team actually uses
- Your top 50 help-center search queries from the last 90 days
- You get back
- Articles re-imported as drafts, ready to publish
- Internal links pointing to the localized article, not the English one
- Screenshot captions rewritten per locale
- Search keywords researched per market
- Glossary, up to 300 terms
- We need from you
- An editor seat on the help center
- The list of articles you’re about to retire, so we don’t localize them first
- Not in this one
- Re-capturing screenshots in the localized UI (add-on, $18 per screenshot)
- Community forum threads
An onboarding flow, one language
ten business days, drawn to scale
Day 1 is the business day after the deposit lands. Striped bars are yours; we can’t shorten those, only remind you about them.
Timeline of a ten-business-day onboarding flow: day 1 stranger signup; days 2–3 you approve the tone memo; days 2–6 the first linguist drafts; days 6–8 the second linguist reviews cold; days 8–9 in-context check on staging; day 9 your team reads it; day 10 fixes and glossary handoff.
We sign up as a strangerDay 1
You approve the tone memoDays 2–3
Linguist A drafts app + emailsDays 2–6
Linguist B reads it coldDays 6–8
In-context check on stagingDays 8–9
Your team’s read-throughDay 9
Fixes, glossary, invoice twoDay 10
- fridays countWe close at 2pm on Fridays. It still counts as a business day, because the linguists don’t.
- your bars can move oursIf the tone memo sits unapproved past Day 3, Linguist A keeps drafting in the register we proposed. Changing it later is a find-and-replace on paper and a rewrite in practice.
- two languages, same ten daysSpanish and Japanese run in parallel with separate linguists. The Japanese track adds one review pass inside the same window.
- help-center moves run fifteenSame shape, longer bars, plus two days for re-importing drafts and checking every internal link resolves.
Three desks · three style sheets
each language gets its own desk, and its own checklist
Every package in every language is checked against the list on its card. These are the defaults we start from; your tone memo or glossary can overrule any of them, in writing.
spanish
ES-419 · ES-MX · ES-ESEmpezar
“Get started,” at 96px
- Register
- Tú, unless your English is formal
- Dates
- 3 nov 2026 · DD/MM
- Numbers
- 1.234,56 in Spain · 1,234.56 in Mexico
Checked every time
- Opening ¿ and ¡ on every string that asks or exclaims
- “Bienvenido” rewritten as “Te damos la bienvenida,” so {firstName} needs no gender
- One variant per project; vosotros never wanders into a Latin American file
Priced at the base rate.
portuguese
PT-BRComeçar
Same button, 7 characters
- Register
- Você, everywhere. Tu on request, for Porto Alegre
- Dates
- 03/11/2026 · DD/MM
- Currency
- R$ 1.234,56, with the space
Checked every time
- “Fazer login,” never “logar,” however often your Brazilian support team says it
- Gendered greetings restructured: “Que bom ter você aqui”
- CPF and CNPJ labels on any billing field that touches Brazil
Priced at the base rate.
japanese
JA-JP始める
Three characters, still wider than you’d think
- Register
- です・ます by default
- Dates
- 2026年11月3日
- Currency
- ¥1,234 — no decimals, ever
Checked every time
- No italics; Japanese fonts don’t have them. Emphasis goes in 「」 or bold
- No 。 or 、 at the start of a line
- サーバー or サーバ: chosen once, logged, never mixed
- Family name first; emails open with {lastName} 様
+22%: a second review pass, and the katakana meeting.
À la carte
add-ons, for files that don’t fit a row
Each one attaches to a package or stands alone, and shows up as its own line on the quote. Japanese is +22% unless the line says otherwise.
-
second spanish variant
from $640Spain after Latin America, or the reverse. An adaptation pass — vosotros, ordenador, móvil — on top of the first variant, not a second translation, so not a second full price.
Add to a quote -
app store + google play listing
$385Per language. Title, subtitle, promotional text, full description, and the 100-character keyword field, researched per store rather than translated from yours.
Add to a quote -
lifecycle email, number seven onward
$95 eachBeyond the six in an onboarding flow. Subject line and preheader included; the subject line usually takes longer than the body.
Add to a quote -
screenshot recapture
$18 eachWe capture the localized screen from your staging build at your help center’s exact dimensions, so the Japanese article stops showing an English sidebar.
Add to a quote -
release top-up
$0.21/wordNew and changed strings between releases, checked against the glossary we already built. $180 minimum per release; $0.29 a word for Japanese. Back in 3 business days.
Send the diff -
lqa audit of an existing translation
$0.07/wordSomeone else translated it; one of ours reads it cold and logs every line that sounds translated. $520 minimum. We don’t rewrite unless you ask, and then it becomes a package.
Request an audit -
glossary from what you already shipped
$1,150Per language. We mine your live translations, flag the three different words you currently use for “workspace,” and hand back a termbase you can import on Monday.
Add to a quote
Off the menu
four requests we turn down by return email
Saying no in the first reply saves you the two business days a quote would take. These are the ones that come up most.
terms of service & privacy policies
Legal text needs a legal translator. Your onboarding can say “Hola, Marta.” Your liability clause shouldn’t.
Instead: a certified legal translator. We’ll still add the defined terms to your glossary.
french, german, korean, italian
Three languages is the whole list. A fourth would make the glossaries for the first three worse.
Instead: we’ll share our termbase format so your next vendor starts from the same columns.
voice-over and dubbing
We write subtitles for product-tour videos. Someone with a booth and a microphone should handle the rest.
Instead: localized .srt files, timed to your cut.
machine output, post-edited at $0.04 a word
At that rate, nobody gets to read it cold. That is the one step we won’t take out.
Instead: an LQA audit, if the machine output is already live.