A lot of us are enjoying this new era of building.
With AI and vibe coding, it has never been easier to turn an idea into something real. You describe a feature, wait a few seconds, and something appears on the screen. Then you fix it, polish it, add another feature, and suddenly you feel like you’re making serious progress.
And honestly, that part is amazing.
The dangerous part starts when you ask AI what it thinks about your startup.
If you ask:
“Is this a good idea?”
AI will often hype you up.
It will tell you the market is big, the product is differentiated, the timing is right, and a strong Product Hunt launch, a Show HN post, or one viral Reddit thread could change everything.
So you keep building.
Then, when doubt finally kicks in, you ask:
“What’s wrong with this product? What features should I add?”
Now AI gives you a completely different kind of confidence trap.
It lists 47 problems, 32 feature ideas, 18 positioning angles, 9 onboarding improvements, and a roadmap that makes you feel productive again.
So you keep building.
But you still haven’t talked to customers.
That’s the trap.
AI makes it easier to build, but it also makes it easier to avoid the uncomfortable parts of building a business.
Talking to users is uncomfortable. Sharing early is uncomfortable. Asking people to pay is uncomfortable. Hearing that nobody cares is uncomfortable.
Prompting AI for another feature idea is comfortable.
And comfort is dangerous for a startup.
The problem is not that AI is useless. The problem is that AI is often a completion engine for your current emotional state.
If you sound excited, it gives you reasons to be excited.
If you sound worried, it gives you reasons to worry.
If you ask for features, it gives you features.
If you ask why your startup will win, it gives you a victory speech.
But your customers do not care how encouraging your AI assistant was.
They care whether your product solves a painful problem.
My suggestion: before building more, nail down the one feature that creates the most value.
Not the most impressive feature.
Not the most fun feature to build.
Not the feature AI says will make your product “10x more compelling.”
The one feature a real person would care enough about to try, use, share, or pay for.
Build that.
Then shift your energy to distribution.
Talk to people. Share the product. Ask for feedback. Email potential users. Talk to your neighbor. Post in communities. Be awkward. Be a little cringe. Be the person who is clearly trying to figure it out in public.
Because that is where the truth is.
Not in the AI chat where every answer sounds polished.
In the replies.
In the silence.
In the confused feedback.
In the “I don’t get it.”
In the “Can it do this instead?”
In the “I would pay if it solved this specific thing.”
That is where the product gets real.
So after giving that advice, let me be that guy.
I’m building debate.tellodb.com because I kept running into this exact problem: AI was too agreeable.
The feature I’m testing is called Devil’s Advocate.
Instead of asking one AI whether your idea is good, you can make multiple LLMs argue about it. Ask what feature to build, what not to build, what assumption is weak, or why your product might fail.
The goal is not to make AI negative.
The goal is to make it less eager to make you happy. Get where LLMs disagree.
Because your startup does not need more encouragement. It needs sharper questions.
And honestly, I’d love feedback on whether this actually helps.
In short:
AI can help you build faster.
But if you let it replace customer conversations, it can help you build the wrong thing faster too.
The goal is not to make the AI happy.
The goal is not to make you happy. You should be grinding up all night uncomfortable from all the suggestions you are getting that you feel are making you feel less smart.
The goal is to make customers happy.
And that part is still uncomfortable, messy, and hard.
AI can make the work look easy.
It isn’t.
The speed part is what makes this tricky. AI makes it possible to build a feature in hours, so it becomes very easy to mistake progress in development for progress in the business. I think the harder discipline now is deciding what not to build until a real user gives you a reason. Faster execution is valuable, but only after the problem is clear.
Love the concept of the Devil’s Advocate feature on debate tellodb. Making LLMs argue against each other to surface blind spots is a brilliant way to weaponize that natural bias. A startup doesn’t need a hype man; it needs a stress test. Definitely checking this out!
Thanks, glad you loved it!
That's great advice for someone like me who is looking to work on an idea. Also the platform looks really cool. Thank you so much for sharing.
Glad it was helpful and you liked Debate TelloDB, if you want any help with your startup journey ping me!