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
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.
A lot of people talk about “building in public” like it’s supposed to become another full-time job. I think the trick is keeping it simple.
I don’t try to post every little thing anymore. I just share small updates while I’m already working — traffic changes, things that failed, tools I’m testing, or something I learned that day.
Most of the time, a quick honest update works better than spending hours trying to make the perfect post. People connect more with real progress than polished content anyway.
The part that resonates most is the "forcing function" angle. Build in public stops working the moment it feels like a second job, and most people hit that wall pretty fast trying to manufacture daily content from scratch.
What I've found useful is treating calls and async discussions as the raw material, not the finished post. The stuff that actually gets traction anyway tends to be the unpolished moment where someone said something that changed how you think about the product. Hard to fake that, and honestly you shouldn't have to.