Many times customers ask for Demo or POC (Proof of concept) and dealers provide that. We need to ask ourselves POC – Proof of Concept – is it really required? It may be relevant in some cases, but in most of the cases, it can be avoided. But there are few inherent problems in doing this demo. Much energy and time is wasted in doing the same.

  1. Doing the entire stuff twice
    1. Most of the time demo requires doing entire setup to be done. Most of the time it’s done for Free. There are many system Integrators who charge for a POC, but not all.
    2. This drastically increases the effort and cost of closing a sale, as demo generally requires senior person.
    3. Count one more thing where does the cost of those unsuccessful demos go ?
  2. Client is not serious in providing information or infrastructure.
    1. Since this is a demo, they expect us to come with the equipment and show the demo. In fact many times even SI team is not serious, because this is just a demo.
    2. Now the problem arises when we are selling something that works in a Eco system (or infrastructure)
      1. eg a NAS box, which won’t work well without a very fast HDD and a good network.
      2. Or a thin client which requires a very good server and network, for things to work out pretty well.
    3. Many times, dealer give demo on their laptop, where as actually a server class PC is required.
  3. Management is not aware of the demo.
    1. Many times, The IT person is more interested in upgrading his knowledge, rather than buying something seriously useful for his company. Best way to do this is to get someone do a demo for him, that’s the best and easier way for him.
    2. The finance or purchase department might not even be aware of this, so the question of buying does not even arise.

Basically the idea of customer is to understand the product before buying it. Some of the SIs have practice of charging for the demo, which I think is the good practice. Alternatively, What if we give him money back offer or ask him to raise a conditional PO (CPO). That solves lots of problem. Here we ask the customer to raise a PO, where he states the condition that if the things don’t work as promised, we pay him back (or if you want to be more liberal, he can make payment once things work our correctly.)

There are lots of advantage to this:

  1. Chances of success increases drastically.
    1. Since the final installation is being done, customer and his team are serious about everything.
    2. Planning and deployment are also done properly (from both the sides).
    3. If there are any infrastructure (eg Network or slow server) issues they can get resolved
  2. Serious commitment from the finance and purchase department.
    1. Since a PO has to be raised, all the concerned departments come into action.
    2. The buying intention becomes very clear.
  3. Perfect win win situation
    1. Client limits his liabilities if things don’t work.
    2. System Integrators can make sure that their efforts are not wasted and Return on Efforts increases.


This article is inspired from the ideas by Mr. Manohar Malani

One Comment

  1. Sunil Bhavsar

    Good article and perfect guidance for over enthuse people who get dragged by IT head and unauthorized people in companies and waste time and energy.

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>