The 30-Day Salvage Test Before You Fire a Client
I have fired exactly three clients, and I got the first one wrong: I fired them by email on a Friday afternoon, mid-project, with a long message explaining everything they'd done wrong. They replied with a longer message, told two mutual contacts their version, and the final invoice took two months.
The other two exits were boring. Boring is the goal — and the difference was a test I ran before sending anything.
The test: one direct conversation, 30 days, in writing
Firing is the last step, not the first one. Before you end anything, ask yourself: have I had a single direct, written conversation naming the exact behavior — late payment, scope creep, tone — and given it 30 days to change?
If not, have it first, even when you're sure it won't work. Many "impossible" clients were never told plainly what had to change. We've had it in our heads six times; the client hasn't heard any of them.
The written part matters as much as the direct part: a written warning either fixes the relationship or becomes the paper trail that justifies ending it.
What counts as a pattern rather than a bad week? Chronic late payment after a deposit, clear terms, and reminders are already in place. Scope creep that continues after you've directly said "that's outside the agreed scope." Communication that stays rude after being addressed. One incident is a bad day; the same behavior after a direct conversation is a pattern. Late payment is common rather than personal: an analysis of three years of invoicing data across more than 100,000 freelancers found 29% of invoices were paid at least a day late.
Run the money math at the same time
While the 30 days run, do the arithmetic most freelancers avoid. Take 90 days of revenue from the client and divide it by all the hours they actually cost — unbilled overhead, message threads, unscoped revisions, and the dread of seeing their name on your phone. Then compare that effective hourly rate to your standard rate.
A plain example. Say a client paid you $3,000 over 90 days but consumed 60 hours all-in. That's $50 an hour effective. If your standard rate is $80, you're not firing a good client over a bad week — you're ending a client whose real price is below what you charge everyone else. If the effective rate is close to your standard rate, the problem might be a boundary or process fix, not an exit.
When firing is actually right
After the conversation and the math, the verdict is usually obvious. Fire when the pattern survived a direct warning, the rate conversation can't close the gap, and the relationship is costing you more than hours — it's costing you energy that shows up in every other client relationship.
One exception: abuse, threats, or boundary violations that continue after direct warnings don't get the gentle version or the full 30 days. Those get a short, firm, closed-to-negotiation ending, by email, with no referral to a colleague. If the situation involves harassment, safety concerns, or legal threats, talk to a lawyer first.
Timing matters too: fire after a successful delivery, not mid-deliverable, or you hand the client a legitimate grievance they didn't have before.
The script outline (not a script to copy-paste)
I'm deliberately not giving you a word-for-word script — a copied script reads like one, and this message needs to sound like you on a calm day. Here's the structure, in four moves:
- The fact, first. One plain sentence: you're wrapping up the working relationship, effective on a specific date. No throat-clearing, no apology tour.
- What finishes. Name the specific remaining deliverable and its date — or the clean handoff point. This sentence prevents most disputes.
- The handoff offer. One line offering a smooth handoff to whoever takes the work forward. Short, genuine, bounded.
- A brief thanks, then stop. Thank them for the work done together, and end the message. No list of grievances, no defense of every decision, no invitation to negotiate staying.
That shape — fact, finish line, handoff, thanks — is what makes an exit boring in the good way. A few logistics seal it: give real notice, 30 days for ongoing work or whatever your contract specifies, and read the termination clause before you send anything — notice period, deliverables owed, payment terms, kill fee if there is one. During the notice period, hold the end date and the agreed deliverables; a client who knows you're leaving will try to cram unfinished work into the remaining days. And fire by email, not chat apps — the written record is the whole point.
The honest caveat
Firing a client who represents a large share of your income hurts before it helps. Have a month of runway, or a replacement in the pipeline, before you send the email — not after. Never let one client become all of your income.
So: one direct written conversation, 30 days, the 90-day rate math, then decide. If the pattern survived and the math doesn't close, end it cleanly, after a delivery, with notice and a handoff.
For the contract checklist, pushback replies, transition traps, and inquiry-stage red flags, the full guide to ending a client relationship cleanly covers it end to end. Read it before you send anything you can't unsend.
Top comments (1)
The 90-day effective rate math is the part I wish I'd started doing years earlier. One thing I'd add: start logging the unbilled stuff before you even suspect a problem. The first time I tried that math on a client, I had to rebuild it from memory and old chat threads, and I lowballed it badly, because the "quick" asks never feel like hours in the moment.
Now every out-of-scope ask goes on a running list with a date and a rough time, even when I end up doing it for free. Two things happen. The direct conversation gets a lot easier, because "here are the extra requests since March, with dates" lands very differently than "you keep adding things." And sometimes the list shows the problem is partly mine, like a vague spec I wrote, which is a process fix and not an exit.
Also +1 on firing after a delivery. If you can, get that last invoice sent (ideally paid) before the notice goes out. Once a client knows you're leaving, that invoice has a way of sliding to the bottom of their pile.
How often does the 30-day conversation actually save the client for you, versus just building the paper trail?