After our first launch on Product Hunt, our team spent a little over a month upgrading the product. There were major changes to the UI and several new features added, so the process took time from discussions and redesigning the interface to testing, fixing bugs, and updating AI prompts.
We re also a very small team, so everyone had to push themselves to give 200%. Time and resources are limited, and at the same time, we also had to work on securing funding for the next six months to keep the team running and continue developing the app.
Most people are using AI wrong and I was one of them.
For the first year, I used AI like a fancy Google. "Write me a product description." "Summarize this." "Give me 10 ideas for X." Useful? Sure. Transformative? Not really.
Our team is planning to launch a new version of our product on Product Hunt next week, after a period of optimization and improvements. As we get closer to launch day, I realize there s a lot to prepare, and I m curious about how other teams usually approach this process.
So far, here s what we ve been focusing on:
Most importantly, making sure the product works well and delivers real value
Continuous testing to ensure performance and stability
Designing clean and clear product screenshots
Preparing a summary of what s been updated, fixed, or optimized
Writing launch content (tagline, description, first comment, etc.)
Maintaining good health and a stable mindset for the launch
Expanding our network and connecting with other makers
At the beginning, my reason was very simple: I needed a job and I genuinely liked the product.
I graduated with a Marketing degree, but I never felt like I belonged in agencies or similar environments. It just wasn t for me. At the same time, I didn t have much experience in tech either. So I took a leap of faith and applied for a Customer Support role, almost blindly.
The early days were tough. I had no technical background, no real understanding of how apps were built, and everything felt overwhelming. But the product itself became my motivation. I started from the most basic things: learning simple technical terms, understanding how an app is structured, and slowly exploring how everything works behind the scenes.
Every product dashboard I've ever seen tracks the same things: DAU, session length, retention, engagement loops. All of them answer one question is the user coming back?
But lately I've been thinking about a different question: is the user outgrowing us?
Many people have told me that being part of Gen Z comes with advantages we have time, energy, and plenty of opportunities to shape our careers in the AI era. And I do feel lucky to have grown up with technology, to have had early exposure and opportunities to learn and explore it.
But the AI era feels different. The shift is not only new, it s happening at lightning speed. Before I ve even fully adapted to working with AI, we re already seeing waves of layoffs where human roles are being replaced or reshaped by AI systems. And honestly, that creates uncertainty and anxiety not just for me, but for many people around us.
What are three things you re grateful for every day? Are they the same, or do they change over time?
For me, the three things I m grateful for most days are:
Having the health to keep working
Having work that I can pursue and grow with
Having a family that cares about me and supports me from behind the scenes
Of course, each day brings different moments, small wins, or reasons to feel grateful. But at the core, it often comes back to the same things: health, work, and family.
There's something counterintuitive about building an AI product in the mental health and self-awareness space: if you're doing it right, your users should eventually need you less.
Most product teams optimize for stickiness. More sessions, more time in app, more daily returns. But at Murror, we've been wrestling with a different question what if the goal of our product is to help someone build enough self-understanding that they don't need to open the app as often?
There s one thing we re really good at as builders: we constantly try to improve our work and our product every single day. But an honest question I often ask myself is: do we put the same effort into updating ourselves?
At Murror, we re a small team of around five people. For me, it s important not only to improve the product, but to continuously update my mindset, skills, and learnings and share them openly with the team.
I try to communicate everything I learn, ask questions, and clarify problems as much as possible, so the product we re building becomes better, clearer, and more convincing for our users.
To do that, I try to practice a few things consistently:
