CrustData Signals

Enrich company domains with structured signal data (funding, growth, departments, recent hires) and write results to Google Sheets across 5 tabs.

Inputs

1. Domains - a Google Sheet link/ID with a domain column, or a raw list
2. Hire window (optional) - 90, 180, or 365 days back for recent hires (default: 180)
3. Output destination - same sheet (new tabs), different sheet ID, or create new

If the user provides a sheet link, extract the spreadsheet ID and ask which tab and column contain the domains.

Prerequisites

• CRUSTDATA_API_KEY env var - get your API key from the CrustData dashboard
• Python packages: pip install -r ../headless-gtm-shared/requirements.txt (Sheets export uses the optional gspread/google-auth extras)
• Google Sheets OAuth2 token at ~/.google/token.json

Credit rules

Each API call costs real credits. Treat them like money.

API	Cost	Rate limit
/company/enrich	2 credits/company	15 RPM
/person/search	0.03 credits/result	30 RPM

Cost per domain scales with how many hires come back, so it is not a flat rate: 2 (enrich) + 0.03 x (hires returned). Budget by the ICP's hiring velocity, not a single number:

ICP hiring profile	Hires/company	Cost/domain
Low-hiring	~10	~2.3
Typical	~20	~2.6
High-growth / high-hiring	~65	~4.0

The flat "~2.6" only holds for a typical ~20-hire pull; high-growth ICPs run closer to ~4 credits/domain. Estimate with the actual hire window and expected velocity.

JSON files are the source of truth. Every API call saves a per-domain JSON to runs/{run-id}/. Before calling the API for any domain, check whether a JSON already exists in any prior run folder (older runs may sit in the legacy outputs/ dir - check both). If it does, reuse it - do not spend credits again. The sheets writer can combine multiple run folders.

Process

1. Collect inputs

Ask the user for domain source, hire window, and output destination. Default to 180-day hire window if not specified.

2. Run enrichment

All paths below are relative to this skill's folder.

export CRUSTDATA_API_KEY=<your-crustdata-api-key>

# From a list of domains
python3 scripts/crustdata_signals.py \
  --domains domain1.com,domain2.com \
  --hire-days 180

# Chain position: from an upstream records.jsonl (01/02/03) - inherits its fields
python3 scripts/crustdata_signals.py \
  --records ./runs/<run-id>/records.jsonl \
  --hire-days 180

# From a Google Sheet
python3 scripts/crustdata_signals.py \
  --sheet-id <SHEET_ID> --tab "Sheet1" --domain-col B \
  --hire-days 180

The script saves per-domain JSON files to runs/{run-id}/ and maintains a tracker.json for resume. If it fails mid-run, resume with --resume --output-dir runs/{run-id}.

3. Write to Google Sheets

# Single run folder
python3 scripts/sheets_writer.py \
  --run-dir runs/{run-id} \
  --spreadsheet-id <SHEET_ID>

# Combine multiple run folders (dedupes by domain)
python3 scripts/sheets_writer.py \
  --run-dir runs/run-A runs/run-B runs/run-C \
  --spreadsheet-id <SHEET_ID>

# Create a new sheet
python3 scripts/sheets_writer.py \
  --run-dir runs/{run-id} \
  --create-new --title "CrustData Signals - Jul 2026"

The writer accepts multiple --run-dir paths and deduplicates by domain. This means you can enrich domains across separate sessions and combine them into one sheet without re-running the API.

Output tabs

Tab	Grain	Key columns
Signal Summary	1 row/domain	Company info, key metrics, signal analysis (Funding/Growth/Dept/Hiring/Summary)
Recent Hires	1 row/person	Name, title, start date, days since joining, seniority, function
Funding	1 row/round	Date, round type, amount, lead investors, all investors
Company Growth	1 row/domain	Headcount + MoM/QoQ/6m/YoY growth (% and absolute)
Dept Growth	1 row/domain-dept	Department, current headcount, 6m ago, YoY ago, growth %

4. Save run summary

After writing to sheets, save a markdown summary to runs/{run-id}/summary.md with: date, domain count, hire window, credits consumed, domains processed/failed/skipped, sheet URL.

5. Clean up (ask first)

Ask the user whether to keep or delete the JSON backup files. They can always be regenerated but that costs credits again.

Signal analysis columns

The sheets writer auto-generates signal text:

• Funding Signal: "Series A $20M raised 45d ago - FRESH CAPITAL | 3 rounds total"
• Growth Signal: "Growing 32% YoY (+76 employees) - STRONG GROWTH | 202 employees"
• Dept Signal: "Engineering 23% | Operations 23%"
• Hiring Signal: "Senior hires: VP Sales, Head of Eng | 42 new hires | 5 open roles"
• Signal Summary: All signals combined

Key behaviors

• Enrich costs 2 credits regardless of fields requested - always pull all 19 field groups.
• Pre-computed growth fields from CrustData lag by 3–10 months. The script computes fresh growth from timeseries data.
• basic_info.industries is often null. The writer falls back to taxonomy.categories then taxonomy.professional_network_industries.
• Department keys from CrustData are Title Case with spaces (e.g. "Engineering", "Human Resources"). The writer handles this automatically.
• Department timeseries uses employee_count as the key (not headcount).
• Some companies return updated_at: null - a genuine coverage gap, not staleness.
• Rate limiting is handled automatically with conservative delays.

Shared output (records.jsonl)

After enrichment completes, the script writes records.jsonl and meta.json to the run folder. Each record carries the stage-04 fields per headless-gtm-shared/CONVENTIONS.md - funding[] (rounds), headcount_growth, dept_growth[], recent_hires[] (capped at 25; per-domain JSONs keep the full list) - plus signal summaries in filters_matched:

{"company": "Serve Robotics", "domain": "serverobotics.com", "person": null, "funding": [{"round_type": "Series B", "money_raised_formatted": "$56M", "date": "2026-03-02"}], "headcount_growth": {"current_employee_count": 350, "employee_count_yoy_growth_rate_percentage": 42}, "dept_growth": [{"department": "Engineering", "current": 120, "six_months_ago": 95, "growth_6m_pct": 26.3}], "recent_hires": [{"name": "J. Doe", "title": "VP Sales", "start_date": "2026-05-01", "seniority": "vp"}], "filters_matched": ["Series B $56M", "350 employees", "42% YoY growth", "18 recent hires"]}

When the run was fed an upstream records.jsonl (--records), every upstream field is inherited into these records, so the chain record keeps evolving instead of restarting here.

References

• references/enrich-api.md - company enrich endpoint docs
• references/person-search-api.md - person search endpoint docs
• CrustData API docs - API keys, auth headers, industry taxonomy