01
terminology glossary
Every product noun, button label and regulated term is agreed in writing, per language, before translation begins. Typically 80–150 entries, kept as your property.
Technical translation & software localization · Savannah, GA
the localization house for software teams shipping in four languages
Spanish, Portuguese, French and German for SaaS interfaces, help centers and onboarding email — settled in a glossary, inspected in context, and reviewed again after release.
Request a fixed-price quote
Packages begin at $1,740. Prefer to talk? (804) 937-2578
Engaged by
- SaaS product teams
- Documentation leads
- Lifecycle & onboarding marketers
- Support operations
Inside every package
four instruments, one signed scope
Elvora prepares a localization the way a professional firm prepares a filing: terms are defined first, text is translated against them, the result is inspected where readers will actually meet it, and the work is reviewed once more after release.
02
in-context linguistic qa
A native linguist reads the strings inside your staging build or screenshots, checking truncation, gender agreement, plural forms and register.
03
post-launch string review
Thirty days after release we re-read what shipped, reconcile hotfix strings, and carry every correction back into the glossary.
04
four languages, eight locales
Spanish, Portuguese, French and German, with regional variants chosen by where your users actually are — not by default.
Typical engagements
three kinds of work, shown as received and as returned
Representative scopes drawn from the three surfaces we localize most. Client files stay confidential; the shape of the work does not.
The application
a billing app that reads natively in four languages
Source arrives as ICU-format JSON from a React front end. It returns with placeholders intact, plurals correct in each language, and every label matching the signed glossary.
- Typical size: 9,000–14,000 source words
- Locales: es-MX, pt-BR, fr-FR, de-DE
- Linguists read the staging build before sign-off
The help center
a help center that answers in the reader’s language
Articles are translated against the same glossary as the product, so a customer who reads “Workspace” in the app finds the same word in the answer — in every language.
- Typical size: 60–200 articles, Markdown or HTML export
- Zendesk, Intercom and Help Scout exports accepted
- Screenshot captions and alt text included
The onboarding sequence
welcome emails with the subject line intact
Subject lines are checked against mobile truncation, and variables such as the recipient’s first name are tested for gender and case before a single email is scheduled.
- Typical size: 5–9 emails per language
- Merge tags and links preserved and tested
- Preheader and subject reviewed as a pair
| Key | Locale | Returned |
|---|---|---|
welcome.subject | es-MX | Tu espacio de trabajo está listo Approved |
welcome.subject | pt-BR | Seu espaço de trabalho está pronto Approved |
welcome.subject | de-DE | Ihr Arbeitsbereich ist bereit Shortened for mobile |
How the work is priced
priced per project, settled before the first string
A term is decided once, in writing, before it appears on a single screen.
$1,740Single-language pilot
$6,230Launch set, from
$11,450Full catalogue, from
$0.19Per added source word, per language
The particulars
the details a release manager asks about first
Locales
four languages, eight regional variants
- es-MXLatin America
- es-ESSpain
- pt-BRBrazil
- pt-PTPortugal
- fr-FRFrance
- fr-CACanada
- de-DEGermany
- de-ATAustria
Variants are quoted separately; the glossary is built per variant, never shared by assumption.
Quote turnaround
1
business day to a fixed quote, after we see a sample.
File formats
JSON · XLIFF · PO · YAML · RESX · Markdown · HTML · Zendesk & Intercom exports
After release
30
days until the string review is scheduled.
placeholders stay whole
en You have {count, plural, one {# seat} other {# seats}}
es Tienes {count, plural, one {# puesto} other {# puestos}}
es Tienes {count, plural, one {# puesto} other {# puestos}}
Per-project packages
choose the scope; we return a fixed quote
Each package includes the terminology glossary, in-context linguistic QA and the post-launch string review. Invoiced per project by ACH, card or wire.
single-language pilot
$1,740One language · up to 6,000 source words
- Glossary of up to 100 terms
- In-context QA on one user flow
- String review at day 30
launch set
From $6,230Two to four languages · up to 12,000 source words
- A glossary per language and variant
- In-context QA on your staging build
- Release-day support for late strings
- String review at day 30
full catalogue
From $11,450App + help center + onboarding emails · all four languages
- One shared glossary across every surface
- Help center articles up to 150
- Email sequence of up to 9 messages
- A second string review at day 90
The studio
a quiet desk on woodcock road, open by appointment
Elvora works from Savannah, Georgia, and meets clients by call or in person on a booked schedule. Appointments are kept free of interruptions so that glossary decisions can be made properly, and recorded as they are made.
- Address3 Woodcock Road Apt 3108
Savannah, GA 31404 - HoursBy appointment — book a call
- Telephone
Elvora studio3 Woodcock Road Apt 3108, Savannah, GA 31404
Plot the route to our door
Before the first call
what to bring to the first call
A short list is enough. The more of it you have, the more exact the quote — and the sooner the glossary can begin.
- A representative sample: 300 words of UI strings or two help articles.
- Any existing glossary, style guide or list of terms that must not be translated.
- Target languages and regions, with the launch date you are working to.
- Screenshots of the tightest screens — buttons, tabs and table headers.
Commissioning a project
from first file to final string
Write to us with a sample, or telephone to arrange a call. Either way, the sequence on the right is the one every project follows.
-
01
send a sample
Paste a representative 300 words or describe the product. We reply within one business day with a fixed quote.
-
02
quote and glossary draft
You receive a fixed price and a draft glossary for approval. Nothing is translated until the terminology is signed.
-
03
translation and in-context qa
A specialist translates against the glossary; a second linguist reviews the strings inside your build or screenshots.
-
04
release and the thirty-day review
We remain available through launch. At day 30 the shipped strings are re-read and every correction is filed in your glossary.
Do you work from our repository or from exports?
Either. We accept string files directly, or exports from your help center and email platform. We do not need repository access.
What happens if a term is wrong after launch?
It is corrected during the day-30 string review at no charge, and the glossary entry is amended so the error cannot recur.
Can we add a language later?
Yes. A new language is quoted as its own pilot, built on your existing glossary structure.
How is the quote fixed if the word count changes?
The quote covers the stated scope. Words added afterwards are billed at $0.19 per source word, per language, and agreed before work begins.