
Lead Hunter Pro
Find them,call them,email them.
Lead Hunter Pro turns a trade and a city into US contractors worth calling, each with the reason, the source and the date.
The hard part isn't finding companies. It's never letting the AI make a fact up: every claim in a call or an email has to point back to a page.
- Year
- 2026
- Role
- Design, build, deploy
- Stack
- FastAPI · React · SQLite

AI proposes, rules decide.
- Identity
Who is this company, really?
Every company gets a stable internal id. The website is only a way to look it up, because domains change and two companies can share one.
- Evidence
A search result is not evidence.
Only a fetched page that names the company is stored, with its address and date. A page about a different company is never stored.
- AI call 1 · Events
“Won a bid” is five different things.
The AI reads the evidence and proposes events: bid submitted, low bidder, recommended, awarded, signed. If the stage isn't clear, it stays “needs resolution”, never the weakest guess.
- Rules · Signal
The score is arithmetic.
No AI here. Direct evidence, an official source, a second independent source and recency add points; a contradiction takes four away. 12 or more is a strong signal.
- AI call 2 · Gate
The AI suggests a need. A gate checks it.
The second call may not search the web again; it only reads the signals. Then a plain rule-based gate lists every requirement that isn't met.
- Outreach
The first line writes itself.
The email opens with something true, recent and sourced. If no signal passed the gate, there is no personal line: the email stays honest instead.
Unknown is not no.
Every research question ends in one of four answers, and the code refuses to merge them. “We couldn't look” must never turn into “there's nothing there”.
- NOT_FOUND
We looked. It isn't there.
The county lists no award for this company.
- NOT_ACCESSIBLE
We couldn't look.
The portal answered 403. That says nothing about the company.
- NOT_VERIFIED
Someone says so.
A directory mentions it, but no primary source confirms it yet.
- VERIFIED
A source names them.
The award page itself names the company, with a date.


Phone numbers from the source.
Numbers come from state licence boards, a fixed list of all 50 states. If a board blocks one way in, the prober tries the next, so a single 403 never writes a state off.
On the call sheet, the AI only picks a sentence from a fetched page. What you read is the exact excerpt, never a paraphrase.
- 1bulk_fileWorks · kept
- 2open_data_apiNot needed
- 3xhr_jsonNot needed
- 4html_form403 · the old reason it was “dead”
- 5pdfNot needed
Dead only on a true 404 · blocked → next path · exhausted → re-tried in 30 days
Nothing goes out unchecked.
Before an email leaves, an independent checker scores it out of 110 and any hard finding blocks it. Then the sender itself is checked.

- Quality checkScored out of 110 by code, not by the AI that wrote it. Any hard finding blocks.
- Spam wordsChecked before scheduling, not after a bad week.
- Recipient preflightProves the address shape and that the domain takes mail. Only a real bounce proves a mailbox is gone.
- Sender holdThree failures in a row and the account stops sending until someone looks.
- No quiet swapsA deleted sender is never replaced by another account just to clear a queue.
Audited, limits included.
- Limit · Research
Two big runs stopped short.
119 of 150 and 23 of 150 targets were saved. A saved result isn't counted as a qualified email.
- Limit · Sending
93 emails wait on held senders.
Their senders stay held until the original account is recovered. The queue isn't cleared by swapping accounts.
- Limit · Tooling
Four build-tool advisories remain.
The suggested fix brought back 12 worse ones, so it was rejected. Everything that runs in production audits clean.
Built with FastAPI and React on SQLite, one database per concern, behind nginx on Ubuntu, with a local AI model reached over a verified SSH tunnel.
Built together with Hanzlah Kamboh · thank you


