Welcome to LeadHunter

LeadHunter is an outbound research and outreach platform for small teams running their own go-to-market. You bring a product you want to sell and a rough idea of the customers you want to reach; LeadHunter turns that into:

• A scored database of accounts (companies, organisations, venues) that match your Ideal Customer Profile (ICP).
• Per-product fit scores with typed reasons — a 0–10 number, a category label, and 2–4 concrete justifications, so you know why the AI thinks an account is a 9/10 vs a 4/10.
• Campaigns you run against those accounts, with built-in safeguards so you don’t accidentally cold-pitch a customer, a competitor, or your investor.
• A manual communication log across email / LinkedIn / Instagram / X / WhatsApp / phone, with AI drafting and auto-translation between your language and the account’s.
• Inbound attribution when the lead came in through Google Ads, Instagram DMs, referrals, or any non-outbound channel — start them at the right lifecycle status, with the UTM parameters and thread URLs preserved for later analysis.
• Cost-of-acquisition tracking per campaign — ad spend, agency fees, labor hours go in; CAC per outreached / responded / closed customer comes out.

How the pieces fit together

Company  ──►  Product  ──►  Campaign  ──►  Accounts (scored)
   │             │              │              │
   │             │              │              └─►  Conversations · status promotion
   │             │              │
   │             │              └─►  Costs + CAC
   │             │
   │             └─►  ICP (ideal customer profile)
   │
   └─►  Custom fields · Saved filters · Team members

• A Company is your tenant — your team, your data, your accounts. One user can have multiple companies.
• Inside each company you define one or more Products: what you’re selling, who it’s for. The Product carries the ICP.
• Each Product can run multiple Campaigns — same product, different audience or angle.
• Accounts are the organisations you care about. The same account can live in multiple campaigns, but is scored once per product — adding it to a second campaign of the same product doesn’t re-score it.

Outbound, inbound, and the same database

LeadHunter started life as an outbound tool — you research, you find, you reach out. The same database now also tracks accounts that came in through inbound channels (Adwords clicks, Instagram DMs, referrals, event introductions). Inbound accounts start at the contacted lifecycle status automatically since they’ve already reached out to you, and the marketing-channel attribution carries through to the funnel and CAC stats. See Track inbound leads.

Who LeadHunter fits

The product was built around a few specific kinds of operator:

• Small teams running their own outbound — one to five people, doing the actual reach-out themselves, with strong AI assistance but real human judgment on every account.
• Outbound agencies running multiple clients — one Company per client, fully isolated, with per-Company stats and CAC.
• Founders going to market — early days, narrow ICPs, every conversation matters, the funnel and CAC stats inform pricing and positioning decisions.

It’s less of a fit for large sales orgs with established CRM workflows, mass-outreach operations that send identical templates to thousands of leads, or anyone looking for an off-the-shelf contact database to query.

What LeadHunter isn’t

A few deliberate non-features so you know what to expect:

• Not a sending engine. You keep sending through email / LinkedIn / Instagram / WhatsApp / phone yourself; LeadHunter logs the exchange. Sending well across every channel is a different product.
• Not a contact database. LeadHunter doesn’t ship with a pre-loaded index of millions of companies. You bring accounts (CSV / Google Maps discovery / one-off lookup) or capture them inbound.
• Not a marketing-automation platform. No drip sequences, no scheduled blasts, no automated A/B tests. The point is that every account gets human judgment.
• Not a CRM replacement if you need invoicing, contract management, support tickets, or anything past the “from prospect to first conversation” loop. LeadHunter complements those tools — it doesn’t try to replace them.

What you’ll do today

• If you want the bigger picture first, read How LeadHunter works — the end-to-end flow from empty workspace to operational outbound program, with what to expect at each phase and the rhythm you’ll settle into after the first cycle.
• If you’re ready to dive in, follow the Quick start. Fifteen minutes from sign-in to scored accounts.
• If you want the data model in detail, the Concepts section explains the status lifecycle, dedupe stack, and merge semantics that keep your database free of duplicates.

Zero duplicates, on purpose

The most important thing to know about LeadHunter: it refuses to create duplicates. Every import path, every research pass, every API post runs through the same five-level dedupe stack — Google Place ID, name + city (exact, post-normalisation), phone, website domain, fuzzy name within the same city. The first four auto-merge into the existing row; the fifth surfaces for human review. Re-importing the same list twice is safe.

When duplicates do get merged, every unique field from every duplicate is preserved on the survivor — LeadHunter never silently overwrites. See Merge duplicates for the full story.