When to Fire Your Customers - Technibble
Technibble
Shares

When to Fire Your Customers

Shares

“I’m not paying for this repair because this modem I bought from you 4 years ago is the problem. This all your fault!”

Ever had that customer who’s like a brick wall? Ever had that one client who seemed to turn your business transactions into a dead end? You feel like the words “I’m always right, and you’re always wrong,” seems to be written on their foreheads. Truth is, every business will have these kind of difficult customers. Some owners may put up with it, some don’t.


And oh, the customer is always right. This propaganda has been around for a long time. To business owners, this is outright absurd. The customer isn’t always right. The customer is often wrong. And at times, it’s good to get rid of customers who are a bad match for your business. It will save you a lot of trouble by doing that, and money too. But before you get into a firing-customers crusade, let’s talk about the different kinds of customers that spell trouble for your business.

Customers Not Good for Business

Forgive and forget. These are your customers that tend to forget to pay the bill. And sometimes they tell you that they’re broke, but can somehow afford a vacation. You forgive the delay but then they tend to forget to pay again. It’s a never ending loop of forgive and forget the payment. Keeping this kind of customer will hurt your cash flow. It’s wise to cut them loose.

Complaint is my middlename. Of course, there will always be customers with legitimate cause for complaints. Genuine complaints help uncover whatever weakness your business have that you may not be aware of. However, the customer that you should look out for is the chronic complainer. These kind of customers will find something to complain about even if you shower them with gold and offer your products or services for free. Keeping this kind of customer will hurt your reputation, as they are likely to badmouth your business to others.

I love your competitor. This one constantly talks about your competition. There’s always better service offered by the other side. They do it better over there. If this happens once, it may be worth working through. But if this has become a standard script for a certain customer, it may not be worth the trouble. Someone who habitually puts your business down in your presence is never good for you or your other customers.

Mr and Mrs Rude. There is nothing more  unnerving than to face verbal abuse. This manner of treatment should not be tolerated in any kind of business. While sales and revenue is important, it doesn’t mean you have to become a doormat for other people. But it takes a lot of patience and self-control not to lose it when dealing with this kind of customers. Don’t be afraid to set the boundaries, and tell up front that rudeness will not be tolerated. If this customer keeps at it, then say your goodbye and show the exit.

Before You Jump Ship

There’s just something to watch out for, before firing your customer. Yes, it’s natural to want to weed your garden – keep the loyal and profitable customers and do away with troublesome ones. But discharging problem customers the wrong way can and usually have consequences. Stories of bad experiences about your business can travel far and fast.

If you had a quarrel with your customer, then clarify your disagreement first. Be professional and stick with facts. Listen to what your customer has to say, and then express also your perception of what you think is fair. Even if you are the expert, let your customer feel that they are allowed to question your judgment since they are the ones paying you. It may surprise you that after clearing the misunderstanding, the customer does not warrant to be fired.

But if there really is a need to fire your customer, be professional about it. If possible, say it in person that you can’t do the job. You may have a hundred reasons, but you only need one. And say it in a polite way. You can say that currently you don’t have the resources, or are fully booked, or the job does not match your business profile. Anything. You should, however, avoid saying something that attacks your customer’s character. That would be stepping out of the line of professionalism.

Now that you have politely declined to do business with your customer, there’s a void that you need to fill. Your customer is left without someone to perform the service that you do. Point them to the right direction. Refer someone else. Your customer will remember this and will least likely spread hateful stories about your business.

When Enough is Enough

For whatever reason, unhappy people will always be part of the population. And unhappy customers will always whine and feel dissatisfied no matter what you do. Some may feel that every business is out to take advantage of them. But it’s most often the low value customers who do this. They complain the most, waste huge amounts of your time and often need to be chased for payment.

So, when do you fire your customer? When they cost you. When doing business with them makes you lose more money than they bring in. Consider the points below.

Financial cost. If you run an objective profit and loss statement on these problem customers, you’d find how very little they bring into your business. Or maybe none at all. This is taking into account all the time you spend to give what they want and chase after them. They will likely result into net loss because of the low value they bring. And coupled with the time and energy needed to deal with them makes it not worth the trouble.

