Proje vitrini hazırlanıyorPreparing project showcaseПодготавливаем витрину проекта

Industries

CRM for translation agencies: projects, deadlines, corporate clients

How translation agencies can track quotes, deadlines and corporate clients in one place — without missing a delivery date.

Rocketly · 2026-07-30

By nine in the morning, a translation agency owner is juggling three jobs at once: a law firm's contract due by early afternoon, a diploma translation for a family relocating abroad, and a quote request for a manual needing six languages. Which one arrived on WhatsApp, which is sitting in email, whose deadline is actually today — keeping that straight is a job in itself. A properly set up translation agency CRM exists to solve exactly this: quotes, deadlines and corporate client relationships in one screen.

This piece looks at where the daily workflow of a translation agency tends to break, how to bring order to the quote-to-delivery process, and how to grow the recurring corporate accounts that actually pay the bills.

Why a translation job is never just a to-do line

From the outside, translation looks simple: text comes in, gets translated, goes out. In practice every job sits at the intersection of several variables — source and target language, word or page count, service type (standard, certified, proofreading, transcription) and a deadline. The same client can send three jobs in one week, each at a different urgency.

A spreadsheet can carry that complexity for a while, but not indefinitely — three months on, which translator handled a client's last job tends to live only in someone's memory. Picture a two-person certified-translation office: one partner translates, the other answers the phone, books notary appointments and chases files. What that office needs is not a heavyweight platform, just a simple view showing where every job currently stands.

Whoever quotes fastest often wins the job

A corporate client — a manufacturer, an e-commerce company, a law firm — rarely contacts just one agency. The same request usually goes to three or four at once, and the work goes to whoever replies first with a sensible quote. Speed matters almost as much as quality.

In a CRM, every quote request becomes a record: who asked, which language pair, roughly how many words, and the requested deadline. With per-word pricing already defined, a quote can go out within minutes, straight from WhatsApp or email.

The flow below shows the practical path a request takes from the quote inbox to delivery:

1Request in2Quote sent3Approved, in translation4Delivered
How a translation job moves from the quote inbox to delivery

Each step carries a date and an owner. Once a job moves to “approved,” the deadline drops onto the calendar automatically — no one has to recall what was promised.

The deadline is never negotiable

A visa appointment, a tender deadline, a court hearing — a late translation delays something else in the client's life. That is why a deadline in a CRM should not be a note; it should be a field that triggers a reminder.

What works in practice is a simple pipeline: every project moves through stages — quoted, approved, in translation, proofreading, ready, delivered — with time in each stage visible. A reminder firing a day before the deadline removes “I forgot” as an option.

  • Urgent jobs need their own flag: a same-day job should sit at the top of the list, not buried among routine work.
  • Multilingual projects need a line per language: if a manual's English, German and Russian versions go to three translators, each deserves its own tracked line.
  • Delay risk should surface early: if a translator has not started two days before the deadline, there is time to warn the client.

The discipline involved is close to what law firms apply to client and deadline tracking — there, too, a missed date is not an acceptable outcome.

Do not manage corporate and individual clients the same way

A student's diploma translation and a law firm's fifteen contracts a month are not the same kind of work: one is a single transaction, the other a recurring relationship. Seeing both in the same list is not enough — they need different tags and different expectations.

For corporate accounts, what matters is the pattern: how many jobs came in last month, the payment term, which translator or glossary they are used to. That belongs on the client record, not in one employee's head — because that employee eventually takes a day off, and the client should never notice.

Much like accounting firms tracking retained clients, a translation agency should watch corporate accounts by how much came in this month and when the contract renews. Individual clients need a different priority: speed and clarity — clear price, deadline, payment method, job closed.

Certified translation and notarization: one extra step, not a footnote

Certified translation carries a layer plain translation does not: a sworn translator's signature, often notarization, sometimes an apostille. Each step means another wait — and clients just want to know when it will be ready.

It helps to define an extra sub-stage for these jobs: “at the notary,” “back from the notary, ready for pickup.” That way the date given to the client is realistic — not “tomorrow,” but “Thursday, including notarization.”

It is a similar dynamic to what architecture firms face at the project approval stage: the work finishes, but an official sign-off step remains, and if it is not on the calendar, the delivery date is wrong.

It should not matter whether the request came by WhatsApp or email

Work reaches a translation agency through at least four channels: WhatsApp, email, a website form, sometimes a phone call. Checking each one separately wastes time and lets requests slip through unanswered. A faster-replying competitor simply takes the job.

Pulling every channel into one inbox removes that risk. The diagram below shows how scattered channels connect to a single hub:

SharedinboxWhatsAppEmailWebsite formPhone
Requests from different channels land in one shared inbox

That merge is not just convenience — it is continuity. If a client messages on WhatsApp first and then emails the file, both show up under the same record. Nobody has to ask who read which message.

Run your translation projects from one screen

Rocketly brings quotes, deadlines and corporate client tracking into a single place

Try it free

Which language pair, which client actually pays off?

At year-end, most agency owners think: we worked hard, but where did it all go. The answer usually sits in the CRM's history: which language pair brings in the most work, which client pays most reliably, which job type eats the most time for the least return.

That view can surface uncomfortable facts — a rare language pair's one-off jobs might sit right at the break-even line, or a corporate client might always pay late. Once visible, pricing or priority can shift.

It is the same logic catering businesses apply when assessing repeat corporate clients: figuring out which account is genuinely profitable versus which one just creates busywork is hard without the data in front of you.

What a CRM will not do

Worth being honest here: a CRM does not translate, does not enforce terminology consistency, and does not replace a CAT tool like Trados or memoQ. Managing a freelance translator pool, translation memory, quality checks — those belong to other tools.

To be honest, not every translation agency needs a full CRM system — but every agency that trusts memory to track deadlines eventually forgets one.

For a small, single-language agency with irregular work, a full CRM can be more than needed; a shared spreadsheet might do fine. But once volume grows and clients diversify, the answer to where a job stands needs to move from memory into a system — that is where a CRM earns its keep.

Interior design studios hit a similar threshold: tracking client approvals and materials across projects stops working from memory once more than one project runs at a time. The threshold is the same for a translation agency — as regular accounts grow, informal tracking slows things down first, then starts costing jobs.

Frequently asked questions

Does a one- or two-person translation agency actually need a CRM?

If there are no regular corporate accounts and job volume is low, a spreadsheet can be enough. Once three or four corporate clients send regular work, keeping deadlines and quote history in one place starts saving real time.

Does a CRM replace a CAT tool like Trados or memoQ?

No. A CRM handles clients, quotes and deadlines; translation memory and terminology are a CAT tool's job. The two complement each other rather than replace one another.

How is the certified translation and notary process tracked in a CRM?

By adding intermediate stages to a project, such as “at the notary” or “awaiting apostille.” That way the delivery date quoted to the client already accounts for the extra time.

Does merging WhatsApp, email and web-form requests into one inbox really make a difference?

Yes, especially in a business where responding first wins the job. Scattered channels carry a real risk of missed messages and slow replies.

At what point does a CRM start to matter for a translation agency?

It is less about the number of languages and more about job variety and corporate accounts. An agency working in two or three languages with many regular corporate clients gets far more value from a CRM than one juggling many languages but scattered, one-off jobs.

Running a translation agency means juggling several projects at once: different languages, different deadlines, different client expectations. Managing that from memory or scattered spreadsheets eventually teaches a business to survive the day rather than grow. A CRM like Rocketly brings quotes, deadlines and corporate client history into one screen, so the juggling gets a little more manageable — leaving more time for the actual translation work.