Pre-build each new customer's TAM on day one inside an AI-native CRM

Let an AI-native CRM arrive pre-filled: on sign-up it builds the customer's target accounts and contacts from their ICP so agents can start working the market immediately.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

A selection of teams that run this job on Forager · plus other sales-tech platforms

Uses POST /person_role_search/, POST /organization_search/ · People search API reference

What it costs: 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

2 inputs → Company data feed + People data feed + People search + Company enrichment + Work emails → 3 fields sample data

01 · Inputs

Client ICP

Founders · e-commerce brands · US

Title

VP Revenue Operations

02 · Forager

Company data feed + People data feed + People search + Company enrichment + Work emails POST /person_role_search/

Match found

03 · Outputs

Kim ExemplarVP Revenue Operations · Example Inc.

work email: kim@example.com
name: Kim Exemplar
title: VP Revenue Operations
mobile: +1 (416) 555-0186
company: Example Inc.

3 fields in the responseexample data

Steps

Translate the ICP description into filters over company_feed (industry, employees, location, technologies)
Select personas per account from people_feed, or call POST /person_role_search/ for long-tail accounts
Enrich new accounts with POST /organization_search/ and fetch work_email only for contacts the agent will work
Keep the TAM fresh on each feed delivery and alert on new accounts that match

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Translate the ICP description into filters over company_feed (industry,
# employees, location, technologies)

# 2. Select personas per account from people_feed, or call POST
# /person_role_search/ for long-tail accounts
r1 = requests.post(f"{BASE}/person_role_search/", headers=HEADERS, json=body)

# 3. Enrich new accounts with POST /organization_search/ and fetch
# work_email only for contacts the agent will work
r2 = requests.post(f"{BASE}/organization_search/", headers=HEADERS, json=body)

# 4. Keep the TAM fresh on each feed delivery and alert on new accounts that
# match

# 1. POST /person_role_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_role_search/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. POST /organization_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/organization_search/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: People search API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
ICP description	`TAM account list`
persona titles	`contacts by persona`
	`work_email`

Questions about this recipe

How can a CRM pre-populate a new customer's target accounts and contacts?

Enrich new accounts with POST /organization_search/ and fetch work_email only for contacts the agent will work. Keep the TAM fresh on each feed delivery and alert on new accounts that match.

What does it cost to pre-build each new customer's TAM on day one inside an AI-native CRM?

People search: people search 1 credit per request and people search: role details 1 credit per request, charged whether or not data comes back. Company enrichment: 1 credit per request, charged whether or not data comes back. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Company data feed is a flat annual licence, global or regional, not priced in credits. Growth's 8,250 monthly credits cover 1,650 emails or 8,250 search requests, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send ICP description and persona titles. You get back contacts by persona, TAM account list and work_email, as JSON. You also need a Forager API key, which comes with a free account.

What data does an AI-native CRM need to build a customer's TAM automatically?

You send ICP description and persona titles. You get back TAM account list, contacts by persona and work_email. New CRM customers see a populated pipeline on day one instead of an empty database.

Can teams running this workflow see a sample of the company data feed before licensing it?

Yes. Request a sample extract of the company data feed on a 30-minute call and check the fields against your own records before you license it.

When should I run this workflow?

When a new customer completes CRM onboarding and describes their ICP. New CRM customers see a populated pipeline on day one instead of an empty database.

Which Forager products does this recipe use?

Company data feed, people data feed, people search, company enrichment and work emails. Company data feed: a licensed file of 65M+ company profiles and firmographics, delivered to Snowflake or S3 on a schedule. People data feed: a licensed file of 800M+ professional profiles, refreshed on a schedule and delivered to Snowflake or S3.

How accurate is Forager data?

The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo, delivered as a data share to Snowflake, Databricks and Amazon S3 and called through the API from Google BigQuery, your own code, Make and n8n. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

4 steps: translate the ICP description into filters over company_feed (industry, employees, location, technologies), select personas per account from people_feed, or call POST /person_role_search/ for long-tail accounts, enrich new accounts with POST /organization_search/ and fetch work_email only for contacts the agent will work and keep the TAM fresh on each feed delivery and alert on new accounts that match.

Do I need a subscription?

Not to test: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Can our users see Forager data in our product?

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

A selection of teams that run this job on Forager · plus other sales-tech platforms

Clay
- GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Juicebox
- AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
Nooks
- Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Monaco
- CRM add-ons
Selected use case: mobile data in its enrichment waterfall.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Myko AI
- CRM add-ons
Voice-first tool that lets field reps update Salesforce, Veeva and Dynamics.
item
- CRM add-ons
AI-native CRM where teams and agents work side by side.

Pre-build each new customer's TAM on day one inside an AI-native CRM

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How can a CRM pre-populate a new customer's target accounts and contacts?

What does it cost to pre-build each new customer's TAM on day one inside an AI-native CRM?

What do I need to run this recipe, and what comes back?

What data does an AI-native CRM need to build a customer's TAM automatically?

Can teams running this workflow see a sample of the company data feed before licensing it?

When should I run this workflow?

Which Forager products does this recipe use?

How accurate is Forager data?

Which tools can run this workflow?

How many steps is this workflow?

Do I need a subscription?

Can our users see Forager data in our product?

More recipes for CRM add-ons

Detect CRM contacts who changed jobs and alert on moved champions

Power a CRM's native contact-enrichment button

Alert account owners when a customer posts a job naming a competitor

Keep one canonical company record per account in a CRM add-on

Merge CRM duplicates that use a personal and a work email

Back a sales-intelligence database with an additional mobile source

Put people, company and job data your users can act on inside your product