1
0 Comments

The build in public stack I actually stuck with after trying almost everything

Hey IH! 👋

Over the past month of building BuildTrail publicly, one question has come up again and again:

"What tools do you actually use to build in public?"

At first, I kept adding more tools.

  • Notion

  • X

  • Indie Hackers

  • Analytics

  • Loom

  • A newsletter

It felt productive.

In reality, I was spending more time managing my workflow than actually documenting my journey.

The biggest lesson?

The problem isn't discipline. It's complexity.

Today my stack is much simpler:

  • X for conversations and daily updates.

  • BuildTrail for keeping my startup journey in one permanent place.

  • Indie Hackers for milestone posts and longer reflections.

  • Loom for product demos and launches.

  • Analytics to understand what users are actually doing.

  • A newsletter once you've built an audience that wants to hear from you.

Everything else is optional.

I wrote a longer breakdown of why I use each tool, where each one shines, and where each one falls short.

Full article:
https://www.buildtrail.app/blogs/best-build-in-public-tools

I'd genuinely love to hear from this community:

Has your build-in-public stack changed over time?

Is there one tool you couldn't build without?

posted toAvatar for product Buildtrail
Buildtrail