LEAD GENERATION

Nightly digest of repeat visitors scored against your ICP

Runs each night to roll up the day's repeat anonymous visitors, scores each account against your ideal-customer profile with an LLM.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionGroup the day's visits by domain, drop single visitsAirtableAirtable
  • ActionEnrich each repeat accountExa
  • ActionScore each account against the ICPOpenAI
  • LogicDrop accounts below the fit threshold
  • OutputWrite ranked dossiers to the SDR queueAirtableAirtable

What it does

Instead of alerting on every visit, this workflow batches the day's de-anonymized traffic once nightly, keeps only companies that returned more than once, scores each against your ICP, and produces a ranked queue of researched dossiers for SDRs to work the next morning.

When to use it

Use it when you prefer a clean prioritized worklist over a noisy live feed, and you want an LLM to apply your ICP rules (industry, size, geo) consistently rather than relying on a rep's gut.

How it works

  1. 1A nightly schedule triggers the rollup.
  2. 2The workflow reads the day's visit log and groups it by company domain, dropping single-visit accounts.
  3. 3Exa enriches each repeat account with firmographics and recent activity.
  4. 4An OpenAI step scores each account against the ICP definition and writes a fit rationale.
  5. 5A filter drops below-threshold accounts.
  6. 6Qualified dossiers are written to Airtable, ranked by score, ready for the SDR queue.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect ExaNeural search across the web.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.