Difficult clients: the five types, what each costs, and how to respond
Difficult clients fall into five types: the scope creeper, the ghost, the micromanager, the slow payer and the committee. Each one costs money in a specific, measurable way, and each has a specific response. Most responses are a contract term enforced calmly: a change process, deemed acceptance, a single approver, a right to suspend work.
After enough years running a services business you stop being surprised by clients. The same five behaviors turn up in every portfolio, in every industry, at every project size.
A pattern can be planned for. Each type below costs you money in a particular way, and each has a response that works most of the time. In nearly every case the response is something your contract should already say, applied early. The owner’s usual failure is waiting three months and then reacting with frustration to something that needed a calm sentence in week two.
This article is part of the Clients hub. The best defense against all five types is having enough good work that you can turn the worst ones away, which is the subject of the pillar on how to get clients.
What each type costs
The figures assume an agency with a loaded team cost of $600 per person per day and a billing rate of $150 an hour.
| Type | What they do | Where the money goes | Worked cost |
|---|---|---|---|
| Scope creeper | Adds small requests outside the agreement | Unbilled hours | 6 hours a week for 12 weeks is 72 hours, or $10,800 |
| Ghost | Disappears when approval or input is needed | Idle capacity and missed start dates elsewhere | 2 people stalled for 3 weeks is 30 days, or $18,000 |
| Micromanager | Directs the team’s daily work and demands constant updates | Meeting time and lost output | 5 extra hours a week each for 3 people over 12 weeks is 180 hours, or $27,000 |
| Slow payer | Pays 45 to 60 days late, every time | Cash tied up, owner time chasing | $40,000 outstanding for an extra 45 days, plus 3 hours a month of chasing |
| Committee | Gives conflicting feedback from several people | Rework | 3 extra revision rounds at 20 hours each is 60 hours, or $9,000 |
Put your own numbers in. Without a number, raising the issue feels like complaining. With one, you are managing a $27,000 problem.
The scope creeper
How it shows up. “While you are in there, could you also…” “This should be quick.” “I assumed that was included.” Each request is small and reasonable. None arrives with a budget. By month three the project contains 20 percent more work than the contract and the client is puzzled that it is running late.
The response. Say yes to the idea and attach a price. Every time.
Happy to add the export feature. It is outside the current scope, so I have written it up as a change request: 14 hours, $2,100, and it moves the delivery date by three working days. If you approve it by Thursday we can fit it into the next sprint. If you would prefer to hold it for phase two, that works as well.
Clients who see a price beside each request sort their own list quickly. In my experience about half the requests get dropped and the rest become paid work.
The mechanics need two documents: a scope with an explicit out-of-scope list, and a change procedure. Both are covered in the change request process and in the longer guide on how to handle scope creep. Explain the procedure at kickoff so that the first change request arrives as routine.
For tiny requests, keep a goodwill allowance of about two hours a month, and say so when you spend it. A gift the client knows about builds credit.
The ghost
How it shows up. The project starts well. Then you send designs for approval and hear nothing. A week passes. You follow up. Another week. Your team is half-allocated. Then the client reappears with comments and expects the original deadline to hold.
The response. Two contract terms, stated at kickoff and applied without apology.
A response time with deemed acceptance.
Client will review each Deliverable and provide written acceptance or a consolidated list of required changes within five (5) business days of delivery. A Deliverable not responded to within that period is deemed accepted.
A pause clause. If the client is unresponsive for ten working days, the project is paused, the team is reassigned, and work resumes when a slot next becomes available, with a restart fee where the contract provides one.
Then use them. The message on day five:
The homepage designs went to you on the 3rd for review by the 10th. I have not seen comments, so under our agreement we are treating them as accepted and starting the build tomorrow. If you do want changes, send them by end of day and we will include them. Changes after the build starts will go through a change request.
That message usually produces a reply within the hour. When a client has gone fully dark:
I have not been able to reach you since the 3rd. I am pausing the project as of Friday and reassigning the team, because I cannot hold them without a way forward. When you are ready to continue, let me know and I will give you the next available start date, which is currently about three weeks out.
Silence sometimes means the client is unhappy with the work and avoiding the conversation. A phone call to ask directly is worth making.
The micromanager
How it shows up. Daily calls. Requests for hourly breakdowns. Direct messages to your developers with instructions that contradict the plan. Comments on implementation details the client has no background in. Your senior people start to feel like temporary staff, and they are the ones with options elsewhere.
Micromanagement is nearly always anxiety. The client has been burned by a previous supplier, or their own job depends on this project.
The response. Give more visibility than they asked for, on your schedule, and close the side channels.
I can see you want closer sight of progress, which is fair given what is riding on this. Here is what I propose. You will get a written update every Tuesday and Friday covering what shipped, what is next and any risks, plus access to the staging site, which updates daily. We keep the Monday call for decisions.
In return, I would like all requests to come through [PROJECT LEAD] so that priorities stay in one place. When instructions reach developers directly, things get built out of order and we lose time.
Most anxious clients settle within two or three weeks of reliable reporting. The updates must never be late.
If the client still wants to direct daily work after that, they are asking for a different product. Offer it: dedicated people at a daily rate, managed by the client, with the client carrying responsibility for the outcome. What cannot continue is fixed-price risk combined with client control of the method.
The slow payer
How it shows up. Net 15 becomes 50 days, every month, with a different reason each time. They always pay in the end, which is why owners tolerate it for years.
The response. Follow a fixed escalation schedule from the first day an invoice is late, and change the terms after the second occurrence. The schedule, with wording for each step, is in the article on what to do when a client is not paying. The change in terms sounds like this:
Over the last six months our invoices have been paid an average of 34 days after the due date. That does not work for a firm our size. From next month we are moving your account to billing in advance: each month is invoiced on the 20th of the prior month and work is scheduled once payment arrives. I would rather make this change than have payment become a recurring topic between us.
Retainers should be billed in advance from the start, and the article on retainer pricing explains how to set that up.
The committee
How it shows up. Feedback arrives from the marketing director, the founder, the founder’s spouse, a board member and someone in sales, in five separate emails, contradicting one another. Decisions made on Tuesday are reopened on Friday by someone who was not in the room.
The response. Name one approver before the work starts and hold the line when it is tested.
For each deliverable we need one consolidated set of feedback from one person who can approve it. Everyone on your side is welcome to comment, and [APPROVER] collects those comments, resolves any conflicts between them, and sends us a single list.
The clause that supports it:
Client designates [NAME] as its authorized representative with authority to approve Deliverables and Change Requests. Agency may rely on that person’s instructions and is not required to act on feedback from any other source.
When conflicting feedback arrives anyway, send it back:
We have received comments from three people and two of them conflict: [NAME] has asked for the pricing table to be removed and [NAME] has asked for it to be expanded. Could [APPROVER] confirm which direction to take? We will hold that section until we hear back and continue with the rest.
Also limit revision rounds in the scope: two rounds per deliverable, with further rounds billed. A cap gives the committee a reason to gather its views before sending them. Naming the approver is a standard item in the client onboarding process for exactly this reason.
Spotting them before you sign
Every one of these types gives a signal during the sale.
| Signal during the sale | What it predicts |
|---|---|
| “We are flexible on scope, let us just get started” | Scope creeper |
| Slow, patchy replies while you are still being evaluated | Ghost |
| Wants to interview every team member and set their hours | Micromanager |
| Resists a deposit or asks for net 60 | Slow payer |
| A different person on every call, no clear budget holder | Committee |
| Every previous agency was “terrible” | All of the above |
One signal is a reason to adjust terms. Take a larger deposit from the likely slow payer. Tighten the review clause for the likely ghost. Price a contingency of 15 to 20 percent into the fixed fee for the likely committee. When you see three signals at once, decline.
When the response does not work
The sequence is the same for every type. Name the behavior once, in writing, with the cost and a specific change. Give it a month. If the pattern holds, raise the price to cover what it costs you.
If they refuse the new price and the behavior continues, the account is costing you money and people. End it properly, with notice and a handover, as described in how to fire a client. Then fix the gap in your intake that let them in.
Common questions
- How do you deal with difficult clients?
- Identify the pattern, put a number on what it costs, and respond with a process the contract already supports. Raise it once in writing with a specific change and a date. If the behavior continues after a clear warning, reprice the account or end it.
- How do I handle a client who keeps adding to the scope?
- Welcome every request and route it through a written change request with a price and a schedule impact. Say yes to the idea and attach the cost. Clients who see a price next to each addition quickly sort the important requests from the passing thoughts.
- What do I do when a client stops responding?
- Send a message with a specific question and a deadline, then state what you will do if no answer arrives, such as treating the deliverable as accepted or pausing work. Follow through on the date. Bill for the paused team's time if the contract provides for it.
- How do I spot a difficult client before signing?
- Watch how they behave during the sale. Warning signs include resisting a deposit, refusing to name one decision-maker, describing every previous agency as incompetent, pushing to start before the contract is signed, and negotiating hard on price while expanding the scope.
- When is a difficult client not worth keeping?
- When the account loses money after all unbilled hours are counted, when the behavior continues after a direct written warning, or when it is costing you staff. At that point a price increase or a clean termination is better than another quarter of the same.