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
I like the idea but after looking at the website I get the impression that you are limiting yourself by focusing your marketing messaging too much on the corporate or "builder" use cases for your product. I think there are many other use cases for ProdShort including creating short clips of remote auditions / casting calls and collaborative content creation for creative teams like comedy troupes or those involved in theater. I could even see ProdShort being used by those teaching improv to quickly create summary / highlight videos of improv practice sessions hosted through online meetings. I also think you could do more to demonstrate your product's potential accessibility use cases given that it features AI-powered captions. Good luck with ProdShort. I'm rooting for you!
ProdShort
@jay_enn Ohhhh wooow, I would love to see people using Prodshrot in different usecases. To be honest, we speak to builders because we are builders our selfs and we built it to solve our own problems. I never did a remote auditions.
Are you open to discuss one of these use cases on a call ?
Love this. Building in public sounds great until you realize content creation becomes a daily burden. Turning real founder conversations into authentic posts is a very smart solution.
ProdShort
@combajt When I try to create content, I film myself multiple times, try to make it better, repeat, forget... It just takes all the time, I am supposed to be building.
ProdShort
@combajt Appreciate that. Most insights already happen in conversations. Are you building in public?
Build Check
If it drives the traffic you're looking for and you can also vibe-code your product... it's a deal for me
Something that helped me reframe this: for subject-matter experts, "build in public" does not have to mean daily content. It can mean publishing the artifact itself.
I build financial model templates from real deal work — project finance, M&A valuation, mortgage comparison. Each template is a timestamped, public artifact of my expertise. When I publish one on Eloquens, that is build in public. The work is the content. I do not need a separate thread explaining what I am building because the model itself shows it.
The daily-content version of build in public works well if distribution is your competitive advantage. But if deep expertise is your moat, the artifact itself carries more signal than a thread about making the artifact. A CFA with a Top-3 FMWC finish publishing a deal-tested project finance model is saying more in that one release than 30 posts about "what I am learning."
The practical answer to "without making it a full-time job": ship the thing, not the commentary about the thing. The commentary is optional and can be asynchronous — a Quora answer here, a Medium article there, once every few days. But the artifact is the core. Everything else is distribution on top.
How do you handle colleague privacy during these calls? It is cool that the content stays authentic, but you don't always want internal discussions to go public in raw form. Still, I like the idea of automatic progress documentation. It really removes the hurdle to start sharing wins. If you can easily filter what goes into a post and what stays behind the scenes, this is a must-have for any founder.
the authenticity angle is what makes this work honestlyt. most build-in-public content rn is either fake (people writing posts from scratch about 'lessons learned' that never happened) or skipped entirely cuz writing it feels gross.
pulling it from real conversations sidesteps both problems at once. the source material is already true, ur just surfacing it
Nice idea, building in public is powerful, but it only works when it doesn’t start feeling like a second job on top of building. Keeping it real + low effort from actual work sounds like the right direction. curious how you’re making sure it doesn’t turn into “content first, building second” over time?
Love the idea of documenting real work instead of forcing founders to “create content” from scratch every day. Feels much more authentic and way more sustainable.