# Map the security buying committee at SaaS target accounts

**Use case:** 

Give company domains and pick Security as the buying team. Get the likely economic buyer, champions, evaluators, blockers and influencers per company, one person per row with title, department, seniority and profile URL. Roles are guessed from job titles.

## Input

```json
{
  "items": [
    "stripe.com",
    "shopify.com",
    "hubspot.com"
  ],
  "buyerType": "security",
  "maxPeoplePerDomain": 8,
  "limit": 25,
  "includeAudit": false
}
```

## Output

```json
{
  "companyDomain": {
    "label": "Company domain",
    "format": "string"
  },
  "committeeRole": {
    "label": "Committee role",
    "format": "string"
  },
  "roleBasis": {
    "label": "Why this role",
    "format": "string"
  },
  "fullName": {
    "label": "Name",
    "format": "string"
  },
  "jobTitle": {
    "label": "Title",
    "format": "string"
  },
  "seniority": {
    "label": "Seniority",
    "format": "string"
  },
  "department": {
    "label": "Department",
    "format": "string"
  },
  "location": {
    "label": "Location",
    "format": "string"
  },
  "country": {
    "label": "Country",
    "format": "string"
  },
  "startYear": {
    "label": "In role since",
    "format": "integer"
  },
  "hasWorkEmail": {
    "label": "Work email on file",
    "format": "boolean"
  },
  "hasPersonalEmail": {
    "label": "Personal email on file",
    "format": "boolean"
  },
  "lowSignal": {
    "label": "Thin profile",
    "format": "boolean"
  },
  "connections": {
    "label": "Connections",
    "format": "integer"
  },
  "headline": {
    "label": "Headline",
    "format": "string"
  },
  "profileUrl": {
    "label": "Profile",
    "format": "string"
  },
  "slug": {
    "label": "Profile slug",
    "format": "string"
  },
  "updatedAt": {
    "label": "Updated",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Buying Committee Map - Buyers, Champions, Blockers by Domain Actor is ready to run with the inputs already set for "Map the security buying committee at SaaS target accounts". [Sign up or log in](https://console.apify.com/create-task-from-example/ECJYiYf3JYWQDp56H) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Map the security buying committee at SaaS target accounts" task

The Buying Committee Map - Buyers, Champions, Blockers by Domain Actor will start running based on the input automatically. You can also change all the input fields, like which companies? (domains, website urls or emails), who buys your product? (buyer type), and more, to match your specific use case.

### 3. Receive the "Map the security buying committee at SaaS target accounts" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as company domain, committee role, why this role, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Map the security buying committee at SaaS target accounts" task via API](https://apify.com/b2bdata/buying-committee-map.md).

## FAQ

### What does the security buying committee map return?

The security committee map returns one person per row with a committee role, the basis for that role, job title, seniority, department, location and profile URL for each company domain.

### What input does the buying committee task need?

This task needs a list of company domains, a buyer type (Security here), a cap on people per domain and an overall limit. Website URLs and email addresses are reduced to their domain.

### How do I run the committee map via API or schedule it?

Run the security buying committee task through the Apify API, put it on a schedule in Apify Console, or start it by hand. Export the dataset as CSV or JSON and open it in Google Sheets or Excel.

### How reliable are the committee roles in this security task?

In the security committee map, each role is a guess from the job title and team, never a confirmed fact. The roleBasis column explains why a person got a role, so reps can review before outreach.

## About this Actor

This example demonstrates how to use [Buying Committee Map - Buyers, Champions, Blockers by Domain](https://apify.com/b2bdata/buying-committee-map.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/b2bdata/buying-committee-map.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/b2bdata/buying-committee-map.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).