Re:Show HN: AI agents run my one-person company on Gemini's ...
by ppcvote on Tuesday March 10, 2026 @11:29AM
(#47324602)
The domain + company name trick is solid — wish I'd known that earlier. And agreed on parsing page source for tech stack detection, it's surprisingly reliable and the cost is literally zero.
The last_engaged timestamp filter is a good catch. We had a similar issue with our scheduling system where a stuck "busy" state caused the entire pipeline to freeze for over a day. Ended up adding a simple guard: any early exit from a busy state must release the lock first. Same philosophy — one cheap filter prevents a cascade of wasted work.
Also found that parsing script/meta tags directly from the homepage beats any third-party data source for tech stack detection. HubSpot, Salesforce, Stripe, Intercom all leave distinctive fingerprints in page source. Zero API calls, zero cost.
Built something similar for B2B prospecting (batch mode — 50 companies at once). Ended up with almost the same architecture: HTTP scraping at 0 LLM tokens, LLM only for the synthesis step at the end. The bottleneck is rate limiting from the target sites, not the LLM.
One thing I'd add: on the engagement loop bug you mentioned — I ran into the same thing early on. The fix was processing only items where a "last_engaged" timestamp was >N hours ago before feeding to the agent. Simple filter, saved a lot of wasted runs.