12
19 Comments

What should you share when building in public?

Now that I'm ready with the Chatio.ai MVP I want to build it in public but I don't know what to show exactly.

What should I share exactly? Is it MRR, new features, the feedback I've got from users, mistakes I've made, all of the above?

posted to Icon for group Building in Public
Building in Public
on September 15, 2023
  1. 5

    I’d recommend looking at people already building in public for inspiration!

    People like:

    Good luck :)

  2. 5

    According to me the idealogy behind building in public works is as follows:

    • You stumble upon a particular idea, and you discuss publicly about it publicly (here you get the basic insights from people, it can even be demotivating at times, but the constructive feedback gives you a pathway to think in a direction)
    • Also, since you've already discussed the idea, what's wrong with asking people if they're willing to pay
    • You create a landing page for the idea and ask people to roast it!
    • The initial prototype is complete, and start getting signups (here, you also share the figures publicly) now you're unsure about the pricing, you ask people what they think about it...

    & all of this goes on and on. People like to contribute because their ideology also aligns the same way, and maybe this can also be one of the primary medium to gain initial traction.

    Essentially you discuss with the public everything you might with a cofounder.

    1. 2

      I like that approach very much. Open and transparent but also good for marketing your product. Thanks!

    2. 2

      This is great provided you have friends on the internet or just followers that do reply 😀

      1. 1

        Yeah, having numerous friends or followers helps.

        But, even using hashtags, or even tagging people helps gain traction initially.
        And that's what the journey is all about, you share things, and like-minded people start following you.

  3. 3

    Share whatever you think could be interesting for others to learn.

    Think challenges! How are/did you overcome a tech/sales/operations/etc. challenge?

  4. 2

    Think about what would you talk about to your friend in private in the context of your app. What would you share, what challenges would you be willing to discuss?

    I think a lot of people miss the point of being a person, and not just trying to plug in your product in every tweet.

  5. 1

    share everything. what you have done, mistakes you have made, issues you have run into, things you find that work, that don't work.
    the community is very interested in whatever you are willing to share.

    much success,
    Scott

  6. 1

    I'm also trying to build and learn in public with my productized service as well. Thank you to everyone else who is commenting and providing info. For me I've seen that a lot a people share literally everything they are going through when they build and learn in hopes that they can build an audience who wants to learn what they are going through so that they don't have to go through that themselves when they try to build.

  7. 1

    Mistake: New learning for all.

  8. 1

    When it comes to building in public, transparency is your biggest asset.
    Share your small wins and losses, challenges you're facing, and the lessons you're learning along the way. This authenticity not only builds trust with your audience but also provides valuable insights for others in the community. Don't be afraid to show the 'behind-the-scenes' of your journey, as it's often these candid moments that resonate the most with your audience.

    Ultimately, building in public is about fostering a sense of connection and collaboration, so keep the conversation going and learn from the feedback and support you receive.

  9. 1

    what is your purpose of building in public. Is it just to share ? If just to share then just share anything.

    If it is to attract potential buyers than you probably need a strategy on that.

    You need to post something that your potential buyers can relate to. For example for your product, you might show some hilarious response of the chat bot, or some impressive thing the chatbot doing. or maybe talk about LLM and how you use it to improve your chatbot

    You need to think about what content to posts and why you posts it. If it does not fulfil your objective then you might need to rethink your strategy.

    If you want to understand more about build in public strategy checkout this article : What Build In Public really about and Why you should do it

  10. 1

    You should share things that never happened.

    • I've talked to a few millionaires and here are what they said about chatio
    • I refused to sell chatio for seven figures, here is why
    • I fixed a bug that costed us $5K in vercel/aws bill
      ...
  11. 1

    Hey Ryan,

    It's nice to see your a trying to build your company publicly. What I would recommend you to share are:

    New Features: Highlight updates and improvements to keep your audience engaged.

    Mistakes and Learnings: Transparency about challenges and lessons learned is important

    Roadmap: Give glimpses of your future plans to generate excitement and gather feedback.

    The goal is really to create a compelling narrative and show your passion for your project

    Good luck with your startup!

  12. 1

    I share progress and stats, technical questions, roadmap, features, landing page, tricks I find along the way that help others.

  13. 1

    Sorry to hijack but I wonder where to share, like is it only Twitter ? Curious about it

  14. 1

    Basically everything.
    Fun exchange/feedback from customers.
    Your results (people love results)
    What you worked on everyday.
    Sharing other SaaS tools you use...

  15. 1

    all of the above.

  16. 1

    All of the above!

    I always find the most interesting reads are explanations about overcoming major challenges/setbacks in all aspects of the business, not only the technical problems.

Trending on Indie Hackers
How are you handling memory and context across AI tools? User Avatar 112 comments Do you actually own what you build? User Avatar 66 comments Code is Cheap, but Scaling AI MVPs is Hard. Let’s Fix Yours. User Avatar 34 comments I Think MCP Will Punish Thin API Wrappers User Avatar 27 comments What AI Is Actually Changing in IT Certification Prep User Avatar 19 comments Cloud vs Cybersecurity Certifications | 2026 Path Makes More Sense User Avatar 18 comments