When to Fire a Client — The Four Signals, and Why Revenue Is Never One of Them

The founder who fires clients on revenue is the founder who keeps the wrong ones and loses the right ones.

I mean that literally. If the only criterion is “which account is smallest this quarter?”, the account you cut is often the one whose team is easy to work with, whose scope is clean, whose feedback is useful, and whose fee is smaller because they run a smaller operation. The account you keep is the largest one, which is almost never coincidentally the one that has taught your team to answer messages at 11pm, changes the brief three times before invoice, and adds a new stakeholder to the approval chain every fortnight. Revenue is the criterion the P&L is loudest about, but by the time the P&L is loud enough for you to hear it, you have already been paying with the wrong currency for six months.

This post is about the four signals that appear before the P&L notices, in the order they appear, and the specific things to do about each one. It is not a pep talk about “firing toxic clients”. It is the operational answer to a question every services business hits and almost nobody writes down: how do you tell that an account has quietly become one you should end, when the invoice still gets paid?

Why revenue is the wrong instrument

Revenue tells you what an account is paying you. It does not tell you what the account is costing you. Those are two different numbers, and only one of them is on the invoice.

The cost of a difficult account is not “hours worked”, which is the version most agency-finance software measures. It is “hours worked” plus a set of other, harder-to-measure numbers that behave like second-order costs on your entire business:

• Fragmented attention across the team. A demanding account fragments not only the account manager but the two or three people they escalate to. The producer who could have spent an afternoon on planning instead spent it in a Slack thread. The founder who could have taken a sales call instead read a 900-word email and drafted a reply that would not offend. This cost never appears on any timesheet because nobody thinks of “reading an email” as billable time, but it is exactly what a fee is supposed to cover. It is also larger than it looks: the research on interrupted work finds that people compensate for interruptions by working faster, at the price of measurably more stress and effort — so the team absorbing a demanding account is not simply losing the minutes spent on it.
• Bench avoidance. Every senior person on your team eventually decides which two or three accounts they do not want to be staffed on. When a difficult account triggers that decision across three senior people at once, the account is running on your two juniors and your goodwill. This is invisible on the org chart and obvious in the team’s mid-year review.
• Cascading tempo damage. A single account whose response expectation is under two hours does not slow that account down; it slows every other account down. The producer with the eleven-inbox context switch is delivering less good work on the calm accounts too. The revenue on those calm accounts is being taxed by the difficult one, and none of them will ever bring it up.

None of these show up on the P&L in a way you can point to. They show up as a slow, unglamorous drift in team quality and account health that finally reaches the top line about two quarters after the causes started to accumulate. The purpose of the four signals below is to see the causes before they compound.

There is also a reason revenue is a psychologically dangerous instrument, not merely an incomplete one. The longer you have held an account, the more you have invested in it — the relationship, the onboarding, the institutional knowledge, the year you spent getting the reporting right — and the harder it becomes to end, independently of whether it is worth keeping. That is the sunk cost effect, documented by Arkes and Blumer in The Psychology of Sunk Cost: the tendency to continue an endeavour once money, effort or time has been committed, driven largely by not wanting to appear wasteful. A large long-standing account is the highest sunk cost in the business, which is precisely why “but they are our biggest client” feels like an argument when it is only a description.

Signal one: scope drift that is defended rather than fixed

Scope drift is normal. Every retainer drifts. The question is not whether it drifts — it is what happens when the drift is named.

In a healthy account, when you raise “the last three requests were out of scope”, the client either agrees and adjusts the ask, agrees and pays a change order, or asks for a re-scope conversation. All three are versions of the same behaviour: the client acknowledges that the scope document is a contract, and treats a mismatch between the document and the ask as a problem to be resolved.

In an unhealthy account, the drift is defended. “That’s what we always thought was included.” “It’s a small thing.” “This is why we hired you — we shouldn’t have to specify every deliverable.” The specific defence varies. What is consistent is the pattern: the drift is not a mistake to be fixed but a position to be maintained.

