comparison

Per Word, Per Hour or Per Project: Picking the Right Pricing Unit

Certificates, transcreation, subtitles, post editing and DTP do not behave the same way under a per word rate. Here is which unit fits which job, and where each one quietly loses you money.

Three paper stacks of different sizes on a cream desk with a brass stopwatch and a mechanical counter
Plate. Three paper stacks of different sizes on a cream desk with a brass stopwatch and a mechanical counter.

What each unit actually measures and who carries the risk under it

Every pricing unit in translation, per word, per hour, per project, breaks the job into a different kind of task. Each unit measures a separate aspect of the work, and each puts more or less risk on the translator or the client. Understanding what these units actually mean helps both parties avoid surprises and make sure the quote matches the job.

Per word pricing treats the source or target word count as the main driver of the workload. This puts risk on the translator if the content is complex, highly formatted, or includes heavy research. The client, on the other hand, gets certainty in their budget, knowing the total cost up front as long as the word count holds steady.

Hourly rates measure only the translator's time. The translator gets paid for every minute spent, but the total cost can be unpredictable for the client. This model shifts the risk of inefficiency or unexpected difficulty onto the client, but it also means the translator gets paid for all labor, no matter what form it takes.

Project rates aim to capture the full scope of work with a single price. The translator takes on the risk of underestimating, while the client knows exactly what they will pay. This can reward experience and efficiency, but can also backfire if the job scope changes during the project.

Keep reading: What USCIS Requires on a Certified Translation of a Document

Per word: the jobs where source word count predicts effort well

Per word pricing works best when the number of words aligns closely with the actual effort required. Standard document translation is the classic example: contracts, manuals, surveys, and marketing sheets. These projects have clear, countable text, predictable formatting, and few surprises that would add extra labor.

For these jobs, both sides can agree on the word count up front. The translator knows how much work to expect, and the client can easily compare quotes. Rate cards by client or project type keep things predictable. For source languages with consistent structure, per word pricing is fair and tractable.

However, per word pricing starts to break down when the text has a lot of repetition, non-editable graphics, or terminology challenges. If the job requires heavy QA, glossary work, or post-layout review, the real effort may sneak far above what the word count suggests. Good practice is to clarify what is included in the per word rate, and to highlight any extras in the scope before starting.

Per hour: transcreation, terminology research, review of someone else's work

Transcreation and creative adaptation

Transcreation jobs, slogans, taglines, ad copy, rarely fit into per word pricing. The value comes from creativity, not volume. A single phrase can take hours to get right. Per hour billing is fair here, since the client pays for the time and expertise that go into adapting a message for a new market.

Terminology and research

When a project calls for extensive terminology research or glossary development, the hours pile up regardless of how many words appear in the finished product. Scientific, medical, and technical content often fall into this category. Here, per hour rates ensure the translator is compensated for the unseen work required to get the details right.

Revision and review

Assessing or editing another translator's work also resists per word billing. Some pages need only minor fixes, while others require full rewrites or back-and-forth with the client. In these cases, time spent is the fairest metric. Charging by the hour rewards thoroughness and protects against scope creep when the source material is inconsistent in quality.

Hourly billing requires trust. Clients may need detailed timesheets or clear descriptions of what each hour covered. It helps to agree on an estimate or a not-to-exceed cap before starting, and to update the client as the work progresses.

Keep reading: Six Quoting Mistakes on Scanned PDFs and Locked Source Files

Per project: fixed scope, fixed deadline and the change order that protects you

Some jobs are best priced as a whole project. This approach bundles all work, translation, formatting, QA, terminology, revisions, into a single fee. It makes sense when the scope is clear, deadlines are strict, and the client wants one figure for their budget.

Common examples include website launches, product manuals, or multi-file document sets with complex formatting. The translator can factor in all expected labor, including communication, project management, and handoff tasks. Per project pricing rewards efficiency and experience, letting translators use their own tools and workflows to deliver the finished product on time.

The risk: if the scope changes midstream, the translator can lose money. The safety valve is a change order, a written agreement to adjust the fee if the client adds pages, changes the brief, or requests extra rounds of revision. A clear scope and a written change order process protect both sides from surprises.

