Skip to main content

IT startup - scaling up customer base

Recently I had an interesting conversation with someone who brought me a new theory that integrating sales team and development team "closely" will increase the productivity. Conversation went on like these:

Someone: Sales team and development team should work closely for better productivity.
Me: What are the IT companies having such setup? What are the IT companies that increased productivity through such setup?
Someone: (No answer)
Me: How have you arrived at that theory?
Someone: 'coz the sales team will get more technical questions and only when they closely work with the development team, they can able to answer.

Later I felt that the person is somewhat right, the problem lies with the customer base and the person's inability to bring better solution. Then, I come to an analogy of Waiter, Cook and customer base in a hotel.

Waiter, Cook and customer base in Hotel



Here, the Waiter can be compared with the IT salesman and Cook can be compared with the developer. For this example, the Hotel can be taken as Saravana Bhavan, where Cook prepares the foods like Dosa and Waiter acts like a salesman.



  • Customer base #1


    These kind of customers will order foods and won't taste all dishes. They'll pay the bill without any complaints, but you can't understand why they didn't taste all dishes and wasted some food that they paid for. These people will usually be rich and may not come often. Usually may comprise of 5-10%.


  • Customer base #2


    These kind of people will order foods by name and will taste everything. They'll pay the bill without complaints and will usually be happy. They'll also visit often. Usually will comprise 30-40%


  • Customer base #3


    These kind of people would try to taste new dishes. They'll inquire the taste (sweet, sour, spicy) of the food and would love to try new ones. They'll be happy or sad based on the taste. But, they'll pay the bill and visit again. Usually will comprise 50-60%.


  • Customer base #4


    These kind of people will usually be extremely good Cook themselves or some of them will even pretend to be. They'll ask micro details about the ingredients of the food, from where the ingredients are sourced, why particular ingredient is not added,... and any questions that can be answered only by Cook--not the Waiter. For whatever thing they get, they'll usually complain and would fight to pay the bill. Usually will comprise less than 1%.



When dealing with "Customer base #4", people will usually think that the Waiter can better be trained by Cook to give "necessary answers". Also, people would usually keep Waiters above Cooks socially. But, the real problem is that Waiters are cheap and replaceable than Cooks. When the customer is trying to outsmart the Cook, there's no winner.

When coming to IT startups... they should constantly improve the customer base--so that the "Customer base #4" is always below 1%. If such customer base takes 100%, then they can't scale up well.

Comments

Followadream said…
It's a wonderful analogy and presented so well. I am becoming your regular reader Bro! Keep blogging.

Actually, a Neyar Veruppam.. "From your point of view, how a leader should be or what skills should a leader should posses!"

Thanks!

Popular posts from this blog

Interview question #1

Since I have been asked to interview experienced PHP programmers, I was preparing few interview questions. I came to know, most of the people ask questions found in the Internet; most of them are like "What is the function used to connect MySQL DB in PHP". Personally, I don't like these types of questions; I'd thought the person must apply ideas what he was taught in colleges--finally I came out with one question: A product vendor has Quantity Vs. Price data like 1 -> Rs. 50 2 -> Rs. 95 3 -> Rs. 140 .... like upto 1 million data. He wants a system, which gives the price when the quantity is provided. For example, if you provide the quantity value as 2, then it should provide Rs. 95. How this system can be designed? As expected, all the people said about using database tables and quering on quantity. I have asked them to find out a system which doesn't use databases--provided the accuracy of the system may not be 100%--it may give at least 90% ac...

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?