Services & prices

Pick the page your users get stuck on.

Four kinds of work, each priced per project and itemized by language. Translation, native-speaker review and a read-aloud are inside every figure; you never buy them separately.

Per project · Per language · Itemized · Ps

The four engagements

What each one covers, line by line

Prices are starting figures for a typical scope, per language. Spanish, Portuguese and Haitian Creole cost the same.

Interface strings

Up to 5,000 words per release. We work from your string files, so keys, placeholders and plural rules arrive back untouched, and every line that outgrows its button is flagged with a shorter alternative.

  • Glossary written first; you keep it
  • Character-limit checks against your design file
  • Second native speaker reads the strings aloud
From $1,380per language, per release
Quote my strings

Help-center articles

Up to 25 articles per batch. Article IDs, headings and internal links stay where they are, so your search index and redirects need no re-wiring when the Spanish site goes live.

  • Zendesk, Intercom, Help Scout, Markdown or HTML
  • Link checking across the whole batch
  • One product vocabulary, applied to every article
From $2,160per language, per batch
Quote my articles

Patient instructions

Instructions for use, quick-start cards, discharge sheets and on-device prompts. A query log marks every line your regulatory team should read twice; their sign-off stays theirs.

  • Read-aloud check by a native speaker
  • Dosing and warning copy handled line by line
  • Back-translation available at $310 per document
From $640per document, per language
Quote my documents

In-context testing

A native speaker walks your build on a real device and returns annotated screenshots of every clipped, broken or odd line, with a suggested fix beside each one.

  • iOS, Android or web builds
  • Annotated screenshots, grouped by screen
  • Fixes re-checked once at no charge
$890per language, per build
Book a test pass

Why testing is its own line

Spanish runs a fifth longer than English. Your button does not.

Translation can be perfect and the screen still wrong. That is why in-context testing is priced separately and offered on every project: we would rather find the clipped label ourselves than have a patient find it for you.

Add a test pass to my quote
Tested in context · Real device · Annotated · Ps

Side by side

What goes in, what comes back

The same three passes run through every engagement. Here is where each one shows up in the work you receive.

Included in every price
EngagementYou sendYou receiveTypical turnaround
Interface strings.xcstrings, .strings, Android XML, .po, .json, XLIFFSame files, translated, with a flag list for lines that clip5–8 business days
Help-center articlesPlatform export, Markdown or HTMLArticles with IDs and links intact, plus a glossary8–12 business days
Patient instructionsInDesign, Word or PDF with sourceTranslated layouts, query log, read-aloud notes6–10 business days
In-context testingA build and a test loginAnnotated screenshots by screen, with fixes3–5 business days

Back-translation

An independent translator renders the Spanish, Portuguese or Creole back into English, for QA files that ask for it.

$310per document

Regional variant

Spain Spanish or European Portuguese in place of the defaults, at the same rate as the standard variant.

Same rateno surcharge

Rush delivery

Anything due in under five business days moves to the front of the desk.

+25%of the project fee

Before you commit

A quote you can hand to finance

Send a sample of ten strings or a whole help center. Within two business days you get one written fee, itemized by language and by step, with the word count and the assumptions behind it.

  • Projects over $2,500 start with half up front; the balance is due on delivery.
  • Changes under 10% of the word count are folded into the fee. Beyond that, we re-quote in writing first.
  • One invoice per project. No retainer, no per-seat charge.
Send a sample for a quote
A printed proof with pencil marks beside a laptop showing a string file, in black and white Fixed fee · 48 hours · In writing · Ps

On pricing

Questions about the fee

Q1Why is the price per language and not per word?

Per-word rates punish short, careful strings and reward padding. A fixed fee per release, batch or document lets us spend the time a dosing line deserves and lets you budget before we start.

Q2Is native-speaker review really included?

Yes. A translator drafts, and a different native speaker reads every line aloud and marks what sounds off. Both steps sit inside each starting price.

Q3What if my project is larger than the starting scope?

The written quote scales the fee to your actual word count and file count. You see the number before any work begins.

Q4Can you certify a translation for regulators?

No. We flag the lines your regulatory or clinical team should review, and the sign-off remains yours.

Start a project Call (617) 694-9962