u/Imaginary-Box8650

We launched beta for our project a few days ago. We actually used our own tool to find our very first users here on Reddit.

Since we built this to solve our problems, we honestly thought it would work perfectly for everyone else. We were wrong.

As soon as the feedback started coming in, it was a huge reality check. Users instantly caught things we were completely blind to.

One users pointed out that the landing page link looked weird and the Tex sounded like it was generated by AI. That hurt to read, but they were totally right. Another user found a bug in the signup form. After typing one word in the email box, the box lost focus. You literally had to click the screen again just to keep typing. We tested that form so many times and never noticed it. Also, the platform currently requires an active business website to signup, and users told us that is way too restrictive.

Looking back at past projects, used to spend months trying to make everything perfect before showing it to anyone. It was exhausting. Most of those creations never even launched because we were abscesses with making them perfect.

Lesson learned. Perfect is a trap. If we hadn’t shipped this early, we would still be polishing a pegs that people couldn’t even signup for properly.

How do you stop yourself from overthinking and to make everything perfect before you launch??

I’ve been into vibe coding for about a year now. My first project was a crypto portfolio tracker called Consider (it’s not active anymore).
When I started, I was using GPT for planning and Gemini+Claude for the actual coding. I had a few failed startup idea attempts behind me, so I moved fast. I had validated the idea, I was building what I had in my head.
But I noticed something while working with GPT: it kept adding features. Build, build, build never stop. I wanted a really controlled system because I cared a lot about users seeing accurate balances- so I told GPT that, ant it went full over engineering mode. Eventually the app got to a point where almost worked because of all the “security ” layers it had added.
After fixing all that, I wanted to focus on distribution and marketing Reddit felt like the right place to start. But I was new to it finding right posts took hours, and messages I was sending weren’t landing.
So my cofounder and I built a small tool to fix that. Something that relevant Reddit posts, scores them by intent, and suggests how to approach them. We tried it and my comments and DMs started getting actual responses.

Then my cofounder stopped and said: “this tool is more useful than Consider

That line changed everything. Consider had become bloated and over-built. We decided to put it on hold focus on the tool instead.
Learning from the past, we turned our tool into a product in exactly 3 days.

Here’s what this whole journey taught us:
1. Set constraints and rules for your AI while vibe coding. If you just say “keep building” without boundaries, it’ll drag you into feature hell. Define temperature, output format, what it should NOT do before you start.

2. Short out your distribution channels before you launch. When the product is ready, you should already know how people will find it. Leave that question for later and you’ll ware months.

3. Keep it simple-keep it small- build distribution-then optimize. Optimization comes last, not first.

4. Sometimes your internal tools are more valuable than your main product. Just like slack. What you build to solve your own problem might solve someone else’s too. The sooner notice that, the better.

5. The wrong AI used wrong way will take you in the wrong direction. How you use AI matters as much as which one you pick. Claude + structured prompts + .md files = consistent, predictable output.

FindEvo is in beta now

What’s actually worked for you on the distribution side of your vibe coding journey??

So we thought our beta was flawless. Turn out, Reddit users had other plans.

I did it my first project is launched