Do you ship the ugly version now, or hold it until it's something you're proud of?
My instinct is always to polish. I want the first thing someone sees to be good, because I figure you only get one first impression and an embarrassing v1 sticks to you.
But almost every product I actually respect started out rough. The early versions were janky and half-broken, and the founders shipped anyway because real users teach you things a year of polishing never will.
So I go back and forth on this constantly.
The case for shipping ugly is that you stop guessing. You find out what people actually care about instead of perfecting features nobody asked for. The case for waiting is that a bad first experience can kill momentum before it ever gets a chance to stick, and you don't always get told why people left.
I think the answer depends on how reversible the launch is. A small audience that forgives you is very different from a big public moment you can't take back.
But I'm probably biased toward polishing longer than I should, and I've definitely buried good ideas thinking they were not ready yet.
Where do you land: ship the ugly version and learn, or hold it until you're proud of it?
Replies
PopShort.Al -Stream Short Drama
I think “Done is better than perfect.”
Markets evolve fast. User expectations evolve even faster. The reality is that we may never build a product we're 100% satisfied with. But we can take the first step. We can ship. I've seen too many founders spend months polishing features in isolation, only to discover that users care about something completely different... The goal isn't to build the perfect product behind closed doors. The goal is to get into the market, gather feedback, and let real users shape the product with you. I'd rather ship something imperfect and learn than spend a year optimizing for assumptions.
Basedash: AI data analyst
@elara_thorn agreed, I think it's more true than ever with AI speeding everything up. Companies are more willing to experiment, but also quicker to drop products if they're not valuable. Best to get something into users' hands and iterate towards product-market fit.
Basedash: AI data analyst
Ship it!!
The line I'd draw is between ugly and broken. Ugly is survivable. Broken is what actually kills momentum.
If it's just ugly, 10/10 times I recommend shipping.
Basedash: AI data analyst
@kris_lachance 100%, you can always fix ugly with Mythos + a good design skill later on 😉
The advice I got 99% of the time is to ship and start distribution as soon as possible, if possible even before having a MVP. I talked in real life with another SaaS builder who got his first customers before having a MVP, he basically shipped figma designs and roadmaps. That's how ugly and unfinished it should be at first to sell as fast as possible
But I'm myself scared of shipping something I'm not proud of, I'm trying to build the perfect codebase, refactoring, adding observability... Which is unefficient from a business perspective when you have 0 customers
Basedash: AI data analyst
@thomas_gdpt that's true, I've heard similar stories of early startups selling products that don't even exist yet. Enterprise sales cycles take so long anyways that you can probably ship a product before the deal closes 😄
I'd love to ship faster and iterate, but there's this perfectionism in me that tells me nooo you are not ready yet, polish it off and then we'll see
But I do think building fast and failing (or succeeding if you are lucky enough) is better!
Warmup Inbox
It depends on your product: what does it need to provide value?
If it is a record system like a CRM, you should polish the MVP quite a lot, as a big part of the value will be in the reliability of the tool.
If the value is in leveraging a Growth Hack, you can go with something that might break 25% of the time.
I’d ship once the core value is clear and the experience isn’t broken. Ugly can be improved later, but waiting too long usually means learning too late.
ship ugly but not broken. from a marketing perspective the first impression matters way more than builders think... you don't always get a second chance to show someone your product. but I've also killed ideas by polishing them so long the moment passed. the real answer is probably ship to a small group who'll forgive you, learn fast, then polish before the big moment
Receiptor AI
depends on who you're building for! Accountants and finance people have used gnarly enterprise software their entire careers. What I see is that usually, ugly doesn't phase them at all. What they have no patience for is inaccuracy, because a wrong number in their books is a real problem they have to chase down.
That said, the simplicity of your product's workflow is important in all cases, and I found that "ugly" version is often linked with complex workflow. So ok for ugly, but not ok for complex.
Honestly... its so easy to be picky as even when i look at my app now there's so many design features to change. But honestly, as long as its looking good enough for function, i now realise getting users onto the app is more important than how the app looks. Who cares what it looks like if we've got no one using it...
Maybe the real test is this: if the product works exactly as promised but nobody uses it because the UI is rough, can you recover? Probably.
If the product is beautiful but solves the wrong problem, can you recover? That's much harder.