Zora

Founder's Journal - 8/25/25

Happy Monday Everyone - welcome to the third edition of Founder’s Journal! I sincerely appreciate everyone who has picked back up this newsletter or have found it for the first time as we begin our founder’s journey. Coming up on our first month as a real company and every day has been packed with lessons but none may be greater than the one I learned this weekend. While I was away in North Carolina attending a friend’s wedding my phone was blowing up. My cofounders had stumbled upon “Nano Banana”, a new image generation model that showed up in LLM Arena last week and has begun completely shook up the AI race by surpassing the capabilities of more well known models from companies like OpenAI, Google, and Midjourney. So Saturday at 10pm my phone was buzzing with the guys testing the model against our existing pipeline. The texts are coming in fast and furious as they imagine how this will improve the quality and speed to market of our products. Earlier that week I had caught up with a friend who recently sold his company. By all accounts he had succeeded. As a first time founder an exit is far from a guarantee and there are worse things than making your investors happy while getting a nice salary on the other side of it. But as I spoke to him about lessons learned he was quick to say he wish he had done something he was naturally curious about. That when the times got tough (and they did) at least he could find solace in the fact he was passionate about what he was working on. Reflecting on this past weekend and the joy I witnessed as my cofounders went back and forth late on a Saturday I know we’ve caught that lightning in a bottle. The outcome is far from guaranteed but passion is a lubricant for work ethic. It’s a hell of a lot easier to spend countless nights and weekends glued to a monitor when you genuinely like what you’re working on. Anyways enough with the long preamble. Let’s get into the newsletter. The Attention-to-Habit Conversion Framework What if the difference between successful and failed products isn't features, funding, or even market fit - but whether you understand the psychology of human attention versus habit formation? This week I stumbled into a framework that's changing how I think about everything we're building. It started with a simple observation about podcasts and ended up reshaping our entire product strategy. Here's what I learned: You have to build habit-forming products or attention vacuum products. The former becomes part of someone's routine without them thinking about it. The latter demands the person pays attention to it. Attention is the acquisition. Habits are the retention. Most products die because they get stuck in attention mode. They're constantly fighting for eyeballs, constantly trying to be interesting, constantly demanding conscious consideration from users. That's exhausting for everyone involved. The Podcast Model Podcasts demonstrate this evolution perfectly. They usually start as attention vacuums - you discover them through a viral clip, an interesting guest, a recommendation that makes you consciously choose to listen. But the successful ones transition into habit formation. They become part of your morning routine, your commute, your workout. You don't think about whether to listen; you just do. Checkout the stats from Threadguy’s Twitch streams this week. You can see the attention to habit funnel in motion. Why the Music Industry is Struggling This framework explains something that's been bothering me about the music industry. The attention mechanisms are stronger than ever. TikTok, viral dances, rollout campaigns that dominate social media. But nobody habitually listens to artists anymore. Without habits, you need constant attention-grabbing. That's why artists are forced to build brands, create ongoing content, maintain fan communities. Fan clubs work because they're habitual. Members feel a responsibility to show up for their community. They want to feel seen and appreciated. The engagement becomes routine, not effortful. The Product Framework When building your product roadmap, map every attention-grabbing feature to a routine integration point. Ask yourself: 1. What makes someone come back without thinking about it? That's your retention engine. 2. How does this transition from conscious choice to unconscious routine? 3. What community or responsibility elements reinforce the habit? The best products become invisible parts of daily routines. The worst ones constantly fight for attention they'll never consistently win. Operational Lessons from AI-Assisted Development Speaking of attention and habits, I spent this week deep in "vibe coding" - using AI assistants to build internal tools at speed. The results were... educational. The Hidden Cost of Unstructured AI Development Here's what nobody talks about: AI-assisted development can create massive technical debt if you don't structure it properly. Claude wants to build everything from scratch. It generates dozens of files. Without discipline, you end up with a graveyard of code that nobody understands. The Research-First Principle: Before building anything, ask "How would I execute this without new code?" Most problems are already solved. Spending time researching existing solutions saves weeks of development and maintenance. Documentation Through Conversation We discovered something powerful: nobody wants to write documentation, but everyone's happy to talk. So we started transcribing our meetings and decision-making conversations instead of trying to maintain written docs. The result? We have a searchable database of our thinking, our key decisions, our reasoning. No one spends time writing. Everyone benefits from the knowledge capture. The Compound Learning Effect Even failed projects teach valuable skills. This week's "failed" attempts taught me API integrations, vector databases, and MCP (Model Context Protocol) usage that I immediately applied to our next project. Each project accelerates the next, even when the output isn't what you planned. Process Framework for AI Development: 1. Structure before execution - Plan your file organization and version control 2. Research before coding - Identify existing solutions first 3. Version control as sanity preservation - Commit working states frequently 4. Learning extraction - Explicitly capture what each project taught you Everyone Needs Mentors I'm the dumbest person in most of the technical conversations happening on our team right now. That's exactly where I should be. Logan is mastering image modeling at a level that rivals industry leaders. Remy has a creative mind that can see characters and worlds as if they really exist. Lucas is shipping products we never planned to build. Surrounding yourself with people who are better than you in their domains accelerates everyone's learning. Failure becomes growth. Discomfort becomes progress. The Compound Effect of Structured Thinking Whether building products, teams, or processes, the winners will be those who understand the difference between attention and habits, structure and chaos, platforms and features. This week taught me that seemingly unrelated insights compound: - Habit formation principles apply to user retention and team culture - AI development chaos teaches structure discipline that improves all systems - Documentation through conversation scales knowledge beyond individual capacity Your Weekly Questions As you think about what you're building this week: 1. Which of your products are attention vacuums that need habit formation? What routine integration points could you create? 2. What operational processes could benefit from conversation-first documentation? Where are you writing when you should be talking? That’s it for this week. If you found this useful please let me know what you think in the comments and share it with your friends. See ya next week, Austin