> "We punted on tons of key issues because we wanted to wait until we proved there was a market for our product. Once we realized there was much more of a marke

> "We punted on tons of key issues because we wanted to wait until we proved there was a market for our product. Once we realized there was much more of a market than we thought, we suddenly had to allocate a bunch of resources to customer support and bug fixes… things that we wouldn’t have needed at the same level if we had built a more robust and full featured product out of the gate." flat out: you're doing something wrong. coding right is faster than hacking around. i guess that's what you are saying: at some point you have to redo all the previous buggy work you've done, and adding features is a nightmare, so all the "progress" you thought you were making was totally backwards. i'm just surprised that "point" came to late in development. once you start having real customers, as opposed to testing an idea with gradually more tech-based mockups, how can you afford not to be doing things right? how you can make progress if every feature is introducing bugs? do you just ignore the bugs and keep pounding against the wall, brute force adding <crap> and trying to trick people into thinking everything is ok, keep the payments coming? don't build your own grave. customers who expect to use your project for the long-view after you've built it require a REAL product. i sooooo wouldn't want to clean up after that mess.