Build in Public VS Build in community
Daisy Do
31 replies
We shouldn't build in public.
Where competitors are active.
We should build in community 👇
Where potential users and customers are active.
Replies
kevin newsum@tornadomagnet
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
Share
Both. You shouldn’t be afraid of competitors, if you’re genuine and have engaged community
Build in community
Flipner AI
I think that it's cool if you have an opportunity to do both
Commenter.ai
Build in public
Both work better
It both works.
Build in community is good
Build in community
Both work better
Build in public
Bababot
I am working on both
@kabir_haynes Cool Kabir! Where do you usually build in public?
It both works.
Build in community
AI Researcher
I totally get where you're coming from, but I think there's actually a lot of value in building in public. It allows for transparency and feedback from a wider audience, which can be really valuable for improving your product.
Build in public
Build in community
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.
Lancepilot
Agree Daisy. Building in a community definitely seems more strategic, engaging directly with potential users and customers. It fosters a more meaningful connection.
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.
REI Litics
@johannes_kraus_13 this is interesting. I see your point about community and didn’t think about it compared to public