Guides
Why do translation agency clients leave right after onboarding?
Why translation clients leave in the first quarter: invoice surprises, unscheduled reviewers, unstated client tasks, silence, and inconsistent second projects.
What to take away
- Clients who leave in the first quarter almost never leave over quality. They leave over five specific experiences, and all five are visible in advance.
- The most common is the surprisea cost, a delay, or a task the client did not know was theirs.
- The second most common is the reviewer nobody scheduled.
- Losses in this window are unusually recoverable, because the client has not yet built a habit elsewhere.
- Ask departing clients what happened, in a way that lets them be honest, and write down the sentence they use.
The five reasons
1. A surprise on the first invoice
The quote said one thing and the invoice says another. Usually the difference is real work: file preparation nobody mentioned, an extra review round, a locale added mid-project. The work was legitimate and the surprise was not.
Five reasons clients leave
- 1Invoice surprise
- 2Late reviewer
- 3Unstated client tasks
- 4Silence
- 5Inconsistent second project
The fix is not cheaper pricing. It is a change order issued when the change happens, not an adjustment revealed at the end. A client who approves an increase in advance rarely resents it. A client who discovers one afterward remembers nothing else about the project.
2. A reviewer who appeared late
The client's colleague in the target market was never in the schedule. They read the delivered text, disagree with fifty word choices, and now everyone is arguing after the deadline. The client experiences this as a quality problem with your work, when it is a scheduling problem with their organization that you allowed to go unaddressed.
Name the reviewer per locale during intake. Give them a window. Agree what happens if the window passes.
3. Tasks the client did not know were theirs
Supplying final source. Answering queries. Approving terms. Providing character limits. Each is reasonable and none is obvious to a buyer who has not bought translation before.
A two-column responsibilities table, agreed before the first project, converts this from a grievance into an expectation.
4. Silence
No confirmation of receipt, no notice that a file was larger than expected, no warning that a deadline was at risk until it passed. Buyers tolerate a great deal of difficulty and almost no silence.
A short update at a predictable point in every project costs nothing and removes the anxiety that makes clients start looking elsewhere.
5. The second project felt different from the first
Different linguist, different terminology decisions, different tone, because the first project's decisions were never captured. To the client this reads as inconsistency, which is the failure mode they were most afraid of when they hired an agency instead of a freelancer.
Capture every reviewer preference into the glossary the day it is made.
What to check before you blame quality
| What the client said | What it usually means | What to check first |
|---|---|---|
| "The quality was not what we expected" | The reviewer changed a lot of wording | Whether preferences were captured after project one |
| "It cost more than we planned" | A change order was never issued | Whether the change was flagged when it happened |
| "It was hard to work with you" | Silence, or unbatched queries | The query log and the update cadence |
| "We are bringing it in house" | Sometimes true, often a polite exit | Ask one more question, gently |
| "The tone was wrong for our market" | Locale, not language, was never settled | Whether the market was named at intake |
The last row is worth dwelling on. A buyer who asked for Spanish and received a rendering aimed at the wrong market will describe the result as poor quality. The translation may be excellent and still wrong, because the convention, address, and register belong to a different audience. That decision belongs at intake, in writing.
Accessibility and public output, briefly
When translated material will go in front of the public, the client may have accessibility obligations that shape the deliverable. Finding that out after delivery is another way a first project ends badly.
The Department of Justice small business guide to the ADA is a starting point for the general topic in the United States and settles nothing about a particular organization or another jurisdiction. Ask at intake what the output must satisfy.
If the account involved spoken work as well as written, check whether the two were run through the same process. They should not be: the occupational profile of interpreting and translation describes them as separate professions, and an interpreting request handled on a document schedule is a distinct and avoidable failure.
How to ask a departing client what happened
Ask once, briefly, and make it easy to be honest. "We would rather know what went wrong than be told it was fine" gets a better answer than a survey.
Do not turn an exit conversation into a request for a public review. If you run a review program, apply it to everyone the same way, disclose material connections, and leave critical feedback in place; the FTC guidance for marketers on soliciting and paying for reviews sets out the practices that cause trouble.
Write down the client's own sentence, not your interpretation of it. Those sentences are the most useful diagnostic material a small agency ever collects.
The process that prevents four of these five is described in the onboarding and delivery guide. The measurement approach for catching them early is in the four onboarding symptoms and what they mean.
When the cause is linguist selection or consistency across projects, the answer is in how the bench is recruited and trained. The reputational cost of a first-quarter loss is felt in everything described in the marketing and growth guide.
Common questions
Can a client who leaves in the first quarter be won back?
Sometimes, and more often than later losses, because no habit has formed yet. Fix the specific thing, say what you fixed, and offer a small project rather than a discount.
Should I offer a refund when a first project goes badly?
Consider a credit against defined future work instead. A refund closes the relationship; a credit keeps a door open and still acknowledges the problem.
How do I tell a real quality problem from a preference dispute?
Ask for the segment, the objection, and a proposed alternative. Corrections survive that request. Preferences turn into a conversation about the glossary, which is where they belong.
Is churn in the first quarter always the agency's fault?
No. Programs get canceled and buyers move on. The point of asking is to separate those from the five reasons above, because only the five are yours to fix.
