True, but that's all the more reason to "get something out there" without a lot of QA--just do it as a private beta, internal test, prototype, one-off for a single client, etc.
If you can't afford to have a bad product at launch, then don't let your launch be the first time your customers try your product, you know?
There’s a difference between early adopter types who you might already know and the wider market. “Launching” means making your thing available to the second group, not the first—but the first group is the group you should be trying to please first.
If you think like a customer, then the launch and the first-time-customers-use-the-product are the same thing. But if you’ve got your PM hat on, the launch is the END of a long process of learning, building, shipping, validating with a smaller group that’s representative of the wider market.
If you can't afford to have a bad product at launch, then don't let your launch be the first time your customers try your product, you know?