LEAD GENERATION

Exa Job-Listing Discovery with ICP Fit Scoring

Uses Exa neural search to find fresh job listings that imply adoption of a target tool category, scores each company against your ICP.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule kicks off discovery run
  • ActionExa neural search for signal-matching job listingsExa
  • LogicParse company details and compute ICP fit score
  • LogicDrop companies below score threshold
  • OutputUpsert qualified leads to HubSpot with score and sourceHubSpotHubSpot

What it does

Instead of relying on a fixed company list, this workflow uses Exa to discover postings across the open web that semantically match a buying signal — for example "hiring a platform team to migrate off a legacy CRM." Each discovered company is scored against your ideal-customer-profile rules, and only those clearing the threshold are written to HubSpot as scored leads.

When to use it

Use it for top-of-funnel discovery when you do not yet have the target accounts named and want the signal itself to surface them. It is well suited to entering a new segment or testing a fresh value hypothesis where you would rather find demand than guess at an account list.

How it works

  1. 1A schedule kicks off the discovery run.
  2. 2Exa runs a neural search for job listings matching your signal phrasing and returns candidate pages.
  3. 3A logic step parses company and role details and computes an ICP fit score from size, industry, and signal strength.
  4. 4A logic gate drops anything below your score threshold.
  5. 5Qualified companies are upserted to HubSpot as leads with the fit score and source posting attached.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ExaNeural search across the web.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.