Hello Fellow Delphi Person. Don't see enough of those. We have been looking at some similar ideas. For a new company there are complicated choices, and a big reality check.
#1) Is your idea going to be worth your effort?
#2) Is there a real market or monetization strategy out there?
#3) What is the minimum energy you will need to expend to get a prototype to test the idea?
#4) What will it take to move from that prototype to a finished shipping revenue positive solution?
Software Startup Rule #1. Most software companies do not fail for lack of technological expertise, the fail for lack of understanding the market. (If you don't do the software -- then that is YOUR JOB)
Software Startup Rule #2. Get help with building a plan. Every dollar you spend building a great plan will return to you in missed headaches.
Software Startup Rule #3. Everybody has a great idea on how to change your idea a little, but will they sign a contact with a deposit to get you to do it? If not, think long and hard, does it distract you from your focus?
Software Startup Rule #4. Software Development is Easier in Photoshop and on a whiteboard, so use them to test your idea. Prototype with pictures and powerpoint. Get a Technical Needs Analysis done AFTER you know what you are building.
I have managed the design, build, deployment and maintenance of software that has been used by millions of users a month, but we never shipped a product until it was ready, and we never started a product with a commitment that we were going to have some level of revenue stream or market advantage from it.
We have build products that failed, but not for engineering reasons, for marketing reasons.
The reason for mentioning this is the idea of how to get things launched is a great topic for this forum.
I have been working with someone I did a startup with that grew for under 10 to 90 people from Feb 95 to Dec 95, just before the internet boom. I left to do internet stuff, and recently he has reached out to me and said,
"There is no simple solution."
* Local teams take time and money to build.
* Remote teams will try to build the exact spec you send them - without any of your insite but will take all of your money giving you something that looks like what you want. (Oh - I know this one too well)
* What you should want is to partner to manage your project from cradle to grave.
The people who write your prototype are not the right people to scale it to the size you want to make your investors happy.
Lets keep moving this discussion forward / since we are all very good at what we do, and all have opinions lets put our heads together and find a way to make startups happen.
PS: Not Sure I know what I'm talking about? Look at my linked-in profile. http://www.linkedin.com/in/podjacker
PPS: Send me an email and I will send you an electronic copy of the book I wrote for friends and students who were doing small ventures in the mid 2004. subject: "CashCowMarketingPlan Please"