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

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/

Problems with CakePHP - follow-up

Some people have responded including the Datepicker fame Marc Grabanski . So, this follow-up... First of all, I was not ranting nor complaining; I've just blogged/documented my experience. The common problem most of the people pointed out are that it scales for addons.mozilla.com. Those who have accessed their source code can understand that they've done lot of things and also the site is not database-intensive. You should really create a real database-intensive website to understand what I mean. The other point that been pointed out is about open source and community. Lot of people may not be knowing that it's 2 people pushing it and don't want others to be credited . The generic model or dynamic model idea was originally been from grigri and Marcel . It's hard to be called as open source as only few and sycophants are driving it's direction (I'm not talking about svn access) So, here are my humble checklist before you start shouting at me Did you read a

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