List Coverage Audit

List coverage audit

The user already owns a list: an old TAM export, conference attendees, a scraped directory, a CRM dump. Most rows on it are dead this quarter. This skill answers the only question that matters before money is spent on the list: who on it is hiring right now.

Ask for it like this

• "Which companies in accounts.csv are hiring right now?"
• "Qualify this list before I enrich it"
• "What share of my TAM is actually in motion this month?"

How it works

Bulk path, one call:

POST /v1/migration-import

Upload the list (CSV of company names or domains), header X-API-Key from $REQBEAT_API_KEY. The response splits it into covered (tracked, with live status) and misses.

Row-by-row path, when the user wants control or the list is short:

POST /v1/clay/enrich   body: {"domain": "...", "name": "..."}

Returns is_hiring and open_req_count per company. The same call powers a Clay qualifier column.

Output format

Three numbers first, then the table:

• In motion: N of M companies hiring right now (the only rows worth spending on)
• Tracked but quiet: covered, not hiring; park them on a watch instead of a sequence
• Unknown: not in the corpus; say so plainly

| company | domain | hiring now | open reqs | verdict |

Verdicts: work now / watch / skip this quarter.

Rules

1. The economics point of this skill is the inverted waterfall: signal check first, people-enrichment second. Spell the saving out: rows removed times the user's per-row enrichment cost.
2. Unknown is an honest answer. Never mark an uncovered company as not hiring; the corpus not seeing it is a different fact.
3. Offer the follow-through: quiet rows onto account-watchlist, in-motion rows into pre-call-brief and signal-first-outreach.