Corporate musings - Written by Julien Le Nestour on Friday, November 14, 2008 - Comments - Permalink

Pilots are not for profit-making. And we’re not playing games.

Expand to see inline the other posts in IT Man­age­ment»

This post is the first of the ven­dors series, explor­ing client-vendors part­ner­ship con­sid­er­a­tions. They’re all tagged and you can find them here.

James Gard­ner has a post up explain­ing how he and his team are look­ing at ven­dors com­ing to them with a new tech­nol­ogy to try out. He makes a series of good points and I would encour­age every ven­dor to read them closely. I can relate to all but one:

Some peo­ple, of course, will argue that this kind of think­ing means that smaller com­pa­nies (who sim­ply don’t have the money to invest with­out com­mit­ment) are locked out of deals with a larger organ­i­sa­tion. That prob­a­bly true, and its too bad.

We actu­ally seek inno­v­a­tive small com­pa­nies, but that doesn’t mean we will pay for doing pilots either. Let me expand this point on pilots.

Here’s how we look at the value proposition:

We can be con­tacted by ven­dors, but often we con­tact them, espe­cially when they are small and not mature for the enter­prise mar­ket. As James said, we won’t even con­sider pay­ing for a proof of con­cept or any other activ­ity that requires us to spend resources (could be money, but more often time) to just see the light and be con­vinced of the value your prod­uct can add: this is your job and respon­si­bil­ity as a ven­dor. Your “cost of doing busi­ness”. So don’t ask any­thing at this stage, we are already spend­ing an increas­ingly valu­able asset on you: our atten­tion. If we talk with you, espe­cially if we called, we are gen­uinely inter­ested, so don’t blow it up.

Assum­ing we know how we should, in the­ory, cre­ate value from your offer­ing, we’ll need to test it, in our own spe­cific and unique ecosys­tem. Your tech­nol­ogy can be cre­at­ing value for any other com­pa­nies, if it doesn’t for us, then it’s of no use. That’s why we do pilots: to con­firm that either the busi­ness value will be real­ized or that the tech­ni­cal risks can be mit­i­gated (at a real­is­tic cost).

A pilot is a small-scale deploy­ment of the tech­nol­ogy con­sid­ered. It will often be sim­i­lar to a full deploy­ment tech­ni­cally, but we will offer it only to a lim­ited set of users. Excep­tions exist: for exam­ple when we think the value poten­tial is impor­tant, but we are unsure how we will be able to real­ize it in our orga­ni­za­tion. We might want to do a full pilot here, open to any vol­un­teer will­ing to try out. But in gen­eral, a pilot is a full deploy­ment, used by a small sub­set of users and lim­ited in time.

The point I want to make here is the pric­ing: we won’t pay for all this. But we are ready to off­set the costs. Let me explain.

A pilot phase is an invest­ment phase for both the ven­dor and the orga­ni­za­tion buy­ing the prod­uct. The ven­dor is invest­ing time and money to demon­strate the capa­bil­i­ties of its soft­ware in a unique ecosys­tem. The orga­ni­za­tion is invest­ing a lot of time and money as well to deploy it inter­nally, con­fig­ure it, set up the pilot phase with busi­ness stake­hold­ers, con­fig­ure the tool, etc. It costs both sides, but as a rule it’s gen­er­ally cost­ing us more.

Pure invest­ment, for both sides. Then hope­fully the pilot is suc­cess­ful and the project moves to a full deploy­ment. And both sides start reap­ing the ben­e­fits: the ven­dor as rev­enue, the orga­ni­za­tion as enhanced productivity.

What about small com­pa­nies? Well, in our case, we are ready to off­set the cost of the pilot. But we mean real cost. If you need to buy hard­ware, fine. If you want to bill us consultants’s time, nope.

The insis­tence of mak­ing prof­its right away is a good sig­nal of how much value the prod­uct brings. Con­fi­dent ven­dors are all too happy to pro­vide all the sup­port for the pilot for free, because they know we will want to move on to a global deploy­ment. They are con­fi­dent and jump on the occa­sion. If you’re try­ing to make a quick profit right at the pilot phase, then that tells us you are not con­fi­dent you will bring value and want to book a quick profit. So yes, we use those atti­tudes as a sig­nal to judge the qual­ity of the prod­uct. It served us well.

