An enquiry arrives that reads: "How much to translate a document?" It could be a one-page birth certificate needing certification for an official application, or a two-hundred-page technical manual into five languages with formatting to match the original. The price difference is enormous and nothing in the message distinguishes them.
Translation is one of the easiest services to quote precisely, and one of the hardest to quote from a first message.
The teardown: the missing variables
Price depends on the language pair, the word count, the subject matter, whether certification is required, the file format and the deadline. Customers usually supply none of these, because they do not know they matter.
What to ask, in order
Which language into which language, how long the document is or can they attach it, what the document is and what it will be used for, whether it needs certification or notarisation, what format they need back and when they need it.
The purpose question does the most work
Asking what the translation is for often answers three questions at once. A document for an official application needs certification. An internal summary may only need a rough translation. Marketing material needs adaptation rather than literal translation, which is a different service at a different price.
Rare languages and specialisms
Common language pairs are quoted from a standard rate. Rare pairs, or specialist fields such as legal, medical or technical, depend on translator availability. Saying so honestly prevents a quote that cannot be delivered.
Capturing it in conversation
SpideyChat for agencies asks for the language pair, length, purpose and deadline at any hour and captures the file details for a quote.
Customer: How much to translate a document? Assistant: The rates page shows the price per word for common language pairs, with certified translation priced per document. Could you tell me which language it is in now and which you need, roughly how many words or pages, what the document is for, and whether you need a certified translation?
Deadlines and rush rates
Urgency is common, particularly for official deadlines. Publishing standard turnaround by word count, and any rush rate, lets customers choose rather than ask.
Certified and official documents
Certification requirements differ by country and by receiving authority. The website should explain what the service provides and direct customers to confirm requirements with whoever is receiving the document, rather than promising it will be accepted.
Volume and ongoing work
Many translation buyers are not making a one-off purchase. They have a product catalogue, a website or a steady flow of documents. Asking whether this is a single job or the first of many changes the conversation entirely, and often the rate. Ongoing clients are worth far more than the document in front of you, and capturing that intent early is what turns a quote into a relationship.
Software and file formats
Customers often send files in formats that need extra handling, such as design files, scanned images or subtitles. Explaining which formats you accept, and which cost more to process, prevents surprises once the file arrives.
Interpreting is a different service
Interpreting enquiries need date, duration, location, languages and setting. Keeping them on a separate route avoids confusing two different businesses.
Working across markets
Agencies serving multiple languages face the same intake problem, described in multilingual enquiries for agencies working across markets, and long forms lose enquiries, as covered in the enquiry form questions that kill agency conversions.
Keeping rates accurate
An assistant quoting from outdated rates creates the problem described in when your chatbot gives a wrong price. Demand spikes matter too, as heating and cooling firms know, described in air conditioning quote requests in a heatwave.
Getting started
Publish rates per word, certification pricing, turnaround times and the details you need, then capture files at any hour. Try SpideyChat on your own site, or read about capture on the features page.