# Build an in-market account list from intent data

> A step-by-step build: define your ICP filters, pull the accounts researching your topics, add the buyers and their emails, and refresh it weekly.

Source: https://www.b2benrich.com/guides/in-market-account-list  
Author: Dag Holmen, B2Benrich · Updated 2026-10-28

In-market accounts are companies that fit your ICP and are researching your topics right now. Fit alone gives you a long list of companies that could buy someday. Intent alone gives you a pile of research activity, much of it from companies you’d never sell to. The overlap is the list worth working this week.

This guide walks through the build in five steps: turn your ICP into API filters, pull the accounts researching your topics, add the buyers, find their work emails and refresh the whole thing weekly. Every step except the intent pull uses B2Benrich endpoints you can call today. The intent step is marked where it goes, because the intent endpoints aren’t documented yet.

## What makes an account in-market

Two things have to be true at once.

1. **It fits.** Industry, size, region and the other criteria your best customers share.
2. **It’s researching now.** Recent activity on topics tied to what you sell. One page view doesn’t count. Repeated research, several related topics or more than one person at the company does.

Some teams call accounts with a sharp rise in research "surging accounts". It’s a useful idea: compare each account to its own baseline, not just to a fixed threshold.

## Step 1: Turn your ICP into API filters

Start with the fit side, because it changes slowly and you can cache it. The [company search API](https://www.b2benrich.com/guides/company-search-api) takes the firmographic filters you’d use in a spreadsheet: industry, headcount range, revenue range and headquarters location.

Filter values have to match the API’s own lists. Pull them first from the meta endpoint, for example `POST /v1/search/meta/employee_count_range` or `POST /v1/search/meta/industry_linkedin`, and copy the exact strings. The values in the example below are placeholders.

```bash
curl -X POST https://api.b2benrich.com/v1/search/companies \
  -H "X-Api-Key: $B2BENRICH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "industry_linkedin": "Software Development",
    "employee_count_range": "201-500",
    "headquarters_country_name": "United States",
    "page": 1,
    "page_size": 100
  }'
```

The response has `records` and a `total_count`. Each record has the company’s `id`, `name`, `domain`, `industry`, `employees_range` and more. Page through and save every domain. That’s your fit set, or target account list.

If you also filter on tech stack, the [prospecting API](https://www.b2benrich.com/guides/prospecting-api) takes a `technologies` company filter.

## Step 2: Pull the accounts researching your topics

Write your topic list before you touch the intent data. Three groups cover most offers:

- **Category:** what you sell, in buyer words.
- **Problems:** the pain that starts the search.
- **Competitors:** the names buyers compare you to.

Then ask the intent data which of your fit-set domains show activity on those topics. Keep only the overlap. Accounts with intent that fall outside your fit set are worth a look once a quarter, because a lot of them can mean your ICP is too narrow. They don’t belong on this week’s list.

## Step 3: Add the buyers

For each in-market account, find two or three people who own the problem. `POST /v1/search/company-employees` takes a domain and filters like `job_function`, `job_level` and `persona`. As with company filters, get the allowed values from the meta endpoint.

## Step 4: Find the work emails

`POST /v1/enrich/person/name-domain-to-email` takes a first name, last name and domain and returns `{ status, email }`. Check `status` before you use the email. More detail is in the [email finder API](https://www.b2benrich.com/guides/email-finder-api) guide.

Here are steps 2 to 4 as one script:

```python
import os, requests

BASE = "https://api.b2benrich.com"
HEADERS = {"X-Api-Key": os.environ["B2BENRICH_API_KEY"], "Content-Type": "application/json"}

def post(path, body):
    r = requests.post(f"{BASE}{path}", json=body, headers=HEADERS, timeout=30)
    r.raise_for_status()
    return r.json()

def get_intent_signals(account_domains, topics):
    # TODO: replace with the B2Benrich intent endpoint once it's documented.
    # Return your own shape: [{"domain": ..., "topic": ..., "strength": ..., "seen_at": ...}]
    return []

fit_domains = load_fit_set()  # domains saved in step 1
topics = ["sales engagement software", "outbound automation", "competitor-x alternatives"]

rows = []
for signal in get_intent_signals(fit_domains, topics):
    people = post("/v1/search/company-employees", {
        "domain": signal["domain"],
        "job_level": "VP",            # use a value from /v1/search/meta/job_level
        "job_function": "Sales",      # use a value from /v1/search/meta/job_function
        "page": 1,
        "page_size": 3,
    })["records"]

    for p in people:
        found = post("/v1/enrich/person/name-domain-to-email", {
            "first_name": p["first_name"],
            "last_name": p["last_name"],
            "domain": p["company_domain"],
        })
        rows.append({**signal, "name": p["full_name"], "title": p["job_title"],
                     "linkedin_url": p["linkedin_url"],
                     "email": found.get("email"), "email_status": found.get("status")})
```

## What the finished list looks like

| domain | company | topic | first_seen | buyer | title | email |
|---|---|---|---|---|---|---|
| acme.com | Acme | sales engagement software | 2026-10-21 | Maya Chen | VP of Sales | maya.chen@acme.com |

Keep `topic` and `first_seen` on every row. Reps need the topic to write a relevant message, and you need the date to know when the row goes stale.

## Step 5: Refresh it weekly

An in-market list starts aging the day you build it. Research windows close, people change jobs and new accounts start looking. Schedule the build as a weekly job and split the work by how fast each part changes:

- **Fit set:** re-run monthly, or when your ICP changes.
- **Intent:** re-pull every run.
- **Buyers and emails:** look up only for accounts that are new to the list, and re-check older contacts now and then.

Compare each run to the last one and tag every account as new, still active or dropped. New accounts go to reps first. Dropped accounts go back to marketing. To act on new accounts the day they show up instead of once a week, see [signal-based outbound](https://www.b2benrich.com/guides/signal-based-outbound).

Because B2Benrich is unlimited API usage for $500 a month with no credits, re-running the full pipeline every week doesn’t change your bill.

## Frequently asked questions

### What are in-market accounts?

In-market accounts are companies that fit your ideal customer profile and are actively researching topics tied to what you sell, such as your category, the problem you solve or your competitors.

### What are surging accounts?

Surging accounts are companies whose research on a topic has risen sharply compared with their own usual level. Comparing each account to its own baseline catches real changes better than one fixed threshold.

### How is a target account list different from an in-market account list?

A target account list is usually built on fit alone and changes slowly. An in-market list is the part of it showing current research activity, so it changes every week.

### How often should I refresh an in-market account list?

Weekly is a good starting point. Re-pull the intent every run, re-check firmographics less often, and only look up buyers and emails for accounts that are new to the list.

### Can I build an in-market account list with B2Benrich today?

You can build the fit set, buyer search and email steps today with the company search, company-employees and email finder endpoints. B2Benrich is adding intent data to the API, and the intent step plugs into the same script once those endpoints are documented.