The tell is that the client’s response to naming the drift is more work for you, not less. A healthy client, told the last three requests were out of scope, sends fewer out-of-scope requests. An unhealthy client sends more, with better justification for why they should be free.

This is the first signal, and it is early. The account is still profitable at this point on paper. The drift has cost you maybe six unbilled hours this month. But the pattern is now set, and it is not going to un-set itself. When you see this, you have between one and two months to have the re-scope conversation (documented in how a profitable retainer quietly becomes an unprofitable one — the three-move script is designed exactly for this moment). If the re-scope fails, you have moved into signal two.

Signal two: the approval chain grows

Signal two shows up as new stakeholders. Every 6-8 weeks, a new person joins the approval conversation. The head of category. Then legal. Then the CFO’s assistant. Then a consultant somebody hired to advise on the vendor relationship. Then somebody’s boss.

Each new person is individually reasonable. The problem is not any single addition; it is the pattern. A healthy relationship stabilises around a small approval group after the first month or two. An unhealthy one accretes people at a rate that has nothing to do with the size or importance of your work.

The mechanism behind the pattern is worth naming. When a client is dissatisfied with something they cannot articulate, they add reviewers. The theory is that another set of eyes will surface what is missing. In practice, each new set of eyes has slightly different criteria, and the deliverable that would have satisfied the original stakeholder now has to satisfy all of them, which no deliverable ever does. So the client adds another reviewer, and the cycle deepens.

For you, this manifests as re-work, re-work, re-work — usually accompanied by increasingly vague feedback. “Not quite there.” “Could you push it more?” “Maybe try a different direction.” The instinct is to do more work. The correct diagnosis is that no deliverable is going to satisfy the current group, and the account is going to consume the number of hours needed to satisfy a group whose composition will change again by the time you’re back in the room.

The fix at signal two is a re-scoping of the approval process, not of the deliverable. Not “let’s clarify what you want” — you cannot clarify what a moving target wants — but “let’s clarify who owns the decision, so we’re not shipping to a moving room”. If the client agrees, the account can heal. If they cannot even name a single owner, the account has told you what you needed to know: there is no version of the deliverable that will settle the room, and continuing to serve it is a bet you will lose.

Signal three: the brief that changes after delivery

Signal three is more advanced. The deliverable is finished, on-brief, and delivered on time. Then the brief retroactively changes.

You are told, in one form or another, that what you delivered “isn’t quite what we needed” — despite it being exactly what the written brief asked for. The direction that was signed off in week one is now, in week four, “not what we thought we were saying”. The version approved for launch on Monday is, on Tuesday, “not going to work with the CEO.”

This is different from an unclear brief. An unclear brief is a mistake at the start. A retroactively-changing brief is a pattern of moving the goalposts after the shot has landed. The two look similar in a single instance and are completely different across a series.

The reason this pattern is dangerous is that it is not, strictly, unreasonable — sometimes a client genuinely changes their mind, sometimes a stakeholder appears late and objects, sometimes the market moves. In one-off cases it is a cost of doing business. As a pattern it is a diagnostic: this client cannot commit to a brief with the confidence needed to run a services relationship at all.

The specific damage of signal three is not the re-work. It is the psychological effect on your team of shipping work into a fog. A team that ships to a stable brief improves at the craft. A team that ships to a brief that will be redrawn after delivery stops improving, because there is no way to internalise “what good looks like” when the definition changes retroactively. Your good people leave first, quietly, and their exit interviews mention “unclear direction” — which is the polite version of “the target moved after every arrow landed”.

The action at signal three is: you have one honest conversation about the pattern, using specific examples, and either the client acknowledges it and agrees to a written brief-lock (with change orders for material changes) or they explain it away. The explanation is your answer. This is the last stage at which the relationship can be repaired. If the brief keeps moving, you are at signal four.

Signal four: the account nobody on the team will staff

The final signal is behavioural and it is unmistakable.

