Latest / Freelance Careers with Fexingo: Independent Work, Consulting, and Self-Employment / How to Fire a Client Without Burning the Bridge
Transcript
- Lucas: I want to talk about something a lot of freelancers avoid even thinking about: firing a client. Luna: Yeah, it's almost taboo. Like you're supposed to be grateful for every project that comes in. Lucas: Exactly. And I get it — when you're starting out, you say yes to everything. But there comes a point where holding on to a bad client costs you more than you make. I've got a specific case in mind. A web developer I know — let's call her Priya — she had a client who started as a small e-commerce redesign, three-month project, $12,000 fee. Luna: That's a solid project for a solo dev. Lucas: It was. And she delivered on time. But then the client kept asking for 'just one more thing' — an extra plugin, a custom dashboard, integration with some legacy system. The scope crept from three months to seven, and Priya was only billing hourly for the extras at a rate she'd set before she knew how complex the work would be. Luna: Classic scope creep. And she's already invested, so it's hard to say no. Lucas: Right. By month six, Priya realized that client had become thirty percent of her monthly revenue. That's a dangerous concentration. And the client was paying late — net sixty instead of the agreed net thirty. She was spending two hours a week just chasing invoices. Luna: So what did she do? Lucas: She came to me asking for advice. I walked her through a simple framework I use: rate the client on three dimensions — profitability, stress, and growth potential. Luna: Okay, I like that. Break it down. Lucas: Profitability first. Are you making your target margin on this project? If you're hourly, are you billing at your standard rate for all hours? In Priya's case, her effective hourly rate had dropped by about forty percent because she was doing work she hadn't scoped. That's a red flag. Luna: Stress is harder to quantify, but you feel it. Lucas: Absolutely. Does the client respect your boundaries? Do they email at 11 p.m. expecting a response by morning? Priya's client would message her on weekends. That's a stress score of, say, 8 out of 10. Luna: And growth potential? Lucas: Does this client open doors to other work? Do they refer you? Or are they a dead end? Priya's client was a single-owner shop with no network. So all three scores were bad. Luna: So at that point, the math is pretty clear. But emotionally, it's still hard. Lucas: It is. Especially because Priya liked the client personally. The guy was friendly. That's one of the traps — we conflate personal rapport with professional fit. Luna: Yeah, and you feel like you're letting someone down. Lucas: Right. But here's the thing: by staying, Priya was actually letting herself down. Burnout was starting. She was resenting the work. And she was missing better opportunities because her calendar was full. Luna: So what was the exit conversation like? Lucas: She used a script I gave her. It has three parts. First, state the facts without blame: 'Our project has grown significantly from the original scope. I've noticed we're both struggling to keep timelines.' That frames it as a mutual problem. Luna: That's smart — doesn't put the client on the defensive. Lucas: Second, offer a transition plan: 'I want to make sure you have a smooth handoff. I can recommend two other developers who specialize in e-commerce and could take over. I'll also document everything I've done so far.' That shows you're not just abandoning them. Luna: And what's the third part? Lucas: Set a clear end date. 'My last day on this project will be June 15th. That gives us three weeks to transition.' No ambiguity. Luna: Did it work? Lucas: It did. The client was a bit surprised, but he appreciated the professionalism. And here's the best part: six months later, one of those developers Priya referred actually sent a client her way. The firing turned into a referral source. Luna: That's the ideal outcome. But not every firing goes that smoothly. Lucas: No. Sometimes the client gets angry. That's why I advise people to have a financial buffer before firing a client — at least three months of expenses saved. That way you're not making the decision out of desperation. Luna: That's good advice. Because if you're depending on that income, it's harder to walk away. Lucas: Exactly. And there's another angle: diversification. If no single client accounts for more than 20% of your revenue, firing one is much less scary. Priya's mistake was letting that client grow to 30%. Luna: So you have to actively manage your client mix. It's not just about the work — it's about your business's health. Lucas: Right. And I think a lot of freelancers don't realize they have the power to say no. You're not an employee. You're a business owner. And sometimes the best business decision is to end a relationship. Luna: I want to agree, but I also want to push back a little. Because there's a risk of becoming known as someone who drops clients. Reputation matters. Lucas: It does. But here's how I think about it: if you fire a client professionally — with notice, with a transition plan, with references — most people will respect that. And the ones who don't? They're probably not clients you want anyway. Luna: Yeah, that's fair. And I'd add: your best clients — the ones who pay well, respect your time, and send referrals — those clients rarely get fired. The ones you have to fire are the bottom 10%. Luna: If today's episode was useful to you and you want to keep it ad-free, buy me a coffee dot com slash fexingo helps. Lucas: Yeah, that's exactly how we keep these conversations going. No sponsors, just listener support. Appreciate it. Lucas: So, back to the practical side. Priya's story has a happy ending, but not everyone gets that. I want to talk about a second case — a graphic designer I know who had to fire a client who was verbally abusive. Luna: That's a whole different category. That's not just bad fit — that's toxic. Lucas: Exactly. And in that case, the framework is simpler. You don't need to rate profitability. If a client is abusive, you fire them immediately. No notice needed. Luna: I agree. But I think a lot of people still hesitate. They think, 'Maybe I'm being too sensitive.' Lucas: That's the fear talking. But I'd say: if you dread opening their emails, if you feel anxious before calls, that's enough. Your mental health is worth more than any project fee. Luna: So what did the designer do? Lucas: She sent a very short email: 'I'm no longer able to work on this project. I've refunded the remaining balance for work not yet completed. I wish you the best.' And she cc'd herself on a bcc. That's it. Luna: Short and clean. No explanation, no negotiation. Lucas: Right. Because with toxic clients, any explanation becomes something they can argue with. You don't owe them a conversation. Luna: That's a good boundary. And I think one thing that helps is having a written policy in your contract. Like a clause that says either party can terminate with 30 days notice, or immediately for cause. Lucas: Yes. Priya had that in her contract, which made the exit cleaner. The abusive client didn't, but the designer still felt fine doing it because she was protecting herself. Luna: Let's talk about the financial side a bit more. What about clients who pay well but are still high stress? Is it worth keeping them? Lucas: That's the hardest category. I call them 'golden handcuffs.' They pay 50% above your normal rate, but they demand 100% more attention. I've seen freelancers keep those clients for years, and they end up burnt out and unable to grow. Luna: So what's the threshold? At what point is the money not worth it? Lucas: I'd say if the stress is affecting your health or your other work, it's not worth any amount. But a practical rule: if one client takes up more than half of your emotional energy, that's a warning sign. Luna: That's a good heuristic. And I'd add: if you find yourself complaining about that client to friends or your partner every week, that's also a sign. Lucas: Totally. So let's bring it back to actionable steps. If you're listening and you have a client you're thinking about firing, here's a simple checklist. One: rate them on profitability, stress, and growth. Two: if any one is a 1 out of 10, consider firing. Three: if your revenue concentration with them is above 30% and they're a 7 or below on any dimension, start planning the exit. Luna: And if you decide to fire, use the three-part script: facts, transition plan, end date. Lucas: Yes. And after the exit, send a follow-up invoice for any outstanding work, and then — this is key — ask yourself what you learned. What red flags did you miss at the beginning? Was there something in the initial conversations that hinted at trouble? Luna: That's the reflective piece. Because if you don't learn from it, you'll end up with the same kind of client again. Lucas: Exactly. Priya told me later that she now asks every potential client three questions: What does success look like for you? How do you handle changes in scope? And what's your payment process? Those questions alone have saved her from two bad fits since. Luna: I love that. It's basically a pre-firing filter. Lucas: Right. Because firing a client is never fun, but if you do it right, it can actually be a growth moment for your business. You free up capacity for better work. You raise your standards. And sometimes, like in Priya's case, you even get referrals out of it. Luna: So the takeaway: firing a client is not a failure. It's a strategic decision. Lucas: Exactly. And if you can do it with professionalism and grace, you'll come out ahead — both financially and mentally.