CatchIntentCatchIntent
Leads

Leads

The actual people inside each Account. Where you act.

A Lead is a real person inside an Account — the path from a why-now signal to a sent message. Every Lead belongs to exactly one Account; the Account is the durable working atom, the Lead is the action.

You can browse Leads two ways:

  • Inside an Account — see who is in this company, who's strongest, what's still missing vs. your buyer roles.
  • The Leads tab — a flat person-list across all accounts, sliced by warmth, title, seniority, or status. Same data as Accounts; different shape.

What a Lead contains

FieldWhat it tells you
ProfileName, title, LinkedIn URL
AccountWhich company they're in, with its full signal stack
Why-nowThe signal that surfaced this person (job change, account funding, etc.)
Warmth scoreHow strong the fit + signal are. See Warmth Scoring
SequenceA drafted multi-touch outreach sequence written for this person and this why-now

Open any Lead to see the full reason, the source, and the outreach sequence you can edit and send.

Working a Lead

  1. Open the Account — context first. Read the signal stack.
  2. Open the strongest Lead inside it.
  3. Send or push. Copy each step and send it from your own LinkedIn account, or push the Lead to your CRM.
  4. The Account state updates so the team doesn't double-up. See Account States.

What does not reach you

Quality is partly about what we drop pre-save:

  • Already-delivered people don't deliver twice.
  • People you've dismissed don't resurface for a while.
  • Anyone employed at one of your Competitor domains is filtered out automatically.
  • Candidates the verification step judges a poor fit are dropped before delivery (you can see what was dropped and why in Settings → Tuning).

None of these count toward your lead allowance.

Drop policy: borderline beats empty

A Lead is dropped pre-save only for unambiguous disqualifiers — competitor employee, wrong industry, brand exclusion, irrelevant hiring role. Anything uncertain or borderline or weak ICP match is kept (with a low-confidence flag if needed). In an account-first model with finite supply, "we found nothing" is worse for you than "we found something borderline."

If a borderline lead is wrong, drop it; the Audience learns.

Daily and monthly volume

TierLeads/moDaily soft cap
Trial50 total (whole trial)
Growth1,00050/day
Scale4,000200/day
EnterpriseCustomCustom

The daily soft cap = monthly / 20 (one working month). It exists so a bad Audience config can't burn the whole monthly budget on noise in one day. Liftable per-workspace on support request.

On this page