You need to staff the account. You ask the senior producer who has the right skills for it. They tell you they are already at capacity. You check — they are, on paper, but everyone is at capacity all the time in a services business, and this producer would normally find a way. They don’t, this time. You ask the second-choice producer. They also cannot. You suggest a rotation that would free somebody up. It gets pushed back on. In the end you either take the account yourself, or you assign it to whoever is most junior, or you assign it to whoever will not push back.

This is the whole signal. Not that you talked to the team about it, not that someone raised a concern — but that when you go to staff the account, everybody quietly reorganises their availability so it does not land on them.

Your team has already decided that this account is one they cannot make succeed, and they have made the decision below the level of official conversation. They will not tell you in a meeting, because it feels petty. They will tell you by being busy. The pattern is remarkably consistent and it appears about two quarters before the P&L notices anything.

At signal four, the account is over. Not because you have decided so, but because your team has, and your team is the reason the account is being delivered at all. Every day you continue is a day you either burn out yourself doing the work, or ship substandard work through your juniors, or lose a senior person to the account they said no to.

The right action is to sunset the account at the next natural boundary — a renewal, a contract cycle, the end of a quarter. Not mid-project, not in anger, not with a long email. A one-line conversation, a written termination note, and a professional handover that lets the client take the work to a competitor if they want to. Ninety days later you will wonder why you did not do it three quarters earlier.

What “firing on revenue” actually looks like

I need to name the specific pattern the four signals above are meant to protect against, because it is the most common way founders fire the wrong clients.

The typical account-review looks like this. It is Monday morning, the P&L is out for the quarter, and the finance meeting is looking for margin to protect. Somebody says “what if we let go of the smaller accounts?” The smallest three accounts are named. They add up to a manageable-looking revenue hit. The decision is taken.

Six weeks later, three things happen. Two of the three released accounts referred you their next enquiry, which you no longer see. Your senior producer is quietly frustrated — the accounts they most enjoyed working on were two of the three you cut. And the large account you kept has, in the six weeks since the release, put in two additional stakeholders on its approval chain and produced eleven Slack messages after 9pm.

You have not saved margin. You have concentrated your revenue in an unhealthy account and cut off your best pipeline in exchange. This is what firing on revenue produces: a services business optimising for its worst customers by cutting its best ones.

The four signals above are what you should be measuring instead. Which accounts are showing signals? Fire those. Which small accounts show none? Keep those, especially the ones your team asks to be staffed on.

The one thing that is not a signal

There is one behaviour that looks like a signal and is not one: a client who negotiates hard on price at the start.

Hard price negotiation, up front, is usually a sign of a serious buyer who intends the relationship to last. They know what they can afford and they want you to price it correctly. Once the deal is done at a fair number, these are frequently the easiest accounts to run — they respect the scope, respect the process, and expect you to earn the fee they agreed rather than to be paid for effort.

The accounts that make the four signals show up are, more often, the accounts that did not negotiate at the start — that took your first quote, said “great”, and started the work. The absence of negotiation looks like an ideal buyer and is often a signal you missed: the client did not care about your price because they never intended for the arrangement to feel expensive to them at any point. That is not the same thing as being a good buyer. That is a buyer who expects the price to buy them your attention on their terms.

Watch signal one, not the price they paid.

Doing the exit well

If you have reached the conclusion that an account should end, the exit itself is a business decision, not an emotional one. Two things matter, and neither of them is the temptation to say what you have wanted to say for six months.

Time it to a natural boundary. A contract cycle. A quarter end. A retainer renewal. Never mid-project, never mid-sprint. The reason is not politeness — it is that firing mid-project costs you an argument about the value of unfinished work, which is an argument nobody wins and which sours the professional reputation on both sides. Wait for the boundary. It is usually less than eight weeks away.

Offer the handover. Say what work is complete, what work is in flight, what documents the client has, what documents they should ask for. Introduce them to a competent competitor if you can — not one you dislike but one you would be happy for them to be with. This costs you nothing that was not already lost and protects your reputation with everyone the client will speak to about the transition.

