Skip to main content

Bootstrapping in India

I'm posting my response to a question asked on LinkedIn Answers by Sramana Mitra: "Bootstrapping a Product Company from India?"

Here's what I had to say:

  • One aspect of bootstrapping is money. The other is people- good people.
  • We're solving both problems with our strategy of treating our offshore team in India as a services company that specializes in high-quality, low-cost product development for early-stage startups in the Silicon Valley.
  • But we are really a web-based product startup based in the Silicon Valley with our offshore team based at Hyderabad, India, since June 2005. When I came back from India in September 2005 after putting it all together, I had a team that boasted a University gold-medalist who turned down an offer from Google and deferred PhD at MIT to join us, a national programming competition winner, and a seasoned manager from Wipro. Then one fine day, in March 2006, my whole team just disappeared, and I only had 85 pages of use-cases left to show for it!
  • Since then, I've rebuilt the team with more dedicated and ambitious employees led by someone who had prior experience of working for a Silicon Valley startup but only a 2nd class B.Com degree. But we're now just kicking ass big time because we're using user-stories instead of use-cases. Our Extreme Programming driven process has done wonders for us, and we're now the experts at applying XP across borders for a cash-starved early-stage web-based product startup - and we're leveraging our experience to help other Silicon Valley startups also bootstrap.
  • For us, it's less about money and more about a strategic decision to help in our growth plans. We are kicking ass because we offer complete source-code level transparency and control, no long-term contract, better quality, faster, at a fraction of the cost of outsourcing to India. And while the rest of the services industry has only two models, "I Screw You" (i.e. Time & Material) and "You Screw Me" (ie. Fixed Bid), our unique pay by productivity model gives us an incentive to put the most productive people to work on other startup projects as well.
  • Most importantly, we're not really a "services" company nor aspiring to be one anytime soon. This means we're not doing it for money, we can pass on all the savings from our process to the customer. We're doing it to hire and retain good people in India- where engineers prefer brand-name companies first, and then services companies with steady cash-flow- not "risky" product companies.
  • The fact that we're also an early-stage product startup in the Silicon Valley- eating our own dog-food so to speak- lends great credibility to our offering. And it helps that we understand intimately the value of being responsive to the customer and market needs.


Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. Allow me to explain. The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with. Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria. Describing all the requirements as User Stories for a decent sized product is

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams . Between the bigger things you cannot do, and the smaller things you don't want to do, you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded". I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day. Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add you