Opportunity cost. Your problem customers also cost you by making you lose out on opportunities. They take your valuable time away from your high value and respectful clients. A high value client not given attention is already a lost revenue. So firing your problem customer will allow you to focus and spend more time with high value clients. This builds loyalty and can increase sales with your valued customers.

Emotional cost. An unreasonable customer can make your life miserable. This can affect your productivity. In fact, it affects everyone who is involved in your business. Even your other customers can feel the stress levels. When you lose happiness in doing business, no amount of money can compensate for it. And you’re likely to make mistakes when distressed. One major benefit of running your business is having fun. You should not allow anyone to take the fun out of being a business owner.

Use your sound judgment when dealing with difficult customers. They can cause you to lose money, lose your high value customers, and lose your happiness. If that happens, then there is no point in keeping them. Even so, it’s still wise to make them feel important. Firing a customer is not pleasant for both sides. But part ways professionally. Be tactful and polite. And refer them to another business that can take care of their needs. By that, you save money for your business. And you save your reputation as well.

  • Joe F says:

    I never had any problem dumping a “dead end” customer. Every warranty should be clearly written on every invoice. If you have client that’s past due and needs service, I simply say Sorry we can’t help you because your account is “on credit hold”, or “past due.”

    Although I did have one belligerent customer, a cootter (an half crazy old man) who I did some small work for and hadn’t seen in years, come in and demand service rudely. Because he once, just once that is, spent money with me, I offered to look his PC for free. A quick once over, NOT diagnostics, I sometimes give away as long as its 5 minutes or less.

    For some reason he just went off on his ISP, and vented it me. He then said, “Ah you computers are a dime a dozen…” I then reached into my pocket, and gave a nickle. He said, “What’s that for?” I said, “here ya go, go buy six…” He left. I laughed, as was glad to never see him again.

  • Joe says:

    I have been a Technibble lurker since 2009, having had a PC consulting business in the past but am now retired.

    So how about considering the converse of the above story – when to fire your vendor if you can’t get him to fully support his work?

    I am a long time user of a basic hierarchical dB program called Maple (used to be called Maple Pro) from a Russian company named Crystal Office Systems ( http://www.crystaloffice.com ). I purchased this product many years ago when the owner (a Denis Zolotov) was offering a life-time license. I forget what I paid for it, maybe $20 or $30 (current price appears to be $31.95). At some subsequent time, the author decided to start charging newer users for major upgrades but that did not apply to me since I had a lifetime license.

    Given that I did not know when or if he would go out of business, I have asked for a permanent license key from the author a number of times but he has refused to provide one to me, forcing me to query him periodically for a new key when the old one stops working.

    Over the years I have accumulated 160MB of entries that range the gamut from things I am interested in, to invention ideas to personal health information.

    On the last program update, my dB apparently fails to work and will not open. I just get a never ending loop until I forcefully terminate the program. There is a built-in dB repair function in the program, which unfortunately, does not work. When I run it against my dB, the result is a 57KB remnant! The author of course claims that the repair function works.

    However, my dB does work on the prior release w/o any issues.

    With this background, I reached out to the author to inform him of the problem and see what he could do to effect a repair.

    Sadly, I have made ZERO progress because the author says he MUST have a copy of my dB to test it. I have repeated over and over that I cannot share the dB with him because of the personal and proprietary information it contains. I wouldn’t share that information with anyone in the USA, let alone someone in Russia!

    Being a former system programmer in the IBM mainframe world years and years ago, I offered a suggestion to give me a debug version of the program that would trap what was happening as my file was opened but he has rejected this idea, stating that he needed to do this under his IDE. Apparently, as a “modern” programmer, he does not seem to know how to do anything outside his IDE! [roflol].

    We are at an apparent stalemate The program author refuses to consider any solution other than me sending a 160MB proprietary dB to Russia. Why is the author being so stubborn? Perhaps he wants to get rid of a life-time licensee and sees this problem as his way to do so? Or perhaps he really is just not competent enough to be able to debug anything outside his IDE.

    I am left hanging and it seems that my only recourse is to locate another similar program, find a way to port my dB over to that program and “FIRE” this uncooperative vendor.

    Meanwhile, I would caution anyone from purchasing programs from this company based on the fact that the business is located in Russia, the likely inevitability of a problem occurring and the author’s apparent inflexibility (stubbornness?) and perhaps lack of more than basic programming expertise to solve a problem.

    Does anyone have any ideas or opinions to share?

    • Waldo says:

      As a possibility, can you make a copy of the database with altered data, to eliminate the proprietary info? With that, he’d be able to see the structure you’re working with, at least.

      Why update, if it’s going to cause problems? The old version worked, so keep it.

      How much is your time and frustration worth? If a new working version is $32, and the option may be to rebuild the functionality in a new database – when you find one – WTF? If the price had a couple of zeros after it, I could see some logic to what you are doing. It doesn’t. Paid upgrades get a 60% discount to retail, so you’re trying to save $1/month? Does not compute.

      • Joe says:

        I resolved the problem on my own by using brute force. I deleted the highest level nodes one by one until I found what appeared to be the bad one. Then I deleted each entry inside that bad node until I discovered that there were two problem entries. Once I deleted those, I was able to open the old dB in the new release. So obviously since my dB worked with the older release of the program but not the latest version, something was changed in the latest version. Perhaps a new driver, an API version or something related to opening up the dB. IMO, the author SHOULD HAVE been able to come up with possible investigative approaches that did not require him getting access to my proprietary data.

        I communicated this info to the vendor/author this past Sunday. At that time, I sent him the problem node and all the content in that node (nothing private there), asking him to take a look at the node contents and tell me what is wrong. As of today, I have yet to receive a return reply.

        The point of this isn’t the original cost of the program to me but the stubbornness and intransigence of the author to entertain any other approach to resolving this problem other than send the whole dB to him to work with within his IDE. The value of technical support is when you need it!

        If I could have deleted private info, I might have entertained it just to stop all the time wasting with this author. But the private info is scattered throughout the dB, so that was not viable.

        Now I have to ponder the potential amount of time it would take me to export and re-import the dB into some other program or do I stick with a vendor that has proven himself deficient when the rubber meets the road?

        Again, there are problem customers and there are problem vendors/providers. This is a problem vendor and I certainly would not buy any further software from him. It’s not always the customer that is at fault.

        • JWalker says:

          Did you offer to allow him remote access to your computer so that he could examine the database on your side? Or was remote access to your system unacceptable as well?

          • Joe says:

            He made no request for remote access and I am unsure what he could have done remotely anyway since he had said that he would need to access my dB through his IDE. It seems that he only knows how to work through an IDE.

  • Luckily I only have a single non paying client. The writing was on the wall. I had to chase him down constantly for previous payments. He declared bankruptcy in the recent past. He is always “too busy” except when his office computer crashes and he can no longer access his business files. He works in the construction industry, which info posted to the Freelancers Union suggests has the highest potential for non paying clients. Lucky for me it wasn’t a large sum of money, but it was annoying because the guys wife works with my daughter and I lowered my fee because of that relationship. So I guess I learned the hard way., but I did learn.

  • Mark Oster says:

    I had a company with 18 seats that had a reasonably cordial general manager sit down with me a couple months ago and actually say “… last year we spent $27,000 on IT services and we just can’t spend that much next year again…” Keep in mind that their entire company is run on the internet. VOIP, reservations, website and operations are all connected. They are an adventure dinner theater that packs in an average of 300 to 400 visitors a night. While this account was often stressful because their operation runs late at night and I would get calls from their average age of 19 years old employees at 8 and 9 pm occasionally, I still stayed on-board and felt that their company was still producing decent money.

    Last month I pretty much let them seek out some other independent IT toad that wants to get $45 an hour to handle their constant end user issues. Did I feel bad and nervous about letting them fly away? Sure I was but I have found that I now have that time to use for many of my other clients that need regular maintenance done instead of just putting out fires.

    Sometimes a loss is a blessing in disguise.

  • >