DEV Community

Ashkan Rajaee
Ashkan Rajaee

Posted on

When to Fire a Client (and How to Do It Without Burning the Brand)

Almost every founder of a services firm has a client they kept too long. The one who rewrote the scope every week, paid sixty days late, and treated your engineers like a ticket queue. You kept them because the revenue felt too important to lose. Then you looked up a year later and realized that one account had cost you two good people, a chunk of margin and a lot of sleep.

Earlier in my career, as a partner, I helped grow a software consulting company from about $6M to $60M in under three years, and later I founded and ran a fully remote consultancy. Growth at that pace teaches you that not all revenue is good revenue. Some clients make your firm better. A few quietly make it worse.

Here is how I think about when to fire a client, and how to do it without burning the brand.

Firing a Client Is a Leadership Decision, Not an Emotional One

The worst exits happen in anger, usually right after a bad call. The best ones are planned weeks ahead, based on facts, and handled with care.

Before deciding anything, separate a hard client from a harmful one. A hard client pushes for quality, asks tough questions and holds you to your promises. That client often makes you better. A harmful client damages your people, your delivery or your economics, and keeps doing it after you have tried to fix the relationship.

The Signals Worth Taking Seriously

No single bad week is a reason to walk away. Patterns are.

Your best people ask to be moved off the account. Engineers rarely complain about hard technical work. When strong people quietly ask to rotate off a client, the problem is usually how they are being treated.

Scope keeps moving and nobody will sign a change. Every project changes. The warning sign is a client who expects new work inside the original price and resists every change request.

Payments are consistently late. One late invoice is an accident. A pattern of sixty or ninety days turns your firm into an unpaid lender.

The margin is gone and cannot come back. If the account is unprofitable even after honest attempts to reprice or rescope, you are paying for the privilege of serving it.

Values clash. Requests to cut corners on security, mislead end users or treat your team with disrespect are lines, not negotiations.

Try to Fix It First

Most relationships deserve one honest attempt at repair before an exit. Ask for a direct conversation with the decision maker, not just the day-to-day contact. Name the specific problems with examples, not feelings. Propose concrete changes: a reset of scope, a new change-request process, payment terms, or a different working rhythm.

Sometimes this works, and the client turns into one of your better accounts. When it does not, you have a clear record that you tried, and the decision becomes easier for everyone, including your own team.

How to Exit Without Burning the Brand

Once the decision is made, the way you leave matters as much as the decision itself. Clients talk, and so do the engineers who worked on the account.

Give real notice. Follow the contract, and where you can, give more time than it requires. A rushed exit hurts the client's business and your reputation.

Lead with responsibility, not blame. Explain that the engagement is no longer a good fit for either side and that you want to hand it off well. You do not need to list every grievance.

Hand off properly. Document the system, the open work, the access and the known risks. Offer a transition period and, if useful, introductions to other firms who may be a better fit.

Protect your team. Tell your people what is happening and why before the client hears it, and make sure nobody on the account is left exposed during the transition.

Close the money cleanly. Agree on final invoices, outstanding payments and ownership of work in writing.

Learn From It Before You Sign the Next One

Every client you have to fire is a lesson for your sales process. Look back at the early signs you missed during discovery and contracting. Maybe it was a buyer who pushed hard on price and never on outcomes, or a contract with vague scope. Add those signals to how you qualify new work.

The real goal is not to fire clients. It is to build a client base where firing one is rare, because you chose well in the first place and you were willing to walk away when it truly mattered.

If you are building a software services firm and want help shaping a delivery model and client base that grows without wearing out your team, visit https://tdzpro.com.

Ashkan Rajaee is the founder of TDZ Pro. He has spent years building and scaling software engineering teams, including a fully remote software consultancy.

Top comments (0)