Consulting: my experience on when to drop a client

I have been consulting for several years. I think my first consultant job was around 1999 or even 1998. I think I told the story on this blog before: I had planned to finish my Ph.D. and then move into industry. At that point, I faced a wall: very few companies in Montreal were looking for fresh Ph.D.s. I cannot blame them, but back then, it was a big disappointment for me. So, I went into R&D consulting with companies outside Montreal (Paris, Ottawa, Marseille…). It seems there is a fairly good supply of companies lacking a solid R&D department, but needing the R&D. At least, that’s true during some economic cycles. So, I provide ideas, software, documentation, against fair compensation over a couple of months or slightly more. I usually get to keep ownership of some of my work though some of it remain secret.

I stopped consulting for a few years while I was at the National Research Council of Canada (NRC). But now that I’m back as a university professor, I’m back into consulting.

Why do consulting? Firstly, it is fun: you get to work on mostly exciting (read:new) projects that have some importance. Secondly, it pays well enough. If you contribute significantly to a project, you might even be able to negotiate some profit sharing: I was once offered 5% of a company or some cash (I took the cash). Consulting is also a special kind of business: it is focused on your expertise and not on business expertise. You are may have to write bills and do some accounting, but you don’t have to deal with bankers and venture capital, with hiring 30 people and finding offices. Consulting also keep you on your toes: you have to keep learning about the new trends. It also gives you valuable insights into what is really important in the industry and what isn’t.

Why not do consulting? Uncertain times: you might make $30k in a few short weeks, and then make absolutely nothing for a month or more. If you can live with it, it is not so bad because you can use the free time to do other work like research or learning a new computer language. If times get tough, you might have to do some jobs you don’t particularly care for. Also, consulting is not like building a company or a product: your clients do this, not you. Hence, your growth is limited: you can only sell the time you have and this has some pretty dire consequences on how you manage your “business”.

As a consultant, you sell mostly one thing: your time. And you have a finite supply of it. This means you must be extremely picky about the projects you do and clients you work with. You must make absolutely sure that it leads you somewhere because agreeing to one project means you can’t do some other project someone else will offer you down the line.

This is somewhat counterintuitive at first. You’d think that you’d want to agree to do as many projects as you possibly can, and be nice to all clients. That might be true if you sell T-shirts, but not if you are a consultant.

So, how do you recognize a good project and a good client? Bad projects are not so bad as bad client since most consulting jobs are over short periods.However, sticking with a bad client can have terrible consequences. Fortunately, a good client is somewhat easy to recognize. A good client is someone who wants to work with you specifically and has good reasons to do so.

How to recognize a bad client:

  • He will try to bully you in accepting terms that are not acceptable to you. For example, I’ve had a client try on several occasions to intimidate me into lowering my hourly fee to about a third of my usual hourly fee.
  • He will have a selective memory. As a consultant, you don’t carry along a lawyer, so you need to trust the client to remember the terms you’ve agreed to. This is usually not a problem with real business people as they can’t stay in business with selective memories unless they are called Bill Gates. I suggest that the minute you find out the client as a defective memory, you run away.
  • You don’t see how the client has any need for your skills or the client doesn’t/can’t understand what you can offer. This has happened to me quite often due to the highly specialized nature of my work.

Through Jarche, I found out this nice article in Startup Journal which points out the very same thing. Knowing when to drop a client or a project is one of the most important skill you can learn as a consultant:

(…) I’d just been advised to seek a portfolio of engagements that will spawn new experiences and opportunities, listen to my heart and assess the tradeoffs of each opportunity. So I thought to myself, I don’t love what I do for this CEO and working for him isn’t expanding my network, making me rich or helping me to achieve my long-term goals. Should I allow him to chip away at me every time I see him?

No questions there. I resigned, confident that I can replace the revenue with more fulfilling and remunerative work. More importantly, I began to feel for perhaps the first time that I’m on the right road.

Published by

Daniel Lemire

A computer science professor at the Université du Québec (TELUQ).

8 thoughts on “Consulting: my experience on when to drop a client”

  1. I’m told that the first rule of project management is choosing the right project 😉
    Unfortunately, when consulting is your primary source of income, you can’t always be so picky. But you’re right Daniel, you have to know when you have a bad client, and get out as quickly as possible; however painful it may be.

  2. Choosing your projects is a luxury, choosing your clients is a necessity. An unreliable client or a client who doesn’t really need you, will end up hurting you in the long run if only because, whether you realize it or not, you will miss other potentially interesting clients.

    Actually, in my opinion, bad clients (as defined above) will lead you to tough times invariably and whether or not you depend on your consulting for a living is irrelevant. I wasted months with bad clients and I was very frustrated until I learned that I was doing it all wrong and I didn’t have to accept bad clients.

    You have to be very selective with clients… and this may mean you have to invest a lot in networking or even change business or drop out of consulting.

    However, I would be far more tolerant for bad projects. Sometimes, you have to do boring or uninteresting work, that’s life. Of course, if you have other revenue sources, then you can turn down bad projects, and that’s the big difference between depending on consulting for a living and not.

  3. Looking over your “How to recognize a client” list, I easily recognized similarities between those bad clients, and my more obnoxious students. I’m checking the online classlist for my intro algebra class; there’s one girl I flunked last term, and if she enlists in my section this term, I honestly don’t know what I’ll do.

    So, to your “why do consulting?” list, I’d add: if you have a bad client, you can drop them. Not so with bad students, alas.

  4. Thanks for the article, Daniel. I have republished it on ConsultantCommons, a new open content space where IT consultants to nonprofit organizations can share their experiences and improve their practice.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax