I usually get a few messages from makers during the week asking if I could hunt them.

Short answer: I don't currently hunt (but maybe in the future)

I always aim to raise topics and questions relevant to startups/products and my personal endeavors that others might relate to.

The threads usually start with an intro to the topic, my experience, and, lastly, ask others to share their experiences. I try to structure these parts into clear, error-free sections so that they are easy to read. I have never used AI, for what it's worth.

I'm currently building a tiny tool to reduce churn for SaaS products using Stripe, something super simple:

But before I go too far, I m genuinely curious...

How do YOU handle cancellations right now?

• Do you ask why they leave to improve your product?

• Do you offer a discount? A pause?

• Or just let them go?

Hey everyone!

After years of building digital tools, I ve finally decided to launch one of my creations here on Product Hunt. As a developer, I usually feel more at home writing code than doing public launches but this time, I want to do things right.

Hey Product Hunt!
This morning I launched my first solo product ever: Controol a minimalist finance app built around one idea:

Know how much you can spend, not just what you already did.

No team. No paid ads. No launch list. Just late nights and building something I personally needed.
I honestly didn t expect much but hours later, it made it to the Top 5 of the day

The feeling? Wild.
Strangers are connecting with the mindset behind it, and it's been amazing to read their comments.

The perfection of creations generated by artificial intelligence makes it difficult to distinguish fiction from reality.

The precision of AI images has advanced to the point that even professionals (graphic designers, video-makers) are sometimes not 100% sure of their authenticity.

Let's get to know each other, but in a more challenging way Only 3 words to describe yourself.

No more, no less.

I ll go first

Hello PH folks

I m a second-time founder, currently building ResearchGenie to help cut down the time and effort it takes to find, decode, and act on research and insights.

I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:

• Write down a simple problem statement: "what am I trying to solve?"

• Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"

• Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.

• I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.

• I take the output and paste it into my notes. I then give it to Cursor.

• Once in Cursor, I create a new project folder and got at it!

Curious what everyone else does and if you've experience any things to avoid or must do

I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:

• Write down a simple problem statement: "what am I trying to solve?"

• Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"

• Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.

• I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.

• I take the output and paste it into my notes. I then give it to Cursor.

• Once in Cursor, I create a new project folder and got at it!

Curious what everyone else does and if you've experience any things to avoid or must do