Subscribe
Sign in
Build in Public VS Build in community
We shouldn't build in public.
Where competitors are active.
We should build in community 👇
Where potential users and customers are active.
30
Replies
Best
Rubin Shao
Building in community is essential, but building in public requires rapid development capabilities, enabling you to iterate quickly on your product. Otherwise, you risk being surpassed by imitators.
Report
Share
I would rather build in community. You always have the problem that you don't know your customer very well in the beginning...so adding a lot of "noise" in public..is bad, compared to a real closed community environment.
@johannes_kraus_13 this is interesting. I see your point about community and didn’t think about it compared to public
I would rather build in community. You always have the problem that you don't know your customer very well in the beginning...so adding a lot of "noise" in public..is bad, compared to a real closed community environment.
Agree Daisy. Building in a community definitely seems more strategic, engaging directly with potential users and customers. It fosters a more meaningful connection.
Both. You shouldn’t be afraid of competitors, if you’re genuine and have engaged community
Obviously not totally mutually exclusive (YMMV), but if I have to choose one, as a community builder, I have seen some genuinely remarkable insights bubble up from community feedback