Many experienced translators include a change order clause in their contracts. This spells out what counts as a new request, how changes are priced, and how delays or additions will be handled. The key is to be explicit before the work begins.

Per runtime minute for subtitles and per page for certified vital records

Subtitling: per runtime minute

For video subtitling, the standard unit is the runtime minute. The translator is paid for each minute of finished video, not the transcript's word count. This reflects the real work: syncing dialogue, splitting lines, timing cues, and fitting translations into tight character limits. The job often includes adaptation to local conventions, which goes well beyond straight translation.

Rates per runtime minute depend on the video type, the density of speech, and the level of formatting required. News clips and interviews may have a steady pace, while documentaries or corporate videos might need more adaptation. The key is to confirm the runtime in advance and clarify what is included in the quote.

Certified translation: per page

Legal and vital records, birth certificates, diplomas, court documents, are usually billed per page. These documents have to be certified, often with a signed affidavit or notarization. Word counts can be misleading here, as formatting, seals, and handwritten notes may require extra time per page.

For these jobs, most translators charge a flat fee per page, sometimes with a premium for rush service or complex layouts. The per page unit matches the way these jobs are submitted and delivered: as scans or PDFs, not editable text files. This keeps the process simple for both client and translator.

See how WordRate handles this for translation and localization

Source count or target count, and why the direction of the language pair matters

One wrinkle in per word pricing is the question of which words to count: source or target. In some language pairs, the translation expands or contracts. English to German, for example, often produces more words in the target. The reverse is true for English to Chinese, where the target is usually shorter.

Source word count is easiest to verify before work begins, especially for editable files. It lets the client know the price up front. Target word count, however, is sometimes used for languages where the output varies widely, or where the client needs the final count for their own records.

For jobs involving non-editable formats, scanned documents, images, or handwritten notes, estimating the final word count may be the only practical option. The key is to state up front which count will be used, and to explain if the language pair is likely to expand or contract. This avoids disputes at invoicing time and builds trust with the client.

Mixed quotes: one job, three units, one invoice a client can approve

Many real-world projects mix pricing units. A single job might combine per word translation, per hour terminology research, and a per project management fee. For example, a client asks for the translation of a brochure, adaptation of a slogan, and desktop publishing for print. Each task fits a different pricing model.

The best practice is to break down the quote into separate lines: translation per word, adaptation per hour, formatting per project. This makes it clear what each task costs and avoids confusion later. Clients appreciate the transparency, and it gives them a chance to cut or add services before signing off.

When the invoice matches the quote, approval is faster. The translator can point out which units cover which pieces of the job. If the client adds work mid-project, a change order shows how the extra charge is calculated. This reduces friction and keeps the relationship professional and clear.

Tracking these mixed models is easier with a rate card system. Storing client-specific rates and applying them to each line item prevents errors and saves time when generating quotes and invoices.

How to switch an existing client from one unit to another without a fight

Changing the pricing unit for a long-term client can be delicate. Many translators find themselves stuck with per word rates for work that has shifted, transcreation, post editing, or heavy revision, but fear that changing the model will upset the client or lose the account.

The key is to explain the reason for the change in concrete terms. Show how the job's nature has evolved: more creativity, more research, more formatting, or more review. Point to past projects where the per word rate did not reflect the actual work involved. Offer a trial period for the new pricing unit, or a blended model that bridges the gap.

Whenever possible, provide a detailed breakdown of what the old rate covered and what the new unit will include. For clients used to per word, showing the time spent on recent projects in hours can help make the case for moving to an hourly or project rate. Transparency builds trust and reduces pushback.

If the client is under budget pressure, offer clear estimates and a cap on hours or project fees. This reassures them that costs will not spiral. Written terms and a clear explanation show that the change is about fairness, not just raising rates. Over time, clients who understand the logic behind the switch are more likely to accept the new unit and continue the relationship.

For translators and language service providers juggling multiple clients, rates, and units, tools that combine flexible quoting, glossary tracking, and delivery management in one place can make these transitions easier. They also reduce the chance of errors when moving between per word, per hour, and per project jobs.