04-crustdata-signals

Solid

Enriches company domains with structured signals from CrustData - funding rounds, headcount growth, department growth, and recent hires. Use when the user wants to pull company signals, enrich domains with funding/growth/hiring data, check who recently joined a company, find new hires at a domain, get headcount trends, or anything involving CrustData enrichment. Also triggers on: "run crustdata signals", "enrich these domains", "pull funding data", "who joined recently", "headcount growth for these companies", "department growth", "recent hires at", "crustdata enrich".

Data & Documents 18 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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](https://crustdata.com) - Python packages: `pip install -r ../_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 ...

Details

Author
Zevenue
Repository
Zevenue/headless-gtm
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

04-theirstack-jobs

Pulls open job postings from the TheirStack API and turns them into structured hiring signals - open roles per domain, titles, seniority, posting dates, hiring team, plus free firmographics (headcount, funding stage, industry). Step 04 (signals) of the API-first GTM chain, and the discovery entry for hiring-defined ICPs. Use when the user wants hiring signals, open reqs, job postings, "who is hiring", "which of these companies are hiring X", "find companies hiring Y right now", open-role checks on a domain list or records.jsonl, or anything TheirStack. Sizing counts bound every pull before spend - free without company filters, ~1 credit against a domain list - then 1 credit per job returned. For people who already joined - recent hires, headcount growth, funding rounds - use 04-crustdata-signals; for scoring and campaign angles, hand the records to 05-signal-builder.

18 Updated today
Zevenue
Web & Frontend Solid

05-signal-builder

Rank a prospect's outbound signals and pick the campaign approach (PQS / PVP / Pain-led) - the judgment layer (step 05) of the API-first GTM chain. Takes scraped website markdown (03-firecrawl-research), structured vendor signals like funding / headcount / recent hires (04-crustdata-signals), or just a URL or pasted content, and emits ranked provenance-backed signals: the exact quotable sentence, source URL, 1-10 score, and recommended approach. Use whenever the user wants to score, rank, or prioritize prospects or accounts, decide outreach angles, or asks "which of these companies should we email first", "what's the angle for this account", "rank these signals", "score these prospects", "turn this scrape into campaign angles", or "run signal-builder" - and whenever a records.jsonl or enrichment output is ready for judgment before writing copy. Scoring and interpretation live here; scraping belongs to firecrawl-research, vendor signal pulls to crustdata-signals, email finding to resolution.

18 Updated today
Zevenue
AI & Automation Solid

03-firecrawl-research

Scrapes a company website into clean, page-typed markdown using Firecrawl map + scrape + extract. Triggers on: "scrape this company", "read their website", "extract pages from", "research this domain", "fetch their careers page", or any URL + "scrape/extract/read". Covers single domain, batch processing, structured LLM extraction, and Google Sheets output.

18 Updated today
Zevenue