How to quote a document translation job in under 15 minutes
How to quote a translation job in under 15 minutes: the questions to ask, an honest word count, and a rate card that does the arithmetic for you.
A client who asks you for a quote is usually asking two other translators the same thing on the same morning. That is the part most of us forget while we sit there working out a number. The first clear, defensible quote in the inbox often ends the search, even when a cheaper one turns up two days later. So the real problem is not how to quote a translation job perfectly. It is how to quote one fast enough to still be in the conversation, without committing to a figure you will resent in week three. Fifteen minutes is enough for most document jobs. It is only enough if the thinking happened before the request arrived.
Why speed matters more than precision when you quote a translation job
We see a lot of inbound requests, ours and our users'. The pattern is consistent: most clients stop comparing once they have one quote they actually understand. Two days of silence reads as busy, or not interested, and by the time your careful number lands the job has a name on it.
This is not an argument for guessing. Speed without a method is how a freelancer ends up translating 18,000 words for a 9,000-word fee. The speed comes from having made the pricing decisions earlier, on an afternoon when no client was waiting, so that the quote itself is lookup and arithmetic.
There is a second reason to be fast that has nothing to do with the race. A quote is the first working sample the client gets of how you run a project. One that arrives the same day, names a delivery date, and says exactly what they will receive tells them more about your reliability than your CV does. Translators who are slow to quote and excellent at the work still lose to this.
We should be honest that this advice sits badly with careful people, and some of the best translators we know are careful people. Sending a number within the hour feels like the opposite of professional diligence. The resolution we have landed on is that the diligence moves earlier: into the rate card, into the questions you ask by reflex, into the analysis you run before you think about the price. None of it happens while the client waits.
Two situations where the clock does not matter. Procurement tenders with a submission deadline and a scoring matrix, where nobody is reading in order of arrival and a carelessly filled form loses on its own merits. And agency vendor onboarding, which is a rate sheet rather than a quote. A third case is worth naming separately: the three-line request with no file, no company name and no deadline, which is usually somebody collecting numbers to wave at a cheaper supplier. That one gets a polite set of questions, not fifteen minutes of work.
Ask for the file, not a description of the file
A client once described a job to us as a short deck, maybe twenty slides, for an internal training session. The file was thirty-eight slides with 9,400 words sitting in the speaker notes, which is where the actual training content lived. A quote built on the description would have been off by more than half, and the person who wrote it would have had to either eat the difference or go back and renegotiate, which is worse.
The other common gap is a PDF exported from a Word file the client still has on their drive. Asking whether the editable original exists takes one sentence and can remove two hours of layout rebuilding from the job.
So the first reply does two things at once. It asks for the file, and it asks three questions: what the translation is for, what format they want back, and when they need it. The purpose is the one people skip, and it decides the service level. Internal reading, a published brochure and a document going to a government authority are three different jobs at three different prices, and without knowing which one it is you cannot tell whether you are quoting post-editing or full translation with your own revision pass.
Put all of it in one message. Each round trip costs a day, and the day is the thing you are trying to protect.
Sometimes an NDA blocks the file until there is an engagement. Then quote a range and write the assumptions it rests on in one line: editable DOCX, no scanned pages, under 15,000 words, no layout work. Say plainly that the figure firms up when you see the file. A range with stated assumptions is honest. A single number from a verbal description is a bet you are making against yourself.
Separate the word count from the billable count
The number in Word's status bar is not a billable count. Depending on how the counter is set it may leave out text boxes, footnotes and endnotes, and it tells you nothing about tracked changes still sitting in the file or comments the client assumes are included. XLSX workbook translation has a worse version of this problem: the visible sheets are often not the whole job, because dropdown values live on a hidden sheet and nobody mentions them. In PPTX presentation translation, whatever counter the client used almost certainly skipped the speaker notes.
The honest count comes from running the file through a CAT tool analysis. It gives you segments, repetition inside the file, and matches against the translation memory you keep for that client. Those are the numbers you quote from, and the ones you can show if the figure is questioned.
A maintenance manual we looked at recently came in at 12,000 words by the status bar. The analysis put it at 15,800, of which 2,900 repeated across the warning tables and another 1,100 matched a manual translated for the same client in the spring. Three numbers, three defensible quotes, and only one of them is fair to both sides.
The analysis takes a couple of minutes, which is why it fits inside the fifteen rather than competing with them. Start it and look at the file while it runs. Where this breaks down is a scanned PDF, because there is nothing to analyse until the text exists. There the count is genuinely an estimate: count three representative pages, multiply, and write on the quote that the final figure follows the extracted text.
Price from a rate card you built on a quiet afternoon
Fifteen minutes only works because the hard thinking is already done and written down. The card lists, per language pair, what you charge for full translation with your own revision, for post-editing AI output at the level you are willing to deliver, and for a light pass over output meant only for internal gisting. Under that sits your minimum charge, your hourly rate for preparation and layout work, and the rush surcharge you will actually honour rather than the one you quote and then feel bad about. With that page open, a quote is a lookup and a multiplication.
If your rates still assume a human-only workflow and you have started using AI in the middle of your process, the pricing question is a different one and worth settling before the next request arrives. We wrote about pricing when AI is part of your workflow separately, because it does not fit inside a fifteen-minute decision.
The card covers the jobs you recognise. Keep a fourth bucket for the ones you do not: an unfamiliar domain, certified work, a file format you have never handled. Those get quoted by the hour or turned down, and spotting them in the first two minutes is part of the method rather than a failure of it.
The minimum charge is the line people leave off, and it is the one that protects the fifteen minutes. A 200-word certificate priced per word pays for about a third of the email exchange it generates. Set the floor at something like an hour of your time and apply it without apologising for it; clients who send small documents regularly are usually the ones who understand this best, because they pay minimum charges everywhere else too.
Cards drift. We have seen freelancers quoting 2024 numbers well into 2026 because the spreadsheet was never reopened. Put the date on it and look at it twice a year.
Turn the file's condition into a line on the quote, not a silent loss
Preparation is where freelance margin quietly disappears. A DOCX produced by converting a PDF carries a manual line break at the end of every visual line, which segments badly and has to be cleaned before anything useful can happen. Tables drawn with tab characters. Images with text baked into them that somebody expects translated. Two-column layouts that reflow once the target language runs twenty per cent longer than the source.
Two minutes of actually looking at the file tells you which of these you are buying. Then price it as a named line: source preparation and post-translation layout check, two hours. The client can see it, ask about it, or make it go away by sending a better file. All three outcomes are better than absorbing it.
One case we think about often: a thirty-page DOCX that had been round-tripped through PDF needed ninety minutes of cleanup before translation could start. Buried in a per-word rate, that cleanup turned a reasonable job into an effective hourly rate the translator would have refused outright if anyone had said it out loud.
None of this holds for small jobs. For a two-page certificate, itemising preparation is noise, and the minimum charge is there precisely so you do not have to. Our rough threshold is fifteen per cent: when preparation looks like more than about fifteen per cent of the work, it gets its own line.
Say what you are not doing, too. If the client wants the original InDesign layout rebuilt around the translation, that is desktop publishing with a translation inside it, and it is priced as such or declined.
Write the quote around the three questions the client actually has
Price, date, and what arrives. Everything else on a quote is optional decoration.
What arrives deserves more words than most quotes give it. Name the format: a translated DOCX, or a translated DOCX plus a bilingual XLSX if they want the content in their own CAT tool later. Name who checked it. Writing "translated and revised by me" beats silence, and it is how your price stops looking arbitrary next to an agency quote that includes a second linguist.
The date should be one you can hold against what is already booked, which means knowing your own throughput rather than a number from a forum. If you have never measured it, realistic daily output figures are a better starting point than optimism. Then write the date as five working days from your go-ahead rather than a calendar date that silently expires while the client waits for internal approval.
Scope is one sentence: one round of revisions, and what a revision is. Corrections to terminology and genuine errors, not retranslation because the source document changed. That sentence prevents most of the awkward conversations that happen in week three.
Add a validity period, seven days is normal, so nobody comes back in March expecting January's price. Keep all of it in the body of the email. Five short lines that can be read on a phone beat an attached PDF proposal for any routine job.
If the quote prices an AI-assisted step, you also need to know the file will survive it. SnapIntel takes DOCX, XLSX and PPTX files, prepares a domain analysis, glossary and translation prompt that you review and approve before translation starts, and returns the translated file with a QA report and a quality rating. It also produces a neutral source and target XLSX export, so the content stays usable if it later needs to go into a translation memory or in front of a reviewer. The trial covers 5,000 words over seven days with no card, which is usually enough to learn what a typical client file costs you in post-editing time before you put a number on it.
The fifteen minutes, and when to ignore them
Two minutes reading the request and confirming you have the real file. Three minutes on the count, with the CAT analysis running while you do the next step. Two minutes looking at the file's condition. Two minutes in the rate card. Five minutes writing the email and sending it. One minute logging what you quoted, which you will want in six months when the same client asks for the same kind of job.
That last minute earns its place. A one-line log of what you quoted, for which file size and which service level, becomes the thing you check the next time the same client writes, and it stops you from quietly undercutting your own past self. It also shows you, after thirty or forty entries, which kinds of job you win and at what price, which is the only pricing research that is actually about your clients rather than the market in general.
Some requests should break the fifteen minutes on purpose. Multi-language packages where you are coordinating other translators. Certified or sworn translation with legalisation steps attached. Procurement portals with their own forms. Any client whose last project ended in an argument about scope. Those deserve an hour of thought, and a few of them deserve a no.
If you do one thing this week, build the card: current per-word rates by pair and service level, minimum charge, hourly preparation rate, rush multiplier, all on one page you can read in thirty seconds. Then save three quote templates with the price, date and deliverable lines left blank. After that, track your own median response time for a month. That number explains more about why jobs land or do not land than your rate does.