Why expand­ing on all of this? Well, to drive home this point James is mak­ing for sim­i­lar reasons:

I often won­der, when I sit across the table from a poten­tial part­ner whether they realise this, or think we’re play­ing a nego­ti­a­tion game. I can assure you we’re not.

Believe us. We are not try­ing to play hard­ball. We just need to work within a large struc­ture which adds some over­heads. The cost of doing busi­ness with large com­pa­nies is high, but then again the rewards are higher and we take part of the risk off the table by off­set­ting your cost. And don’t for­get when you ask us to demon­strate commitment:

Here is another term I some­times hear from ven­dors: “we will do some­thing but you need to have skin in the game”. Since when did invest­ing our time and resources in work­ing with you not become skin the game? We have skin in the game from the first meeting.

Source: The proof of value

Share or Book­mark:
  • Print
  • email
  • PDF
  • Twitter
  • LinkedIn
  • Facebook
  • del.icio.us
  • StumbleUpon
  • Tumblr
  • Mixx
  • Ping.fm
  • Reddit
  • Google Bookmarks
  • Digg
  • BlinkList
  • Diigo

Related Posts


  • Julien,

    Well said. I definitely agree pilot should not be profit makers. I think small fees offsetting the costs for "ecosystem" customizations helps quite a bit for small vendors. More importantly, it creates partnership model and trust early in the game rather than antiquated supplier/vendor relationships.
  • By the way, big enterprises contacting small vendors is a very progressive strategy. More companies should be like that :)
  • Lee Bryant
    Interesting perspective, and I can understand where you are coming from. I think the main danger here is that you end up with product vendors, who can cash in on licenses for little or no up-front cost, rather than solution providers, who might have higher up-front costs but greater long term value. In fact it may be worse than that - this logic is probably what leads many IT departments to sleep walk towards Sharepoint rather than work with partners to create something better. The problem is, not all larger companies are as interested as you in working with smaller vendors, so the risk is often very lop-sided.

    It is great that you share your thinking like this. I wish more IT-side people would do it, as I think both they and the vendors have to much to gain from a productive and honest conversation. Well done!

    Right now, I think the value in the vendor space is mostly with best-of-breed tools like Socialtext, Confluence, Newsgator, Jive, etc. The problem is that none offers a full E2.0 solution like IBM Connections, and of course there is no such thing as a one-size-fits-all solution. Each enterprise case is quite different.

    I expect a lot of innovation and consolidation in 2009 around these issues, and I am hopeful that cost-cutting in a recession will finally be the motivation IT departments need to think beyond their current ways of working.
  • Hi Lee -

    Thanks for commenting. I'm coming from the strategy side and still new to IT: the value of being open about my expectations and openly discussing where we see value hugely outweigh any (if any...) drawbacks.

    Regarding solution providers, the same logic can be applied with the trio clients / vendors / solution providers (SP). SP could work with vendors along the logic outlined in the post, and agree beforehand how they will handle pilots. It should be easy to obtain pilot licenses for free from the vendors.

    SPs would then provide the solution to their own clients, for some of the costs associated to building the solution. For clients, if the pricing is done well, there should not be a major difference between offsetting the costs of vendors and those of the SP.

    Of course, solutions will vary along the fully custom / "productized" axis, with costs varying accordingly. But this should also be for SP an investment. As outlined in the post, once large companies embark on a pilot, it's usually to make it work, not merely to taste the waters. So SP and its client should be well aligned in making the pilot a success and turning it into a full deployment.

    I believe solutions providers have in fact a very important brokerage role to play. I'll go deeper on that aspect in another point, with Sharepoint considerations. I agree with the dynamics you observe, but for me they stem mainly from an immature pricing and segmentation strategy from vendors.

    Thanks again for your comments!
  • Lee Bryant
    BTW - I would like to add that I find your blog intelligent and stimulating, so please keep it up!
blog comments powered by Disqus
Get Adobe Flash playerPlugin by wpburn.com wordpress themes