Every founder I work with wants to launch something they're proud of. I get it. You've been thinking about this product for months. You want it to feel polished. Professional. Finished.
Here's the problem: you don't actually know what "finished" looks like yet. Not really. You think you do, but you're guessing. And spending three extra months polishing a guess is one of the most expensive mistakes you can make.
Why ugly works
The first version of Airbnb looked like a Craigslist post. Twitter was a janky internal tool at a podcasting company. Dropbox launched with a demo video before the product even worked properly.
These aren't inspirational stories about scrappy underdogs. They're evidence of a pattern: the companies that win are the ones that get something in front of people fast, learn from what happens, and iterate.
The ugly version does something the polished version can't — it surfaces the problems you didn't know you had. You can't user-test a Figma mockup. You can't learn from a pitch deck. You need a real thing that real people try to use and get frustrated with.
What I actually mean by "ugly"
I don't mean broken. I don't mean buggy. I mean:
- One core feature that works well, and nothing else
- Default styles instead of a custom design system
- Manual processes behind the scenes where automation would eventually live
- No onboarding flow — just a page and a button
- Copy that explains what it does in plain English, not marketing language
Ugly means unfinished, not unprofessional. There's a difference.
The polishing trap
I've watched multiple founders burn through their entire budget on version one because they kept adding "one more thing." Better animations. A dark mode. An admin dashboard nobody will use for six months.
Meanwhile, their competitor launched something worse-looking three months earlier, got real users, learned from them, and built version two that actually solves the right problems.
Speed of learning beats quality of guessing. Every time.
What I tell clients
Give me the one thing your product does that nothing else does. I'll build that first. I'll make it work. I'll make it fast. And we'll ship it before either of us thinks it's ready.
Then I'll watch what happens and build the next thing based on reality instead of assumptions.