Ship embarrassingly early with clear beta warnings to set expectations
Release your product even when it feels embarrassingly unfinished, but set clear expectations through beta labels and warnings. You still get press and interest, and early users self-select for risk tolerance.
When to use
When you have a functional but rough product and are debating whether to launch or polish further. The warnings protect you while the launch generates momentum.
Don't do this
Waiting for perfect before launching, or launching rough software without warning users about its beta status.
5 Founders Who Did This
Released version 0.8 in February 2013 which was indeed pretty embarrassing but had a lot of warnings around how beta it was
Explicitly stated biggest fear is nobody trying the product—would be fine with people trying and hating it because that is feedback. This fear drove him to launch imperfect rather than endlessly tweaking
Launched barebone product as basic as possible. Made it clear it was only him, used 'I' in emails never 'we', about page emphasized solo founder
Launched with only 3 interviews instead of the planned 10 because phone-based transcription was taking too long. Treated each new case study as its own mini-launch event
Launched as a PDF attached to a school email listserv with a clipart logo, manually attached to emails for just 45 initial subscribers