mask_off

@impeculiar1b Hi

If you are still under 5k followers Say hi 👋 Let’s follow you

@hellojakejohn That's the most underrated take I've read today. The 'why behind the stack' is exactly what I'll try to capture. Just followed you, would love to follow your journey too 🚀

Both. Although, nobody documents the thinking before the building. Which AI model, which voice API, whether to allow profile uploads... none of those are tech decisions. They're margin, brand, and legal decisions wearing a technical costume. Skip the blueprint, pay for it later.

I'm starting to build in public. 🚀 Every lesson, mistake, and win. I'll be documenting it all on X. No filter. Just the raw journey of building a SaaS from scratch. Quick question for you: what's the #1 thing you'd want me to document? → The technical side (stack, architecture, code) → The business side (marketing, revenue, customers) → Both equally Drop your answer in the comments — it'll shape what I share. 👇 #BuildInPublic #SaaS #IndieHacker #Founder #StartupJourney #Entrepreneurship

@linkedgrow_ai That's exactly the mindset I want to bring to this the messy middle is where the real lessons are. No sugarcoating, just what actually happens 💪 Just followed you, would love to follow your journey too. Let's build in public together! 🚀

@VibeCodingNow Document the mistakes most people hide. That's what makes build in public worth following. Everyone shows the wins, but the messy middle is where people actually learn.

@RoyPaclio 100% agree The legal side is something most builders skip until it bites them. Really appreciate the reminder, adding it to my list of things to document openly 🙏 Just followed you, love to keep an eye on what you're building too. Let's keep each other accountable! 🚀

@VibeCodingNow Love the build in public approach. One thing I wish I documented early: the legal side. Set up your Terms and Privacy Policy before launch. It's boring but stops app stores from rejecting you or investors from panicking. Show that struggle, too.