Everyone says "build in public"… but how do you do it without making it a full-time job?
Building in public is important today. It helps you build a community, get feedback, and create traction around your product. But creating content to share every day — shorts, posts on X, LinkedIn, Instagram — can quickly become boring and very time consuming.
By recording your meetings with Prodshort, you get content ready to share: Shorts, X posts, LinkedIn posts... You keep things authentic, because the AI documents what you actually do and doesn’t create fake content from scratch. Your real progress, your real discussions, your real decisions become things you can share.
It makes build in public much easier. You can share updates about your project directly from your calls: progress, ideas, feedback, small wins... Stay consistent with your build in public without adding extra work to your day !!
Happy to do calls with founders here to create content together 👉 Let's create content !!
Replies
How does ProdShort decide what part of a call is actually worth turning into content?
ProdShort
@miles_anthony2 By default the AI will select the best moments based on what is being said and potential.
In the settings, you can fine tune the prompt and specify the kind of content you want. Example: Find questions, prefer when Miles speaks, When we speak about marketing....
We also have a manual option when you manually select the moments.
Does it require structured meetings, or can messy, casual calls still produce good content?
ProdShort
@hudson_blake It's built to handle messy content, our mission is to document what you do. The best moments online weren't structured. they just happened to be filmed.
But nothing stopped me from doing structured interviews for specific content I wanted to build.
How do you handle sensitive discussions during calls that shouldn't be shared publicly?
What makes this better than just recording a call and manually clipping highlights?
Does it adapt content differently for platforms like X vs LinkedIn, or is it one format?
Do you see this replacing traditional "content planning," or just supporting it?
So, what happens when people build open source software? My project is completely open source. There is a free tier so people can use it for free, alongside a small fee for more interested users. Will I get feedback from the community about my codebase? I did share it. --What does coding in public really mean?? Does it mean that I have to record myself coding, or does it mean that I share my code with the world through open source? I believe that open source is so needed in a world of decentralization. I hope that everyone in the industry can benefit from my product. I hope that people who are far better at coding than I am will take my code and build more useful tools that are also open source.
ProdShort
@dstr88 We love opensource project, and we believe that in many industries, it's a necessity. What are you building ?
We believe there is no proper way to build in public. You just need to share what you want publicly about your experience, if you are coding, share about it, if you are helping people install your tools, record it and share it.
Just share what you do, there is probably other people out there that might find it interesting
ProdShort
Building in public is more about sharing what happens around the project: decisions, problems, small wins !! @dstr88 What are you building?
Batch it share 2–3 real updates per week instead of daily noise. Capture what's you already doing (calls, notes) and repurpose it into simple posts.
ProdShort
@prince__kumar when Prodshort is connected to your calendar, all your calls are already captured, so you can easily batch real moments from your week !!
The authenticity angle is the real differentiator here. Most 'build in public' tools just automate posting but you're extracting from what actually happened. That's a meaningfully different source of truth. Would love to connect!
ProdShort
@faysal_fateh Let make social media authentic, with things that happens in real life
ProdShort
@faysal_fateh The goal is to capture what actually happened and turn real moments into something shareable. Let's connect
@amraniyasser yes, already following you. Followed you on X, lets connect there as well
I just share the stuff that's already interesting without trying to package it. I'm building a recall safety app that pulls data from 41 government sources across 13 countries, so weird things happen naturally. A scraper breaks because South Korea blocks foreign IPs at the ASN level, or I find out the EU's safety database tags the wrong country for half its alerts. Those are the posts that actually resonate. The minute I try to "content strategy" it, I freeze up and nothing gets posted. My rule: if I'd text it to a friend who codes, it's worth sharing. If I wouldn't, skip it.
ProdShort
@maliikb So interesting, so you post mainly about the surprising anomalies you find while building ?
@bengeekly Pretty much. The government data itself is endlessly weird once you start comparing across countries. South Korea blocks all foreign IPs at the network level, so you literally can't reach their recall database from outside the country. The EU's safety portal tags a "notifying country" that half the time doesn't match where the product was actually sold. One of my scrapers broke for weeks and I didn't notice because the database silently accepted the writes but dropped them on a constraint I forgot to update.
You don't go looking for this stuff. It just shows up when you're trying to make 41 data sources behave. Those are the moments where I think "oh, someone would find this interesting" and that's what gets shared.