# Company Buying Signal Monitor (`seemuapps/company-buying-signal-monitor`) Actor

Score company buying intent from hiring growth, funding, leadership and technology-change signals.

- **URL**: https://apify.com/seemuapps/company-buying-signal-monitor.md
- **Developed by:** [Andrew](https://apify.com/seemuapps) (community)
- **Categories:** Lead generation, Automation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 company scoreds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Company Buying Signal Monitor

Score any list of companies for buying intent — hiring growth, funding, leadership changes, and technology moves — and get back a ranked, sales-ready account list. Live hiring growth is measured straight from each company's public careers board, so you see accounts heating up before your competitors do.

### What you get

One dataset record per company, sorted hottest first:

- **Buying intent score**: 0–100, weighted across funding (35), hiring growth (30), leadership (20), and technology (15) signals
- **Grade**: `hot` (60+), `warm` (30+), or `watch` — drop it straight into a CRM view or lead-routing rule
- **Signal count and full signal list**: every signal that contributed to the score, with its title, type, date, and source URL
- **Reasons**: plain-English lines like `Open roles increased 140% (5 to 12)` you can paste into an outreach sequence
- **Hiring growth, measured live**: current open-role counts pulled from public Greenhouse, Lever, and Ashby boards and compared against the baseline you pass in
- Export to JSON, CSV, Excel, or Google Sheets directly from the Apify console

### Use cases

- Account prioritization — work the `hot` accounts first instead of guessing which of 500 targets is in-market
- Outbound triggers — fire a sequence the week a target company's headcount plan expands
- Territory and ABM planning — score a full target account list on a schedule and watch the ranking move
- Sales and marketing alignment — hand SDRs a scored list with the reason each account surfaced
- CRM enrichment — write the score, grade, and reasons back onto account records for routing and reporting

### How to use

1. Add your **Companies** — each with a `name`, and optionally `atsSource` (`greenhouse`, `lever`, or `ashby`) plus `atsBoard` so hiring growth can be measured
2. Set `baselineOpenRoles` per company to the open-role count from your previous run — that's what the growth signal compares against
3. Optionally add **Supplied signals** — funding rounds, exec hires, or tech changes your workflow already collects
4. Run the actor — scored companies appear in the **Dataset** tab, highest intent first

```json
{
  "companies": [
    { "name": "Example Inc", "atsSource": "greenhouse", "atsBoard": "example", "baselineOpenRoles": 5 }
  ],
  "signals": [
    { "company": "Example Inc", "type": "funding", "title": "Raised $40M Series B", "detectedAt": "2026-08-01" }
  ]
}
```

Run it on a schedule and store each run's open-role counts, then feed them back as `baselineOpenRoles` next time. That turns a one-off score into a trend line.

### Output format

```json
{
  "company": "Example Inc",
  "buyingIntentScore": 72,
  "grade": "hot",
  "signalCount": 2,
  "signals": [
    {
      "company": "Example Inc",
      "type": "hiring_growth",
      "title": "Open roles increased 140% (5 to 12)",
      "value": 7,
      "sourceUrl": "example"
    },
    {
      "company": "Example Inc",
      "type": "funding",
      "title": "Raised $40M Series B",
      "detectedAt": "2026-08-01"
    }
  ],
  "reasons": ["Open roles increased 140% (5 to 12)", "Raised $40M Series B"],
  "scoredAt": "2026-08-12T04:15:00.000Z"
}
```

### FAQ

**Do I have to supply signals myself?** No. With just a company name and its public careers board, you get hiring-growth scoring automatically. Supplied signals stack on top for a fuller picture.

**Why did a company score 0?** No signals matched it. Hiring growth only fires when a board has at least 3 open roles and more than its baseline — so a flat or shrinking headcount plan correctly scores nothing.

**Which careers boards are supported?** Public Greenhouse, Lever, and Ashby job boards. Companies without one still get scored on the signals you supply.

**Can I run it on a schedule?** Yes — schedule it weekly, store the open-role counts, and pass them back as baselines to track intent over time.

**What is Fixture mode?** A deterministic sample run that returns example data without calling any live board — useful for wiring up an integration before pointing it at real accounts.

# Actor input Schema

## `companies` (type: `array`):

Companies with name and optional Greenhouse, Lever, or Ashby board details.

## `signals` (type: `array`):

Optional funding, leadership, technology or hiring signals collected by your workflow.

## `fixtureMode` (type: `boolean`):

Use deterministic sample data for testing.

## Actor input object example

```json
{
  "companies": [
    {
      "name": "Example Inc",
      "atsSource": "greenhouse",
      "atsBoard": "example"
    }
  ],
  "signals": [],
  "fixtureMode": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        {
            "name": "Example Inc",
            "atsSource": "greenhouse",
            "atsBoard": "example"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seemuapps/company-buying-signal-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "companies": [{
            "name": "Example Inc",
            "atsSource": "greenhouse",
            "atsBoard": "example",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("seemuapps/company-buying-signal-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    {
      "name": "Example Inc",
      "atsSource": "greenhouse",
      "atsBoard": "example"
    }
  ]
}' |
apify call seemuapps/company-buying-signal-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seemuapps/company-buying-signal-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Tnz2JQW8iIHLCty87/builds/QHM0k22KOJF72N5ZG/openapi.json