1 comment

[ 2.9 ms ] story [ 13.4 ms ] thread
I built a search intelligence tool with AI and vibes. The vibes ran out in 30 minutes. Here’s what happened.

It started as a Claude artifact. Hardcoded queries for topics I track closely, auto-refreshing regularly. It worked, but lacked flexibility.

So I upgraded to Claude Code. Built a frontend and a backend. On-demand search, multiple API calls, trend charts, and AI summaries.

Then I hit a wall. 30 mins in I was out of API credits.

My prototype was burning API calls in ways I never imagined. It had no real data architecture (just vibes ).

I described features, not a system. Claude Code built exactly what I asked for. The architecture was completely on me.

The unlock: SerpAPI. One clean API that returns real-time search data with a free tier that's actually usable. Once I had that, everything fell into place.

I took the refined prompt and plugged it into a couple AI builders.

Same prompt, different outcomes:

1/ bolt.new got me moving fast, but stalled when I pushed it.

2/ Lovable got me to a working prototype in the first session. A couple more and I now have something sharable.

A week of building at night. One avoidable mistake. A tool I now use every day.

→ Live site: https://noas-search.lovable.app/

→ Git repo: https://github.com/noashavit/noas-search

Type in any keyword, topic, or person to get:

1/ AI analyst overview

2/ Search trends

3/ Most relevant search results

4/ Most recent LinkedIn posts about Topic / by Person

Just bring your own SerpAPI key (free).

I'm sure there's a lot to improve and would love the feedback! What would you have done differently?