I realize the conventional wisdom these days is to try to launch something earlier than you want to, but has the goalpost really moved back towards launching products that are "not ready" and full of bugs? I don't know how good or bad the OP's product is, I'm just commenting on the sentiment that its admirable if he did launch something that sucks.
I think there's a certain level of craftmanship and pride in your work that should override the urge to launch early for all the usual reasons echoed on HN. Launching too early can be as disastrous as launching too late, I think this lesson often gets lost in translation because the natural habit is to launch too late.
Releasing early by skipping bug fixing you will make a bad first impression, and that'll pretty much destroy any benefit from launching early.
edit: Note - I am not saying sendwrite has lots of bugs, just commenting that launching with lots of bugs is a bad idea.
But I think people naturally tend to wait too long, constantly "perfecting" the design, the features, the code, etc, as if to almost ensure they always have something preventing them from launching. Because launching is scary.
More people need to do this. Like you said, without constant customer feedback, you're tweaking things because you think you should, not because it will improve anything necessarily.