1
1 Comment

Building in Public: Why You Should Try (Even If You Might Fail)

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.

Why share the messy middle?

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:

  • Normalize the reality that building something new is confusing.
  • Create a trail of lessons for others to follow (or avoid).
  • Turn potential failure into value for your community.

Failing in private is safe, but failing in public is generous at least from my perspective.

The invisible work nobody talks about

When you decide to build in public, it’s not just about tweeting milestones. There’s hidden work everywhere:

  • Writing to strangers daily, hoping they’ll give your product a chance.
  • Keeping your app stable while new users test it.
  • Posting updates even when engagement feels low.
  • Checking metrics without letting them define your mood.
  • Balancing family, work, and mental health on top of it all.

This is the part that rarely shows up on glossy “launch” stories, but it’s the part most people need to see.

Why others should try it too

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:

  • Share your first steps, even if awkward.
  • Talk about your mistakes, so others don’t repeat them.
  • Document your lessons, so future you can look back and learn again.

The act of showing up consistently is more important than the outcome, because every honest attempt creates ripples of inspiration.

How this connects to Deeditt

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.

Final thought

If you’re building something, consider doing it in public. Yes, it takes energy. Yes, it feels risky, but it might also:

  • Inspire someone who needed to see the real process.
  • Teach a stranger through your mistakes.
  • Build trust far deeper than polished announcements ever could.

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.

posted to Icon for group Building in Public
Building in Public
on August 18, 2025
  1. 1

    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?

Trending on Indie Hackers
AI runs 70% of my distribution. The exact stack. User Avatar 147 comments I'm a solo founder. It took me 9 months and at least 3 stack rewrites to ship my SaaS. User Avatar 137 comments Show IH: I'm building a lead gen + CRM tool for web designers targeting local businesses without websites — starting with Spain User Avatar 79 comments I built a URL indexing SaaS in 40 days — here's the honest story User Avatar 58 comments We could see our AI bill, but not explain it — so I built AiKey User Avatar 25 comments AI coding should not turn software development into a black box User Avatar 11 comments