You can shovel developers and PMs and QA at the problem, but if it's a greenfield project, (IMO) you're more likely to have people stepping on toes and vying fo

You can shovel developers and PMs and QA at the problem, but if it's a greenfield project, (IMO) you're more likely to have people stepping on toes and vying for territory which can be fatal to a startup. Even if they don't fall to that, time/quality/money is the usual trade-off trifecta, but as long as it solves the problem, extra quality may not necessarily matter. That's where you get into laying out MVPs and getting your customers to agree to buy that MVP and what bells-and-whistles they can live without for a first product. Customers absolutely need iterations to think things through. In fact, that's my default approach now because trying to get everything right for the first meeting is extremely unlikely. Capital does buy you time and iterations.