The temptation to write a long final email explaining exactly what went wrong is powerful and always a mistake. You are not persuading them of anything they will accept in the moment, you are not owed an admission, and the email will circulate for years. Keep the exit short, professional and dignified. If you have to write the long email to get it out of your system, write it, save it, and delete it the next morning.

Where this fits with the rest of the work

The four signals above are the diagnostic. The two neighbouring pieces of writing on the site are the treatment and the prevention.

The treatment, when signals one and two have appeared but the account can still be repaired, is the re-scope conversation script in how a profitable retainer quietly becomes an unprofitable one. If it works, the account heals. If it doesn’t, you have advanced to signal three or four and the actions above apply.

The prevention starts at the moment you take the account. The pricing model you set at the outset — whether the fee is priced for access, for a bucket of hours, or for a productised outcome — is the largest predictor of whether these signals will appear at all. That decision is in how to price your services as a freelancer or consultant, particularly the section on why retainers priced for hours reinvent hourly billing with a subscription wrapper.

And if you have already reached the stage where a client has stopped paying entirely — a distinct problem from the one above, on the wrong side of the “still on the books” line — the sequence and the leverage are in the client has stopped paying: here is the sequence, in order.

FAQ

How long should I wait between spotting a signal and acting on it?

Signal one gives you one to two months to run a re-scope conversation before it hardens into signal two. Signals three and four are late-stage — you have one honest conversation, and if it doesn’t land you sunset the account at the next natural boundary, usually inside eight weeks. Waiting a full quarter “to be fair” is almost always waiting for the P&L to catch up to what your team already knows.

What if the account showing signals is my biggest client?

Size makes the decision harder and the diagnostic more important, not less. A large account showing three of the four signals is doing more damage than a small one showing the same, because it is fragmenting more of your senior team’s attention and setting the tempo everybody else has to match. Sunset at a natural boundary and use the notice period to reweight the pipeline — do not keep it because the revenue line looks scary in isolation.

Should I fire the client outright or try to fix the relationship first?

At signals one and two, try to fix it — that is what the re-scope conversation is for, and healthy accounts respond by adjusting. At signals three and four, one honest conversation is the ceiling; if the pattern doesn’t change after that, you are not repairing a relationship, you are funding one that has already decided what it is. The order matters: attempted repair, then clean exit, never repair-repair-repair until you’re too tired to leave professionally.

What if only one of the four signals is present — is that enough to end the account?

Usually no, if it is signal one or two and the client responds when you name it. A single signal that gets acknowledged and corrected is a normal healthy account having a bad month. It is the compounding — two signals stacked, or signal three or four appearing on its own — that tells you the account is over. Watch the direction of travel, not any single instance.

How do I let a client go without burning the relationship?

Time it to a natural boundary — a renewal, a quarter end, a contract cycle — never mid-project. Send a short, professional termination note, offer a clean handover of what is in flight, and introduce a competent competitor if you can. Skip the long email explaining what went wrong; you are not going to persuade them in the moment and the email will circulate for years.

What if a client asks why I am ending the relationship?

Give a short, non-blaming reason focused on fit — “we’re reshaping who we serve and this isn’t the right match anymore” — not a list of grievances. You owe them a clean exit and a good handover; you do not owe them a diagnostic report on their own behaviour, and offering one rarely changes anything except your reputation. Keep it professional and let the handover do the talking.

Does hard price negotiation at the start mean the client will be difficult later?

No — usually the opposite. Buyers who negotiate hard up front tend to respect the scope and the process once the deal is done at a fair number, because they know what they agreed to and why. The accounts that show the four signals are more often the ones who took your first quote without pushing back, because they never intended the price to constrain what they could ask for.

The one-sentence version

Fire on the four behavioural signals — scope drift that is defended, an accreting approval chain, briefs that change after delivery, and an account your team will not staff — not on revenue. By the time revenue tells you an account should have gone, you have been paying for it in the currency your team resigns over, quietly, for two quarters. The signals above are what let you act before the resignation.