anysite-crm-signals

CRM Signals

Turn a static account list into a prioritized "act now" list. One signal is a guess; 2+ signals within ~30 days is a pattern. Signal-triggered outreach converts several times better than cold cadence (vendor-reported benchmarks: exec hires and job changes lead, then funding) — treat the ordering as solid, the exact percentages as marketing.

Prerequisites

Active CRM connection (crm_list_connections). Profile optional for read-only sweeps; required if the user wants signal fields written back — and then the Writing rules in anysite-crm-setup apply.

Flow

1. Pick the account set

crm_query_records(object_type="companies", list_id=<target list> | search=...,
                  properties=[record_id, name, domain, <mapped signal fields if any>])

Cap a single sweep at ~50 accounts (each account costs several source calls). More → propose splitting or narrowing.

2. Per-account signal collection

Run the cheap universal chain for every account; add optional probes when relevant.

Funding / exec hires / news / layoffs / intent (one lookup covers five signals):

# The domain-resolve you already did (search_sql_companies) returns `crunchbase_link` —
# extract the alias from it for FREE. Only when crunchbase_link is empty AND the company
# is plausibly venture-backed, fall back to the expensive live search:
execute crunchbase/search {keywords: "<company name>", count: 3}   # 20cr/50 — last resort
execute crunchbase/company {company: "<alias>"}
  → funding_rounds[] (date, type, amount, lead investors)
  → leadership_hires[] (date, role, description) — measured live: EMPTY on 6 of 6
    SMB/startup accounts (incl. a 281-person, 10-year-old company; sample: US tech/AI).
    Never build the Act-now tier on its presence for that ICP; empty ≠ "no hires"
  → news[] (title, date, publisher)
  → layoffs[]
  → bombora_surges[] (free intent bonus: topics the account's staff is researching.
    Count it ONLY if a topic matches the user's product category — it reflects what
    they buy, not that they need you; weak-moderate on its own, good as a stack booster)

Alias hygiene: aliases are case-sensitive (412 on miss → re-resolve once, likely rebrand). Keep a name → alias table in the local profile file so future sweeps skip resolution entirely — the profile is a local file, it works even when CRM custom fields can't be created. Coverage honesty: crunchbase_link is filled mostly for venture-backed companies (≈3/10 in a live batch); bootstrapped/service companies often have NO Crunchbase record — for them skip the crunchbase probe entirely instead of fuzzy-searching a wrong match.