LEAD GENERATION

Infer Tech Stack from Job Posts to Route Product-Fit Accounts

Reads new job descriptions to infer a company's tech stack, researches them with Perplexity for confirmation.

CategoryLead Generation
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew ICP job posting detected
  • ActionExtract tech stack from postingOpenAI
  • ActionConfirm stack via live researchPerplexityPerplexity
  • LogicScore product fit, drop misses
  • OutputAdd fit accounts to Notion boardNotionNotion

What it does

Job descriptions leak a company's tech stack in their requirements lists. This workflow mines that, confirms it with live research, and forwards only the accounts whose stack signals a genuine fit for your product, complete with a written rationale, into a Notion board your team works from.

When to use it

Use it when fit is technical, not just firmographic, for example, you sell to teams already on a specific cloud, database, or framework. It filters the noisy hiring firehose down to accounts your product can actually displace into or complement.

How it works

  1. 1A new ICP job posting from the harvester triggers the run.
  2. 2OpenAI extracts the implied tech stack and tools from the posting's requirements.
  3. 3Perplexity does a live lookup to confirm the stack and surface recent context on the company.
  4. 4A logic step scores product fit against your criteria and drops accounts below the bar.
  5. 5Qualifying accounts are added to a Notion target board with stack tags, a fit score, and the rationale.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OpenAIModels, embeddings, files.
  2. 2
    Connect PerplexitySearch-grounded answers with citations.
  3. 3
    Connect NotionPages, databases, comments.
  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.