Customers that I’d like to fire

I’ve had two “inconsiderate customer” incidents this week; actually, both are customers who I’ve done quite a bit of work for in the past but have been inactive for some time.

With customer #1, I contracted in as their business and application architect for several months; even though they didn’t really get what enterprise architecture is all about, I spent most of a year trying to do some internal education on the necessity for EA to help sort out the legacy linguine that was rampant in their organization, as well as the lack of business-IT alignment. A while after leaving, on April 29th 2005 to be exact, I dropped my key contact there an email about the (then) new report from BPTrends on EA tools, saying the following:

…there’s a new report out from BPTrends on enterprise architecture that you can download for free. I gave it a quick review on my business blog, which includes a link to the report. Although the product information in the report is nothing that you can’t get from the vendor’s sites, the first 25 or so pages are a great overview of enterprise architecture, process modelling and simulation tools that provide good background material if you’re ever promoting a related project. I did an earlier post on their report on BPM suites that you might also find interesting.

Usually this type of email at least gets a “thanks”, or “hey, it’s been a while, let’s meet for coffee”, but nothing came back from this. No big deal, customer #1 is a busy person. Then on Tuesday of this week, 340 days after my original email, it arrives:

With customer #2, I did the architecture and design of their original BPM system, and they now need some analysis and design assistance to further increase efficiencies (which presumably would more than pay for my engagement there). Their internal IT architect contacted me in November 2005, we chatted on the phone and by email, then he connected me with the project manager. Long pauses in the conversation ensued, punctuated by several emails and voice mails from me to the PM. Responses took as long as six weeks, or never came at all. Finally, they made a request to have me fly to their site this coming week — the week leading up to Easter, with Friday a holiday here in Canada, and Saturday being when 13 members of my family will be descending on my home for Easter dinner. That, of course, is my problem, so I said yes. Turns out that no one had the funding approved, however, so I received an email two weeks ago saying that the trip was off. I immediately responded with some suggestions on how to restructure the project to reduce the funding issues while still providing value. Their response? Silence, so far.

The thing that frustrates me is that I’m not an unknown salesperson cold-calling these people, I’m a geeky engineer type who worked on site as part of the in-house team with both of these customers for several months and did significant amounts of work that were well-received. Are they just snowed under with the amount of email that they receive, and ignoring all of their business contacts equally, even if they were the one to initiate the conversation? Or, because I’m a contractor/consultant, don’t they consider it worth their time to reply to my email (or even open it for almost a year)? At least I’m pretty sure that they’re not reading this blog entry…

5 thoughts on “Customers that I’d like to fire”

  1. Sandy,

    Welcome to the world of tire-kickers! 🙂

    If I had a dollar for every ‘incident’ I had like this in my many years as a consultant, I could retire. The worst ones are those that shop around and around, and we propose and propose and propose again, but they never buy for some reason that we’ll never know.

    I would chalk up these two previous clients as lacking a sense of urgency. If these issues were biting them in the posterior, you’d be on the next flight out pronto. Doesn’t look like tht happened in either case.

    Over time I’ve learned that good, serious business usually comes to me, not me to it. That doesn’t mean I feel all high and mighty, it’s simply a means of not wasting my time chasing nearly-dead projects or initiatives at comatose organizations whether I’ve worked with them previously or not.

    Enjoy the rest of your weekend and regards,
    Bob

  2. Thanks for the comment, Bob. I’ve been doing this for almost 20 years now and it shouldn’t bother me any more, but sometimes it just makes me shake my head and wonder.

    I agree, most work comes to me now instead of me seeking it out. In the case of customer #2, that’s what I thought was happening. In the case of customer #1, my email was more of a courtesy and intended to be something of value; obviously not, if it took them almost a year to open it!

    No guesses about which customers will not be offered discounted rates in the future 😉

  3. Sandy – I almost hate to admit this, but in my previous life as an IT buyer, I’d have proposals I really cared about sit on my desk for weeks on end, because every day brought a new fire to fight. Post fire fighting, I’d be shocked to see the proposal had aged so. Most often, I would get around to closing the deal. -brenda

    ps – any chance you are attending this: http://www.globalintegrationsummit.com/

  4. Brenda, I don’t have the illusion that my customers are just sitting idle at their desks, waiting for my email to arrive; however, an email along the lines of “sorry, I’m pretty busy right now, get back to you in a couple of weeks” would be good manners.

    No plans to go to the Global Integration Summit.

  5. oops… my comment must have read wrong… I knew you weren’t under that illusion… and yes an email would absolutely be appropriate… what I was intending to say was sometimes a month (or two) would just fly by. now that I’m on the other side (awaiting the email) I feel the pain… payback! I think your “1 year to open” example must be close to a record. -brenda

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.