Have you been designing this product to match the requirements of an existing software company which is selling product today, or are you trying to match the requirements you think you will have once your planned product sells?
If you have an entire process setup already for planning your software development path, and you already have a well working analytics system, then your products are already being managed, and you don't need this.
This product is designed to bring an efficient structure into the life of the ISV. Processes are there for a reason - they make it so you don't have to guess what comes next or what you have to do next. This product is designed on that principle - it takes the random life of the developer and makes it efficient.
There are two ways one can approach the software business - you can either just do things randomly as they coming, and hope things work out, or you can plan ahead, observe trends, iterate and optimize to grow and make more money. This product is designed for people who want to take the second path.
Perhaps if there were a case study of some sort up on your page? Right now, it just looks like a to do list stitched into Facebook, and that's not what we're needing.
If you work without structure, it's difficult. My tool is designed such that you can take a look at the frontpage and you instantly see how everything is performing.
The todo list is a standard todo list (like basecamp has), but the fact that you can keep your product based todo separate from the rest of the usual todo is helpful. When a product is cruising along fine based on trends you observe, you can ignore the product from a business point of view. When things start getting bad, you have a todo list you can refer back to.
I decided against putting up the screenshots of that part because there are too many pages, and I've not completely fleshed out the concept yet.