Should you build your product in public? Here is what I learned.
Victor Zhang
1 reply
Building your product in public is a big commitment to your (potential) users. I quickly realized build in public is not merely creating a discord server or making weekly/daily tweets. Here is what I learned and I put all my readings here: https://public.superusapp.com/share?version=smfeckbkhqgetskz ; Here is what it covers:
- Some great discussion from HN if you should commit to build in public
- Some theoretical and practical guides on how to do it properly
- Specific tips and best practice building a community using Discord
- Some great communities of current unicorn saas products.
Replies
Daniyar Yeskaliyev@dan_yes
Castofly
Victor, I thanks for the link and the discussion.
I think that building in public solves the core problem for the marketing - communication with the audience. It shouldn't exactly be the user audience, customers, investors or someone precise.
It should be a communication with a general public that for some set of reasons is interested in you, your team or the product.
What I find hard for new products / startups / teams, is that the product goes over many iterations, sometimes pivoting completely from the original idea or concept, and for marketing and sales teams it's almost impossible to work promote a product that changes every week.
So my point is that building in public is the proper way of marketing to promote new teams / products.
But yes, it's a great commitment and one should always be self-aware of how efficiently they can communicate with the public - if it takes over 6 months to deliver some news, probably everyone is going to forget about your product by then.
Share