For us, it started from something frustrating: creating content felt very annoying and time-consuming. We tried the classic way: scripting, memorizing, filming, editing. But none of it felt authentic. And honestly, it was eating time we needed to focus on other things.

At the same time, we kept reading the same advice everywhere:
"founders should build in public and create content consistently". Easy to say but harder to do in reality. So instead of forcing ourselves to create content from scratch, we tried something simple: recording our own calls and using those moments as content.

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 !!

We all know someone who just keeps building: One more feature, One more improvement, One more thing to fix before starting sales.

And to be fair, it s easy to fall into that loop. Building feels productive, and there s always something that could be better.
But at some point, you have to ask yourself: are you really improving the product or just delaying sales?

From your experience:
When is the right time to stop building and start selling?

When we started building @ProdShort , our first instinct was to make the product "ready" before showing it to anyone. Then we started seeing founders launching much earlier. Sometimes with nothing more than a landing page, just to see if people were interested enough to sign up... or even pay.

It completely changed the way we thought about validation. On one side, launching early gives you real feedback much faster. On the other, launching too early can make people leave before they see the real value of your product.

We're still not sure there's a perfect answer.

When launching a product, offering a free plan feels like the obvious choice. More users, more feedback, lower friction. But at the same time, charging from day one gives you a completely different signal. People who pay often use the product differently, give different feedback, and help you understand what they truly value.

The challenge is that both approaches seem to make sense.

A free plan can help you grow faster. Charging early can help you validate faster. There probably isn't a universal answer and it depends on the product, the market, and what you're trying to learn first.

I was reading this recent @OpenAI article about Gartner naming OpenAI a Leader in enterprise AI coding agents: https://openai.com/index/gartner....

"Software development is becoming more agentic." This is a good summary of what is happening right now. We are moving from AI that helps you write faster, to AI that can take over tasks (actions, use tools, make changes, run tests, and bring the work back for human review). That is a very different behavior.
The article gives Cisco as an example. They used Codex for a big part of their AI Defense platform and reduced delivery time from several quarters to a few weeks.

As founders, calls are part of our daily life. Brainstorming, quick updates, random discussions with the team and there s always value in those moments. But most of the time, all that value just disappears after the call.
By connecting Prodshort to your calendar, it automatically joins your calls and turns them into ready-to-post content.

If you're a founder and want to create content, I'm doing short discussion calls. Let's connect !!

At the beginning, we tried to define pricing early. Plans, tiers, limits: everything looked clear. But once we started getting real users, things changed. Feedback came in. Some features were used more than expected. Others not at all. Sometimes it felt like the first pricing we defined was just a "starting point", not the final one.

From your experience:

Did you change your pricing after launching?

And how important was the first pricing you defined for launch?

The funny thing is that recording content isn't usually the hard part. Most people can talk for a few minutes, record a meeting, or capture an idea as soon as it comes to mind. The part that often stops people isn't creating. It's knowing they'll have to spend hours editing a few minutes of content.

We felt exactly the same while building @ProdShort

At first, we thought our biggest challenge was finding ideas for content. But over time, we realized that editing was the real pain...

What's the biggest thing stopping you from posting consistently?