Sharepoint has its uses. I think that unless you're committed to deploying on SP, you are probably better off not using it for a prototype. It takes a lot of co

Sharepoint has its uses. I think that unless you're committed to deploying on SP, you are probably better off not using it for a prototype. It takes a lot of configuration just to start out on it, as by default it is hard wired to look like SP. Swapping out the master page to a more useful one and creating a new style sheet with resets takes a lot of work. If you can find someone that has already done it then it might be viable, but IMO unless you are specifically targeting current users of SP (a surprisingly large number of Fortune 500), it is not worth it. The flip side to this is that there are very few products for SP and you would have a large base for each product unit sold. I am a SP developer, so I can help out if you need it.