Lead sourcing
Ten job boards queried in parallel, normalised, then deduplicated on external job ID, employer LinkedIn URL, and company + title + state.
NeuraLeads pulls from ten job boards, then spends the rest of its run deciding what never leaves your mailbox — three-layer dedup, a company-size gate, seven validation providers, and ten ordered checks at the door.
Self-hosted or managed. No per-seat pricing.
10 job boards, queried in parallel
external job ID → employer LinkedIn → company + title + state
−1,240over headcount ceiling, excluded industry, or confidential employer
−1,948contacts discovered, then every address verified before it can queue
−1,430suppression, cooldown, per-company cap, fatigue, domain throttle
−440Stage names, provider counts and the 30/mailbox/day ceiling are the product’s real configuration. Volumes are illustrative and vary by ICP.
The pipeline above isn’t a marketing diagram — it’s the actual architecture. Here is what each stage ships with.
Ten job boards queried in parallel, normalised, then deduplicated on external job ID, employer LinkedIn URL, and company + title + state.
Drops confidential employers, anything over your headcount ceiling, and excluded industries before a single credit is spent on enrichment.
Waterfall enrichment across seven providers, capped at four decision-makers per company per role so you never carpet-bomb an org.
Every address verified before it can queue. Only addresses that come back Valid are ever eligible for outreach.
Ten ordered checks — status, suppression, validation, cooldown, per-lead limit, company cap, fatigue, domain throttle — on all four send paths.
Multi-step sequences with wait and condition branching, A/B variants with chi-squared auto-optimisation, spintax, and per-contact timezone windows.
Peer-to-peer warmup between your own mailboxes, SPF/DKIM/DMARC verification, and continuous IP and domain blacklist monitoring.
Replies threaded by Message-ID chain, categorised by intent, with sentiment scoring and drafted responses held for approval.
Seven-stage pipeline with two-way HubSpot and Salesforce sync, plus per-source cost tracking down to the fraction of a cent.
Every table is tenant-scoped. Four built-in roles plus custom ones you define, with permissions granular down to individual settings tabs.
Domain reputation is the one asset in outbound you can’t buy back. So every message passes the same ordered gate, and the first failure stops it — no override, no “send anyway”.
All four send paths run through it: campaigns, pipeline outreach, one-off sends, and agent replies. There is no fifth path.
UNSUBSCRIBED · INACTIVEOpted out, or marked inactive after a hard bounce.
SUPPRESSEDOn the tenant suppression list, by address or whole domain.
INVALID_EMAILNever verified, or verified and not Valid.
CONTACT_LEAD_COOLDOWNAlready contacted about this same role too recently.
CONTACT_COOLDOWNInside the global window between any two emails to a person.
LEAD_CONTACT_LIMITThis role has already reached its outreach ceiling.
COMPANY_CAPEnough people at this company have been approached already.
SEQUENCE_FATIGUEToo many steps sent with nothing coming back.
DOMAIN_THROTTLEDaily ceiling for this recipient domain is spent.
AI_BLOCKEDPolicy engine vetoed the content or the recipient.
Replies and flagged test contacts skip checks 04–08 by design; everything else runs every time.
Every provider is an adapter behind a common interface, selected per tenant. Swap one out and nothing downstream changes — and you pay them directly, at their rates, not ours.
Sourcing, enrichment, validation, sending, inbox and deals are one pipeline sharing one database. Most teams arrive here consolidating three to five separate tools.
One flat monthly price, with usage metered in credits. Provider costs are passed through at cost and tracked per source, down to fractions of a cent.
Run it on your own box with your own database and mailboxes. Your lead data and your reply history never have to leave your infrastructure.
Connect a mailbox, set your industries and headcount ceiling, and read the run report in the morning before anything sends.