Back to blog
6 min read

Account Mapping From Data, Not a Whiteboard

By Kooperativa Engineering

Account Mapping From Data, Not a Whiteboard

Account mapping, in the sales sense, means drawing the people around a target account: who owns the budget, who influences it, who might champion you, and where you have no one at all. Most maps are a slide or a spreadsheet tab that a rep fills in from memory after a first call. By the next quarter it is wrong, because the people moved and nobody told the map.

The fix is to stop treating the map as a document and treat it as the output of a few queries you can re-run. That changes what the map is good for. A document records what you knew once. A query shows you what is true now and what changed since you last looked.

Step 1: size the group before you name anyone

Start with how many people the company has at each level. The seniority breakdown returns a total and five bands, which tells you whether there is a leadership layer at all in a company of that size.

Requestbash
curl "https://kooperativa.io/api/v1/company/headcount-by-seniority?company_id=COMPANY_ID" \
  -H "Authorization: Bearer ik_live_..."

A company with a few hundred people and nothing above manager is a different account from one with a named director layer. You find that out in one call, before anyone spends an hour researching names.

Step 2: list the senior people

Requestbash
curl "https://kooperativa.io/api/v1/company/decision-makers?company_id=COMPANY_ID&seniority=c-level,vp,director" \
  -H "Authorization: Bearer ik_live_..."

Two limits to know. The endpoint excludes the manager level on purpose, and many real champions are managers. And it merges and sorts results locally under a hard ceiling of 100 rows, so a very large company can return an empty page while the total still reports the full count. For managers, or for a specific function, use people search with a company_id, seniority and a title filter instead. Search pages cap at 50 per page.

Step 3: add people a title cannot show you

If you already know one person at the account, their colleagues are the fastest way to find the rest of the team around them.

Requestbash
curl "https://kooperativa.io/api/v1/person/colleagues?id=PERSON_ID&per_page=25" \
  -H "Authorization: Bearer ik_live_..."

Step 4: keep it current

Pick the five to ten people who matter on each priority account and put a monitor on them. A monitor watches one profile and sends a signed webhook when a tracked field changes.

Requestbash
curl -X POST "https://kooperativa.io/api/v1/monitors" \
  -H "Authorization: Bearer ik_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "type": "person",
    "subject_url": "https://www.linkedin.com/in/EXAMPLE",
    "webhook_url": "https://your-app.com/webhooks/kooperativa",
    "label": "VP Operations, Acme",
    "events": ["person.job_changed", "person.title_changed"]
  }'

A workspace can hold 500 monitors, so this is a tool for priority accounts, not for every contact in the CRM. For the long tail, a scheduled call to the hiring-signals endpoint, which lists recent joins at a company, catches new senior people without a monitor per head.

What the map still cannot tell you

Titles show who might be in the buying group. They do not show who decides. A director of engineering may own the budget at one company and have no say at another. Treat the output as a list of names to confirm in conversation, and record the role you confirmed next to each name, not the title you inferred.

A record shape that works (our suggestion, not an API response):

Payloadjson
{
  "person_id": "PERSON_ID",
  "title_on_profile": "VP Operations",
  "role_confirmed": "economic buyer",
  "confirmed_on": "2026-11-12",
  "last_checked": "2026-11-15",
  "source": "decision-makers"
}

The two date fields are the point. confirmed_on tells you how old your belief about the role is, and last_checked tells you how old the underlying data is.

Get started

Try Kooperativa

One API key. Person and company enrichment, structured search, and monitors under one flat license.

Keep reading

We use only cookies that are strictly necessary to run this site (staying signed in, and protecting forms from abuse). Our analytics tool doesn't use cookies or collect personal data. See our Privacy Policy for details.