Micro-ISV: Working on Multiple Projects at the Same Time?
I believe I have decided on my first Micro-ISV projects; three to be exact. One is a primarily web-based effort. Another is a primarily desktop application. And one is just a fairly simple tool.
My contracting work supposedly ends in January, at which time I can start to focus fully on developing these products. (Of course, other contracting/consulting work could come my way after January, and I have to do the normal cost/benefit analysis — but let’s just assume for the time being that I have full time devotion to Micro-ISV products after January).
The tool I think I can get out relatively quickly. But the web-based application and the desktop application are quite a bit more complicated. I would like to get both out as soon as possible, but as a one person shop, new to this whole Micro-ISV thing, I am wondering about serial vs. parallel work styles when it comes to developing products.
In other words, is development “multi-tasking” a good idea?
Back in the “corporate world” working on more than 1 distinct project at the same time was fairly common. However, at least in my case, you worked in a team setting; so you didn’t own the whole project/product on your own. Plus, you didn’t necessarily have to worry about the non-development aspects of the company (marketing, finances, etc.)
With a Micro-ISV I can see it both ways. On one hand, working on two or more projects at once can remove focus from one project and you might miss something. On the other hand, if you get stuck or just burnt out on one project, you can always move to another project for a while.
So I am hoping I can hear about some experiences from folks that have attempted and either failed or succeeded in managing to work on two development projects at one time.
Input appreciated. Thanks.


Joel – The core problem is how long can you go without revenue? Specifically, I think doing the small app (assuming it is to be sold) first is good, then go after one or the other larger projects. Not both at the same time.
Hi Bob, thanks for the comment. That is definitely a fair approach and one that I am considering. The first app is really a small utility that I might just give away for free to get my name out there. I will probably do that one first. The hard part, if I do the other two projects serially, is which one to do first.
I agree with Bob – get the easy one out first. But, I don’t think that you should give it away free. I think the benefits of providing free software are minimal compared to the benefit of learning to market the product.
First off, congratulations on picking your ideas. That really is a hard thing to finalize.
My first (not finished yet) app, http://webworkschedules.com is a large web based project that has been a lot of work. In the middle of it, I split off for what was suppose to be a two week side effort to create my customer support knowledge base app. It has been a more than two week detour. In that time period, my effort on web work schedules has been minimal.
So my recommendation is that you focus on the quick easy one first and try to sell it, for the learning experience. There is a lot more to do after the code is written and having done that once will make it a lot easier the second time around. Once you have that done, then pick between the two large projects. From my personal experience, having the consulting work on the side has been a huge plus for mental relief for myself and my family. While it is taking up a good chunk of time, it gives me financial security to work on my uISV.
I would not try to split your time between projects. My guess is that as an engineer, you will favor the project with the fun items to do. Then switch to the other project once its tasks are more interesting. In the and you will end up with several partially finished products with nothing to sell.
Also if you finish your small app first, you can use it as your fall back to work on if you get stuck on your second project.
Good luck!
Thanks Chris. That is good real life experience advice that is generally always better than any thinking I may have since I have never gone through this before.