It's harder to iterate in public - the signal to noise ratio is also lower. Our product Graphite spent almost 2 years in closed beta.
Also if you guys love an underdog story, please support Graphite today - we spent most of the day in #3 and are currently trying to overtake #1 :)
building in public? exciting but not without its caveats. let's dive in.
reason one: idea theft. once it's out, it's fair game. protect your core secrets.
reason two: distraction. public updates can pull focus from actual product building.
reason three: pressure. public scrutiny ups the stakes, not always in a good way.
reason four: over-commitment. announcing features prematurely can backfire.
reason five: inflexibility. pivoting gets trickier when everyone is watching.
it's a double-edged sword, this public building thing. choose your path wisely.
not trying to discourage, just advocating for strategic openness. balance is key.
keep these in mind and make an informed decision. good luck brother!
@shajedulkarim_
I absolutely loves these points. They make sense, having had a similar experience in the past where I built in public and was unable to deliver, I just wished I was a little bit more conservative in my approach.
@jakeharr
Awesome point, I see a lot of people say don't worry about idea theft, but when your competition is more than capable of executing, they it can be dangerous to just share all your secrets
Graphite
FlashApply
NotesNudge
FlashApply
NotesNudge
YOYA AI
FlashApply