Business supplies and services: Quotation software for localisation providers
Quotation software for localisation providers that prices word volume, previously translated strings and testing per language separately, so a product team sees where release costs come from.
Where quotes for localisation providers get stuck.
A software localisation quote looks simple: words times languages times rate. In practice the difference lies in what sits under those words. An update consists largely of strings translated before, some unchanged, some slightly edited. Repetitions count differently from new text. Then there is work that cannot be measured in words: checking in the screens, fixing translations that run too long and aligning terminology. Localisation providers that fold everything into one word rate lose margin on releases heavy in testing and look expensive on releases full of repetition.
Quotation software for localisation providers
Example- 1
Split volume by match type
DoneThe quote starts from an analysis of the source strings: new text, partial matches with earlier work, full matches and repetitions within the same release.
- 2
Price testing and review separately
In progressScreen testing, review by a second linguist and resolving space issues appear as their own lines per language.
- 3
Record assumptions per release
NextThe proposal names its assumptions: available context, the string freeze, the number of review rounds and how changes after freeze are handled.
From enquiry to signed quote.
Split volume by match type
The quote starts from an analysis of the source strings: new text, partial matches with earlier work, full matches and repetitions within the same release. Each category carries its own weighting, so the client sees why an update full of familiar strings costs less than the raw word count suggests.
Price testing and review separately
Screen testing, review by a second linguist and resolving space issues appear as their own lines per language. Those lines are based on the number of screens or estimated hours, not words. It stays visible that a small release with many new screens still needs testing.
Record assumptions per release
The proposal names its assumptions: available context, the string freeze, the number of review rounds and how changes after freeze are handled. The client approves per release or under a framework agreement. Strings added after approval become an addendum with the same weighting.
Alongside your calculations and price lists.
Localisation providers usually have a translation environment that produces a volume analysis per match category. The quote reads that analysis instead of retyping figures. Rates per language and category come from your own rate card, with client specific arrangements where they exist. The approved proposal feeds language team scheduling and, later, invoicing. The accounting package remains the source of final invoices.
Per release quote or framework
For a product with frequent releases, quoting each one is a lot of work on both sides. A framework agreement with fixed rates per category and monthly settlement is more efficient but requires trust in the analysis. Quoting per release still makes sense for irregular or large releases whose size varies widely.
Discount matches or not
Clients expect a discount on strings translated before, and that is reasonable. Yet a full match sometimes needs another look, for example because it now appears on a different screen. A low but non zero weighting for such strings, with an explanation of why, prevents disputes and leaves room for a quick check.
Testing included or optional
Some clients test in house with native speakers in their own organisation; others want the provider to check the screens. Making testing an optional line shows the choice clearly. If the client leaves it out, the quote records that issues in the screens after delivery are handled as a new round.
What we prepare in the quotes.
In the quoting software you read in the volume analysis from the translation environment, with weighting per match category and per language, separate lines for testing and review and recorded assumptions per release. That is how we set it up at the start. Together we recalculate an ordinary update of an existing product, and a release where a sizeable number of strings is added after approval. Framework agreements with monthly settlement and a rate list per client can be switched on later.
View pricingSupport and updatesGood to know.
Explore pricing and optionsHow do we explain why an update costs less than its word count?
By showing the analysis per match category in the quote, with each category's weighting. The client then sees how many words are new, how many were translated before and how many repeat. That makes the price explainable and shows that the translation memory genuinely pays off.
What if the client adds strings after approval?
You analyse the addition the same way and it becomes an addendum to the approved quote. The client sees the extra volume and any effect on the delivery date and approves it separately, so the original quote stays recognisable.
Can we use a different rate per language?
Yes. Rates are set per language and category on the rate card, because translator availability and complexity vary by language. The quote shows lines per language, so the client can decide to add a language later if the budget requires it.
How do we price testing without converting it to words?
Based on the number of screens or flows to check, or an estimated number of hours per language. That estimate comes from earlier releases of the same product. After a few releases you know well how long a screen takes, and the estimate tightens.
What often connects to this.
- Enquiry form for localisation providersAn enquiry form for localisation providers that gathers source strings, screen context and release details, so the language team knows where every string appears before translation starts.
- Digital job cards for localisation providersDigital job cards for localisation providers: a string package with version reference that records translation, review and screen testing per language, so every delivery traces back to a release.
- Invoicing software for localisation providersInvoicing software for localisation providers that invoices processed strings, revisions and testing per release and language, with a breakdown the client can verify and a payment link.
Quotes that match the work.
Start with a short intake. Then we schedule a call to show the software with your services, team and way of working.
WhatsAppinfo@vorlyo.com Quotation software for localisation providers: word volume, matches from earlier work and testing priced per language, with release assumptions recorded.
- Split volume by match type
- Price testing and review separately
- Record assumptions per release