Research you can check: Bloodhound

A list of names isn't research. Research is useful when every accepted fact has a source, a timestamp and a reason to trust it. That's the standard I built Bloodhound to.

Private buildCode not public. Details on request.

What it does

Bloodhound turns a research question into an inspectable result:

  1. It plans before it searches. No research tool runs until a validated mission plan exists.
  2. It searches and crawls public sources on its own infrastructure, from approved search providers.
  3. It removes duplicates, merging repeated companies and contacts and recording a confidence level for each.
  4. It keeps the evidence. Accepted facts are stored with their source, and every run keeps a manifest of the pages it read.
  5. It exports the results as JSON, CSV or Excel.
  6. It resumes after an interruption instead of starting again.

A private knowledge service lets later runs reuse earlier findings, but only records that are recent and high-confidence.

What it deliberately doesn't do

  • It doesn't get around logins, CAPTCHAs, paywalls or access controls.
  • It respects robots.txt.
  • It refuses private, reserved and local network addresses, and checks again after redirects.
  • A lead only counts as qualified with public evidence and a confidence above the threshold.

Those limits are part of the product, not an afterthought.

Where this helps

  • Building lead lists that match a specific profile
  • Market maps with a source behind every row
  • Founder and company research
  • Public-source due diligence

Anywhere that "here are some names" isn't enough, because someone has to decide what to do with the answer.

Got a task you do every week? Send it to me.

Describe it in a couple of sentences. I'll tell you honestly whether it's worth automating and what I'd build. You don't pay anything unless it saves you time.

Replies in English or Romanian.