Mark Phạm

Mark Phạm

Co-founder. Building tools
#99094221 follower7 following
⚡️ 4 day streak
#11,496Last month
1 KP
>10,000All time
2 KP

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Recently Supported

Second Brain for AI v2
Second Brain for AI v2AI memory that connects the dots across every tool
QApilot's CoWork
QApilot's CoWork3x Mobile Automation. Same QE Team.
Conan
ConanA native Mac cockpit for Claude Code
welaunch.sh
welaunch.shGet your first 100 customers
Wysera
WyseraOne AI agent. Every department. Content, CRM & ops.
Mementia: Journal & Codex
Mementia: Journal & CodexA scrapbook for your whole life, not a diary.
cotect
cotectA fast, read-first code inspector for the agent era

Forums

•

2mo ago

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?

View more