As makers, we often wait until things are polished before showing them to the world. We want the perfect landing page, the perfect pitch, the perfect growth curve, but here’s the truth: perfection never arrives. What we do have is a choice—to build in silence, or to build in public.
At Deeditt, we recently made a decision to share a challenge openly: bring 100 active users in 4 months. No ads, no growth hacks. Just honest outreach, writing, conversations, and consistency. It’s not glamorous, it’s not guaranteed, but it’s real.
Because the future is uncertain. Some people believe the idea is great, others say it won’t work. Both might be right. None of us know for sure.
And that’s exactly why documenting the process matters. By showing the uncertainty itself, you:
Failing in private is safe, but failing in public is generous at least from my perspective.
When you decide to build in public, it’s not just about tweeting milestones. There’s hidden work everywhere:
This is the part that rarely shows up on glossy “launch” stories, but it’s the part most people need to see.
If you’re building something—an app, a newsletter, a community—you don’t need to wait until it’s a success story to share. You can:
The act of showing up consistently is more important than the outcome, because every honest attempt creates ripples of inspiration.
Deeditt itself was born around this philosophy: that documenting experiences and sharing them with others has value beyond likes, vanity, or algorithms.
This challenge—100 users in 4 months—isn’t just about growth. It’s about living the philosophy we’re building into the product. It’s about proving that sharing the journey, with all its flaws, matters.
If you’re building something, consider doing it in public. Yes, it takes energy. Yes, it feels risky, but it might also:
And if nothing else, you’ll walk away knowing you tried—openly, honestly, and without regrets.
Because building in public isn’t just about growth. It’s about generosity.
Reframing building-in-public as generosity instead of growth is sharp — most takes on this are still ROI-coded. Where I've struggled is calibration: the messy middle builds trust, but sharing half-baked decisions before I'd actually committed has also burned me with users who treated them as roadmap promises. How do you draw that line?