This short guide, inspired by a few stories I've heard, or some purely hypothetical situations, is meant as a support for making all the decisions right, so you are more likely to put your early-stage company down and waste investor's money.
Never listen to anyone
First of all, never take the technical guys seriously. All they are really interested in is hacking and making things as difficult for you as possible. Each time they say something is too complex or simply makes no sense, ignore them. It’s mostly because they are lazy and not willing to do a great job. Or perhaps they are just seeking excuse for not working hard. Anyway, you are the only one with the vision, and the only one who really takes care, so trust your guts and get rid of them as soon as possible. Especially, if there are cheaper replacements available. After all, why would anyone be able to do more in eight hours? What, are they smarter? More experienced? Of course not! Experience doesn't matter, it's overrated.
It doesn’t really matter you are not earning any money. The idea is great and that’s what matters. However, there are also the customers, that have their own vision on how your product should look like. After all, they are the ones that are going to pay for it, so why not to agree? It’s extremely easy, don’t be afraid. Just go to the meeting and every time they ask if you have that functionality, answer: “Yes, we are just working on that”. Another potentially satisfied potential customer? Great! Good job! Preferably, keep adding new features on a daily basis, so your technical team will get lost in complexity of a product that does everything and you will have a good reason to fire all of them. Also, meeting all requirements means your market is virtually limitless, therefore: you will earn even more money than you ever expected!
Presentation equals quality
Things must look good. No, good is not enough. They must look perfect. For example, look at iPhone. Why was it such a great success? Because of integration of services? Intuitive user interface? Number of applications and great SDK? No, of course not! People wanted to have one because: 1) it was glossy and modern, 2) it was trendy and innovative. Why was it trendy and innovative? Who the hell knows and why would that matter anyway? So, don’t bother with code quality, stability, documentation, test coverage or any other stuff you were never interested in. It’s yet another excuse for those technical lazy guys, so they can spend more time with their families and friends.
Engineering? Be "agile"!
The argument, that an average skyscraper has lower complexity than simplest Web application, and therefore building it without any documentation is not a smart approach, is itself one of the most stupid ideas I’ve ever heard. It’s software, it’s easy. How many times you see these guys you just ask to move things around the screen or change button labels, and they do that in seconds? Why adding new roles or changing user workflow would be different? Changing software is simple, everyone knows that. Also, if you create documentation, people will start asking why to do something that you previously said was wrong. Don’t waste your time explaining that.
What to do next when you eventually reach the goal
Now, when you applied those hints, you can go out there, stand in front of the startup crowd and tell the moving story of a rise and fall of an empire, that could be one once, if not a bit of luck and perhaps some more hard-working people. You earned it.