About

Founder & CEO at GoNoGo (gonogo.team) — the first AI platform that validates startup ideas through real voice conversations, not text forms. Our AI agent interviews founders like an experienced investor would, runs competitive research, and generates analytical reports — all from a 15-minute voice session. Previously built Lifeline (mylifelineapp.com). Passionate about AI, voice technology, and helping founders avoid building products nobody needs. Always happy to connect with fellow makers and startup enthusiasts

Badges

Buddy System
Buddy System
Pixel perfection 💎
Pixel perfection 💎
Bright Idea 💡
Bright Idea 💡
Gemologist
Gemologist
View all badges

Maker History

  • GoNoGo.team
    GoNoGo.teamValidate your startup idea through a real AI voice interview
    Jun 2026
  • Neural Bordello
    Neural BordelloPay $1 for life advice from retired AI models
    Jan 2026
  • Lifeline
    LifelineVisual memory journal with emotion auras and AI that listens
    Dec 2025
  • 🎉
    Joined Product HuntNovember 25th, 2025

Forums

•

3h ago

Do you use one AI model for everything or switch when things get messy?

For basic UI tweaks and standard CRUD endpoints lighter models are great because they keep the momentum going instantly.

But the second a weird async bug or race condition pops up those fast models usually just loop in circles until I manually switch to a heavy reasoning model.

•

3h ago

Does building with AI save you time or just move the work to debugging?

I recently finished shipping a project using mostly AI prompts. Getting the basic app running took almost no time which was great but getting it ready for real users was a completely different story.

I ended up spending days catching small mistakes that the agent missed like wrong timezone math missing input rules and broken uploads.

You really cannot trust it when it says a bug is fixed until you test it yourself.

What has been your biggest time sink when building products with AI tools?

•

5h ago

when do you switch from a fast cheap model to a heavy reasoning model mid-session?

for standard UI components and basic CRUD endpoints, lighter fast models feel instant and keep my momentum going without waiting thirty seconds per reply.

the moment a tricky async bug or state loop shows up, those same fast models start going in circles until i switch over to a heavier reasoning model.

do you stick to one model for the whole build or swap them depending on the task?

View more