<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Prateek Dayal &#187; bootstrapping</title>
	<atom:link href="http://www.prateekdayal.net/category/bootstrapping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.prateekdayal.net</link>
	<description>Ruby on Rails + Web 2.0 + Life :)</description>
	<lastBuildDate>Fri, 20 May 2011 16:13:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Why you are not gonna release early and release often (and why you should!)</title>
		<link>http://www.prateekdayal.net/2009/05/16/why-you-are-not-gonna-release-early-and-release-often-and-why-you-should/</link>
		<comments>http://www.prateekdayal.net/2009/05/16/why-you-are-not-gonna-release-early-and-release-often-and-why-you-should/#comments</comments>
		<pubDate>Sat, 16 May 2009 13:08:16 +0000</pubDate>
		<dc:creator>Prateek Dayal</dc:creator>
				<category><![CDATA[bootstrapping]]></category>
		<category><![CDATA[release early release often]]></category>

		<guid isPermaLink="false">http://www.prateekdayal.net/?p=153</guid>
		<description><![CDATA[Since I started working on Muziboo, I have been a big fan of release early, release often philosophy. We launched Muziboo one month after getting the idea with very basic functionality and a very simple design. Since then, we have been listening to our users and continuously improving it. However I have to accept that [...]]]></description>
			<content:encoded><![CDATA[<p>Since I started working on <a href="http://www.muziboo.com" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.muziboo.com');">Muziboo</a>, I have been a big fan of <a href="http://catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html" onclick="javascript:pageTracker._trackPageview('/outbound/article/catb.org');">release early, release often</a> philosophy. We launched Muziboo one month after getting the idea with very basic functionality and a very simple design. Since then, we have been listening to our users and continuously improving it. However I have to accept that many times in retrospect, I have been embarrassed by what I released. At times, I have also renounced release early release often for a few weeks (in search of design/functionality zen) only to realize later that its a bad idea and that I don&#8217;t have much progress to show for those weeks. I recently listened to a <a href="http://blog.mixergy.com/ries-lean/" onclick="javascript:pageTracker._trackPageview('/outbound/article/blog.mixergy.com');">Mixergy interview with Eric Ries</a> and started thinking about why we still don&#8217;t see that many examples of release early release often and see so many stealth mode startups around us. Here are a few points I think influence people:</p>
<p><strong>A different kind of vacuum<br />
</strong></p>
<p>I think everyone agrees that there is nothing worse than building in a vacuum. However I think the second worst thing that you can do is to build with feedback from people that are not your potential users. Most stealth mode startups take feedback from their close friends, family and other people in their network. The problem with this approach is that if someone is not your potential user, he/she is always gonna compare your product with the successful products of the world and not based on &#8216;that one thing&#8217; that you do really well. You are only gonna get very generic feedback like &#8220;design is not that cool&#8221; or &#8220;you should try to use more ajax and overlay windows&#8221;.  In fact its very easy to get wrapped up in refining your product&#8217;s interface and delay your launch.</p>
<p>Ideally you should just get the basic functionality right and launch the product. You should not care if a lot of people think  that your product sucks (it does, but thats ok). Get your first few real users and listen to what they say. Solve a small problem first and then grow from there. Sure, you are going to lose some people who are never gonna come back to the site but thats ok. Internet is a large place so won&#8217;t run out of users anytime soon and once you have critical mass, most likely they will come back anyway. Find the first set of users who care for the solution that you are offering to them (because it solves one of their pain points) and grow with their feedback. Don&#8217;t obsess with UI before launch just because your ex-boss is still not impressed or because that big blogger won&#8217;t write about you unless you have a nicer interface (he won&#8217;t write about you anway and it does not matter again).</p>
<p><strong>Stealth mode as a marketing technique</strong></p>
<p>Another reason I see a lot of people doing stealth mode startup is to create buzz with the bloggers and potential users. Get over it. Most likely stealth mode strategy won&#8217;t create the buzz for you unless you are already very popular. Its just gonna give you too much time to work on stuff that does not matter. Some startups do end up creating some buzz (or curiosity) but in the wrong circle. Your twitter followers and your blog readers will probably get to know that you are working on this next cool thing but thats as far as it goes.  Most likely your target audience will never hear about your stealth mode product and wait for its launch. If people are coming to your site, show them the real thing and not a text box to add their email address to the wait list. <a href="http://hunch.com/" onclick="javascript:pageTracker._trackPageview('/outbound/article/hunch.com');">Hunch</a> can pull it off but you probably can&#8217;t.</p>
<div class="wp-caption aligncenter" style="width: 510px"><a href="http://www.flickr.com/photos/spyndle/513690281/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.flickr.com');"><img src="http://farm1.static.flickr.com/196/513690281_e8feb1109c.jpg" alt="Working in stealth mode" width="500" height="332" /></a><p class="wp-caption-text">Working in stealth mode?</p></div>
<p><strong>Trying to avoiding rejection (and embarrassment) </strong></p>
<p>More often that not, people are just not comfortable releasing something thats not upto their standard of perfection. They don&#8217;t wanna release something they are not extremely proud of on the day of launch. Right from childhood, we are taught to work on our weaknesses and we simply can&#8217;t release something that other people can easily point holes at. My advice is that its ok. In my two years of entrepreneurship I have realized that you can&#8217;t avoid hearing from some people how your product sucks or you that you have no competitive advantage. You cannot avoid those uncomfortable moments where some people tell you that they would never use your product in the current shape and that it has a long way to go before it gets any where. You cannot avoid that situation by postponing the launch by three more months and working some more on it. As an entrepreneur you have to learn to accept some rejection (atleast early on). You cannot and should not try to please everyone.</p>
<p>In the end most of what I have said is from my personal experience and observation. There are always cases where working in stealth is better and if you have the vision and domain knowledge to pull it off, you should do it. However if you are like most bootstrapped startups, you can benefit a lot from releasing early, talking to your real users and then releasing often with their feedback. As Eric Ries says in the Mixergy interview, understand the difference between your product launch and PR launch.</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.prateekdayal.net%2F2009%2F05%2F16%2Fwhy-you-are-not-gonna-release-early-and-release-often-and-why-you-should%2F';
  addthis_title  = 'Why+you+are+not+gonna+release+early+and+release+often+%28and+why+you+should%21%29';
  addthis_pub    = 'prateek';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.prateekdayal.net/2009/05/16/why-you-are-not-gonna-release-early-and-release-often-and-why-you-should/feed/</wfw:commentRss>
		<slash:comments>54</slash:comments>
		</item>
		<item>
		<title>Getting Real and avoiding useless features</title>
		<link>http://www.prateekdayal.net/2008/06/23/getting-real-and-avoiding-useless-features/</link>
		<comments>http://www.prateekdayal.net/2008/06/23/getting-real-and-avoiding-useless-features/#comments</comments>
		<pubDate>Mon, 23 Jun 2008 07:22:37 +0000</pubDate>
		<dc:creator>Prateek Dayal</dc:creator>
				<category><![CDATA[bootstrapping]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[muziboo]]></category>
		<category><![CDATA[productivity tips]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[getting real]]></category>
		<category><![CDATA[release early release often]]></category>

		<guid isPermaLink="false">http://www.prateekdayal.net/blog/?p=90</guid>
		<description><![CDATA[Getting Real is one of my favorite books on writing software and I love reading it every now and then. However when it comes to real projects, one is very likely to skip the advice given in that book. Its very easy to overbuild a product especially if you love coding. I have seen this [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gettingreal.37signals.com/" onclick="javascript:pageTracker._trackPageview('/outbound/article/gettingreal.37signals.com');">Getting Real</a> is one of my favorite books on writing software and I love reading it every now and then. However when it comes to real projects, one is very likely to skip the advice given in that book. Its very easy to overbuild a product especially if you love coding. I have seen this in Muziboo and also seen it in a couple of other projects that I have been closely associated with. On the other side, I have seen a lot of examples of <a href="http://www.google.co.in/search?q=release+early+release+often&amp;ie=utf-8&amp;oe=utf-8&amp;aq=t&amp;rls=org.mozilla:en-US:official&amp;client=firefox-a" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.google.co.in');">release early release often</a> in successful products and have come to believe that it is in general a good idea to write less code initially and write more as and when required.</p>
<p><strong>Its not the features, Its the idea</strong></p>
<p>People should come to your service for the idea or the philosophy of your product and not for fancy features like ajax search. An example that I really like is @ replies <a href="http://blog.twitter.com/2008/05/how-replies-work-on-twitter-and-how.html" onclick="javascript:pageTracker._trackPageview('/outbound/article/blog.twitter.com');">were not</a> part of twitter. They were introduced later when people started using twitter that way. Same goes for video response feature in youtube which was introduced when people started responding to a video  with another video. Assuming that your service will not take off until there are enough features to wow everyone is a mistake. Delaying launch to add more features is an even bigger mistake.</p>
<p><strong>For wide adoption, build what people want</strong></p>
<p>If people start using your service in ways you did not imagine and you build a feature that facilitates such usage, its gonna have adoption. Both @replies of twitter and video responses of youtube were such features. Its a good idea to not let the geek in you decide what features to implement because the coolest new feature may not be what people want. When your users ask for a feature, they adopt and evangelize it. In case of Muziboo, some features that we built did not have huge adoption but surprisingly features offered as part of <a href="http://muziboo.com/pro/upgrade_pro" onclick="javascript:pageTracker._trackPageview('/outbound/article/muziboo.com');">pro</a> account had good adoption even though they are paid. These were the features that we rolled out after users <a href="http://www.muziboo.com/post/show/149-128-kbps-streaming-at-Muziboocom" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.muziboo.com');">asked</a> for it.</p>
<p><strong>Don&#8217;t underestimate the cost of a feature</strong></p>
<p>A feature is not just a hundred lines of code that you can hack together in a few hours. When you have a live site, a feature is much more. It is</p>
<ul>
<li>Real estate on the page</li>
<li>Cross browser compatibility work</li>
<li>Documentation work</li>
<li>Bug tracking and fixing</li>
</ul>
<p>Make sure you factor in all of above before you decide to implement something new.</p>
<p><strong>Don&#8217;t listen to everyone</strong></p>
<p>Finally don&#8217;t listen to everybody. Don&#8217;t listen to the geeks and coders who love coding new features or use cool new technologies. Whenever in doubt, ask your users.</p>
<p>If you have not already read, I highly recommend reading the Getting Real book.  By the time you finish the book you will realize that constraints are not such bad things after all :)</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.prateekdayal.net%2F2008%2F06%2F23%2Fgetting-real-and-avoiding-useless-features%2F';
  addthis_title  = 'Getting+Real+and+avoiding+useless+features';
  addthis_pub    = 'prateek';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.prateekdayal.net/2008/06/23/getting-real-and-avoiding-useless-features/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Relating to real life entrepreneurship</title>
		<link>http://www.prateekdayal.net/2008/06/17/relating-to-real-life-entrepreneurship/</link>
		<comments>http://www.prateekdayal.net/2008/06/17/relating-to-real-life-entrepreneurship/#comments</comments>
		<pubDate>Tue, 17 Jun 2008 13:20:56 +0000</pubDate>
		<dc:creator>Prateek Dayal</dc:creator>
				<category><![CDATA[bootstrapping]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[bangalore startups]]></category>
		<category><![CDATA[entrepreneurship]]></category>
		<category><![CDATA[relating to entrepreneurship]]></category>

		<guid isPermaLink="false">http://prateekdayal.net/blog/?p=87</guid>
		<description><![CDATA[I had been thinking of writing this post for a long time now but never really got around to writing it. Partly, I wanted to know how some other people feel about this. I think it was good to have a discussion with Prof. Suresh yesterday at IIM Bangalore about these issues. So here it [...]]]></description>
			<content:encoded><![CDATA[<p>I had been thinking of writing this post  for a long time now but never really got around to writing it. Partly,  I wanted to know how some other people feel about this. I think it was  good to have a discussion with <a href="http://www.iimb.ernet.in/iimb/html/facultyprofile.jsp?id=169" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.iimb.ernet.in');">Prof. Suresh</a> yesterday at IIM Bangalore  about these issues. So here it is finally :)</p>
<p>These days, Bangalore has atleast one  <a href="http://www.google.co.in/search?q=bangalore+startup+event" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.google.co.in');">entrepreneurship related event</a> every week. More often, there are more.  Some of these are conferences and some unconferences. Most events see  a large number of aspiring entrepreneurs and a few people who have already  taken the plunge. People who have been there and done that are always  in minority. Specially in the unconferences, most people are aspiring  entrepreneurs or people who are currently fighting it out to make it  big.</p>
<p>If you attend these events and pay some  attention, you can almost always catch words like amazon, google, youtube  in the discussions. You can often hear about how Google came in when  search was already a very competitive market and they revolutionized  everything. How they did not make any money for years but focussed on  building a great service and eventually reached great heights. People  often talk of how the founders of these startups had a vision and they  stuck to it untill they made it big. However for some reason the same  people find it very hard to relate to the entrepreneurs around them.  Entrepreneurs who are more or less like them, who worked with them before  and are now on their own, trying to figure things out.</p>
<p><!--adsense--></p>
<p>I find this very ironical. I believe  there are somethings almost all entrepreneurs have in common. Some phases  in life almost every entrepreneur/startup has to go through. Talking  of the same phase in the context of successful startup inspires people  whereas a startup in the same phase (but not big yet) cannot find many  supporters (in the startup circle).</p>
<p><strong>Confusion Rules a Startup</strong></p>
<p>More often than not, people assume that  by definition, startups would have it all figured out and only then  founders would take a plunge. However if you zoom into the early life   of most successful startups, they too took some time to figure out things.  <a href="http://en.wikipedia.org/wiki/PayPal" onclick="javascript:pageTracker._trackPageview('/outbound/article/en.wikipedia.org');">Paypal</a> and Blogger are two great examples of startups who took sometime  before they finally knew what it is thats gonna make it big for them.  Things are never crystal clear right from the start. Zeroing in on something  that can become big and can be monetized takes some time. Even in the  context of an idea, there are several details that take time of figure  out. Most startups do their market research on the way. <a href="http://www.foundersatwork.com/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.foundersatwork.com');">Founders at Work</a> is a great book to read to understand startups and entrepreneurs.</p>
<p><strong>You don&#8217;t start a million dollar company.  You grow yours into one</strong></p>
<p>You can at best start a company. You  cannot start a million dollar company. Atleast not most times. You identify  a need, solve some problems and then scale it up. There are a lot of  startups who have grown this way (<a href="http://craigslist.org" onclick="javascript:pageTracker._trackPageview('/outbound/article/craigslist.org');">Craigslist</a>, <a href="http://plentyoffish.com" onclick="javascript:pageTracker._trackPageview('/outbound/article/plentyoffish.com');">PlentyofFish</a>, Blogger).  In fact there have been several companies in India too. The most popular  of the lot would certainly be Naukri.com. All these companies took time  to grow. Simply because you have not made a million dollar in the first  year or two does not mean you will not make it in the next five.</p>
<p><strong>You will make mistakes</strong></p>
<p>Making mistakes is inevitable. When you  are trying to do something new (again relative) and when there are no  references/guides available for every step you take, you will go wrong  often. Even the big companies have had failed products. Google had to  buy youtube despite having Google Videos. Apple has had failed products.  Several companies join the <a href="http://www.techcrunch.com/tag/deadpool/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.techcrunch.com');">Techcrunch Deadpool</a> every month. Mistakes  are part of the whole startup experience. So if your next door startup  just threw away their last 3 months of work because it did not take  off the way they thought, don&#8217;t write them off.</p>
<p><strong>Marketing IS a problem</strong></p>
<p>&#8220;But how will you market your idea?&#8221;  is a question I hear too often from the crowd in such events. Trust  me when I say that we are all trying to figure it out. I believe all  startups are finally an exercise in sales and marketing more than anything.  So the companies that figure it out are gonna make it big and you know  how long it takes to make it big.  So don&#8217;t expect to hear in a  few lines the answer to this question. Marketing is an ongoing process.  Everyone is new in internet marketing. We all know how romantic social  media is but very few of us have had a chance to go out with it yet.</p>
<p><img src="http://farm1.static.flickr.com/112/300626853_e11beec975.jpg?v=1163914893" alt="" /></p>
<p>Photo Credit: <strong><a href="http://flickr.com/photos/bike/"title="Link to richardmasoner's photostream"  onclick="javascript:pageTracker._trackPageview('/outbound/article/flickr.com');"><strong>richardmasoner</strong></a></strong></p>
<p><strong>Monetization takes time</strong></p>
<p>Most companies put monetization last.  I think its fair enough considering that no real monetization can happen  unless you grow to a critical mass. Since every startup (atleast the  bootstrapping ones) have very limited bandwidth, founders prefer to  put that into marketing and gaining that critical mass rather than monetizing  early on. Give these guys sometime.  Google could monetize only  after a few years. Facebook and Orkut are still trying to figure it  out. Would you write them off?</p>
<p><!--adsense--></p>
<p><strong>Its not all romantic</strong></p>
<p>Startups take time and this is doubly  true in India, where internet has still not reached every corner of  the country. There are not gonna be many quick exits. Most people would  have to stick to their ideas for reasonably long and not everything  they do during that phase is gonna look romantic. <a href="http://www.amazon.com/Dip-Little-Book-Teaches-Stick/dp/1591841666" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.amazon.com');">The Dip</a> is gonna take  over sooner than later and only perseverance would get startups out  of it. During the dip, romantic is the last thing a startup is. However  once out of the dip, that phase and the story of how founders could  pull the startup out of it looks very romantic. So next time you meet  a guy who has been trying to get to the next level for the last one  year, don&#8217;t write off his startup. If you are concerned, try to analyze  his bottlenecks and see if you or your contacts can help.</p>
<p>This post is not about not questioning  a startup. Its about taking the right lessons from the successful (or  failed) startups and then looking at startups around you in the light  of that knowledge. If we want to develop  a true ecosystem, we  must begin to understand the startups well first. We must understand  that they are different from big companies, they have different needs  and different priorities. Thats what makes entrepreneurship so differnet  and hence fun :)</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.prateekdayal.net%2F2008%2F06%2F17%2Frelating-to-real-life-entrepreneurship%2F';
  addthis_title  = 'Relating+to+real+life+entrepreneurship';
  addthis_pub    = 'prateek';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.prateekdayal.net/2008/06/17/relating-to-real-life-entrepreneurship/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>How to stay productive while working out of home</title>
		<link>http://www.prateekdayal.net/2008/06/14/how-to-stay-productive-while-working-out-of-home/</link>
		<comments>http://www.prateekdayal.net/2008/06/14/how-to-stay-productive-while-working-out-of-home/#comments</comments>
		<pubDate>Sat, 14 Jun 2008 06:16:29 +0000</pubDate>
		<dc:creator>Prateek Dayal</dc:creator>
				<category><![CDATA[bootstrapping]]></category>
		<category><![CDATA[home office]]></category>
		<category><![CDATA[productivity tips]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[stay productive]]></category>
		<category><![CDATA[work from home]]></category>

		<guid isPermaLink="false">http://prateekdayal.net/blog/?p=85</guid>
		<description><![CDATA[I must accept that working out of home is an art and I have been trying to master it ever since I quit my job last year. When you work out of home, you end up saving a lot of travel time and traffic stress but there are a lot more opportunities to waste time [...]]]></description>
			<content:encoded><![CDATA[<p>I must accept that working out of home is an art and I have been trying to master it ever since I quit my job last year. When you work out of home, you end up saving a lot of travel time and traffic stress but there are a lot more opportunities to waste time or even worse, feel bored and demotivated.</p>
<p>There are some things that have helped me avoid the traps and stay productive. Most of these techniques start having some effect only after a couple of weeks so like everything else, patience helps here too :)</p>
<p><strong>Be Accountable and track your progress<br />
</strong></p>
<p>Even though you are <a href="http://prateekdayal.net/blog/2008/06/07/why-are-you-doing-a-startup/" >your own boss</a>, you need to stay accountable to yourself and your startup. That means setting up milestones and then reviewing the progress weekly (or bi-weekly if you prefer).<br />
Since I responsible for the development work in Muziboo, I use <a href="http://trac.edgewall.org/" onclick="javascript:pageTracker._trackPageview('/outbound/article/trac.edgewall.org');">Trac + SVN</a> (at <a href="http://assembla.com" onclick="javascript:pageTracker._trackPageview('/outbound/article/assembla.com');">assembla</a>) to keep a track of my tasks and then review the progress every now and then. Your work may be never ending but having measurable tasks helps you get a sense of accomplishment amongst other things.</p>
<p><strong>Don&#8217;t let the boring work bring you down</strong></p>
<p>This one took me a little while to get used to. Every entrepreneur has to do a lot of not so exciting stuff too and we generally keep avoiding it for as long as we can. This results in a lot of baggage that can cause you to worry about it every now and then. Keep a track of this work too and finish one off for every one or two exciting things that you do. Boring work could be anything from sending a courier to replying to a few emails or getting your car insured :)</p>
<p><strong>Have an office in home</strong></p>
<p>This one is often talked about in the bootstrapping circle. Don&#8217;t work out of your bedroom. Have a separate room that is just for work. Try to get out of it even while you have a tea break. Be there just to code.</p>
<p><!--adsense--></p>
<p><strong>Don&#8217;t try to be over productive</strong></p>
<p>You can be the most productive if you don&#8217;t work 24&#215;7. Its good to compulsorily take a day off every week.  Initially this make seem like a crime but  over a few weeks this would actually help you stay more productive.  A break on a sunday helps you look forward to Monday mornings and also gives your head a well deserved break. Also remember that ideas rarely hit you while you are slogging so a break can actually be more useful than you think.</p>
<p>In the end I feel working out of home is like working  out of office. Nothing more nothing less. You need to give yourself breaks just like you did when you had a corporate job and you need to review your progress just like you did back then. Setting up some processes help a lot. Working out of home, you have the luxury of setting up processes that are best for you. Use it :)</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fwww.prateekdayal.net%2F2008%2F06%2F14%2Fhow-to-stay-productive-while-working-out-of-home%2F';
  addthis_title  = 'How+to+stay+productive+while+working+out+of+home';
  addthis_pub    = 'prateek';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://www.prateekdayal.net/2008/06/14/how-to-stay-productive-while-working-out-of-home/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
	</channel>
</rss>

