COBOL.NET and Cuff links

October 30th, 2009 by Chuck Fritz Leave a reply »

I recently sat through several vendor demos for a client who is in the market for a health care claims administration platform. These systems are large ticket items and the vendors ranged from large and well entrenched vendors with years of experience in the market to small and relatively new vendors with fewer than ten clients.

Several of the key decision makers for the client were very focused on whether or not the various vendors invited to participate had chosen to make their presentation in person or via the web. While this seemed to make little difference with regard to the product overviews once each was under way it was discussed several times throughout the two day period during which the demos took place. Each vendor was made aware of the view of the client and made their decision to travel or to demo via the web and phone from an informed perspective.

Several vendors traveled to Des Moines for their presentation and at least one chose to do so exclusively via the web. One well regarded vendor with significant market-share chose to send sales staff to present in person. The two salesmen from Vendor ‘X’ arrived to make their presentation in well-tailored suits with ties. The lead salesman was wearing a shirt with French cuff and cuff links.  So – from the client perspective – these individuals invested the proper time and preparation for their presentation.  So far, so good!

The Vendor X  presentation began with the normal pleasantries and they passed out copies of the Powerpoint slide deck in color. As the salesmen walked through their presentation they connected a technical resource via Webex who spoke in greater detail about the different business features and advantages of their system.  To me it was apparent that the salesmen in the room were involved in the presentation but weren’t in fact doing the demonstration.  Maybe that is too fine a distinction to make and I’m not even sure that all present that day would agree with me.  The two guys in suits made a fine impression regardless of their actual function or purpose.

About one hour into the two hour presentation/demonstration I stepped away for 5 minutes.  When I returned to the room they were covering the underlying technology of one of their core modules. The salesmen were talking enthusiastically about the virtues of COBOL.NET. Wow! I did a double-take and rather than interrupt and expose my obvious ignorance I quickly Googled COBOL.NET to confirm that the language actually existed. Sure enough, it’s a Microfocus product.

I know my client was satisfied that the various presentations given were a success and that there are several vendors with products that we want to further investigate. That investigation will include site visits to out-of-state technology vendors. We need to ensure that they aren’t two guys working in a garage.  (hmmm….)

If we (Source Allies) can take anything away from this it is that customer perceptions are very important and that some non-technical customers may have some very specific requirements that have nothing to do with technology. Seller beware!

After the demos wrapped up the client’s staff and I compared notes internall.  I did not bother to explain to the client that ‘two men in a garage’ is a reference to the founders of Hewlett Packard, a really large company by any standard today.  I also didn’t bother to give them my deep thoughts on COBOL.NET although we covered that briefly.  As for the suits and cuff links, well quite frankly I like wearing cuff links.

Functionality, flexibility and a clean user interface seemed to clearly carry the most weight in the analysis of the applications.  People seemed to appreciate a good design.  I am sure many nontechnical people can’t describe a well designed system but actually do know one when they see one.

I don’t know how many silent points were gained or lost by vendors for choosing to arrive in person or to demo via the web from out of state. All vendors did a good job of covering their respective applications.  I’d hate to think that a vendor would loose because they demo’ed a system online while a less effective application would fare better because a person arrived to hand out Powerpoint slides they had ‘thoughtfully’ printed and assembled in advance.  That doesn’t really seem like the wave of the future.  Some vendors traveled 6 hours in a car each way to make their presentation.  Another vendor had staff travel farther, by commercial air carrier.  Wonder who pays for those expenses in the end? darth

If I get to leave you with a couple of thoughts I’d like them to be that we should always try to understand what our clients’ hot buttons. While those issues or items may not make sense to us we should make note of them and in some manner take them into consideration when working with that client.

Can you imagine having a great product from both a functionality and a technology perspective and ultimately loosing the sale to a larger competitor with a product written in COBOL.NET? Think of the time we’d probably spend analyzing what went wrong.  I’d rather not find myself in that situation – but I’m certain those guys in cufflinks are going to close another deal sooner or later and COBOL.NET will not slow them down too much with some of their prospective clients.

Advertisement

5 comments

  1. sud says:

    Really enjoyed this post. It was entertaining and still insightful.

    It actually led to open another post that came across my reader:

    http://www.miketaber.net/2009/10/29/how-to-sell-enterprise-software/

    Now I know why the really smart sales people at least want to know if we have the money in the budget as one of the first things.

  2. Tim says:

    The customer is probably looking at this as a the beginning of a long term relationship. I would guess they are interested in a vendor that is available and willing to work with them. If the vendor won’t send someone on-site for the initial sales pitch, they probably won’t send someone for support issues.

  3. Mike Taber says:

    Sounds like the guys who came in with cuff links know what they are doing. If the vendor isn’t thrown out due to functionality or technical challenges, it often comes down to which sales rep you would want to deal with on an ongoing basis.

    Do you want the guy who bent over backwards to come see you and obviously put in the effort, or the one who can’t be bothered to make an appearance, the customer will go with the one who made the strongest impression.

    Price is usually a moot issue. Enterprise level vendors do price matching all the time to make sure that’s not a hurdle to winning the deal. If it’s a very strategic account (like the #1 company in a market vertical), sometimes a vendor will lowball the deal to win or a vendor will accidentally price themselves out of it because the other lowballed it. But doing so runs the risk of being seen as a “cheap” alternative and can backfire.

    This was a good read. Very typical of an enterprise sale, but dead on accurate of what is typical.

  4. Chuck Fritz says:

    I agree. That is what the client was reading into the vendors decision to travel to present. They felt strongly that it was an indicator of the level of service they would receive after the sale. That may be true but I don’t think attention during the sales cycle and level of service post-implementation are always tightly linked. I think the best way to ensure you get the desired level of service on a large enterprise product is to have good service levels written into the software license agreement (or services agreement, or both!) with appropriate remedies. If service is one of the key expectations it needs to be openly addressed in the contracts.

  5. Chuck Fritz says:

    The sales team with the cuff links did know what they were doing. They were polite, articulate and thorough. On a scale of 1 to 10 their presentation was probably a 10. Establishing a good rapport with your audience is always key for a presentation. When you think about roles they were doing an excellent job of selling, and that was their role in the process. They weren’t engineering a new solution and they weren’t consulting with the prospective client. They had been asked to demo their product and they walked through that process very effectively. For a non-technical audience you can imagine what aspects of any demo make a longer-lasting impression!

Leave a Reply