Platform · Shipped
Cohort lead capture — inbound→CRM loop
Closes the signals→CRM gap for the Frontier Cohort program: an inbound niche-report request (a landing 'get the report' CTA, or a pa-site signal) becomes a first-class warm cohort prospect in the company-intelligence company-master. captureLead is idempotent on (email × niche), resolves the lead to a company-master key (named company, else the work-email domain SLD; free providers → none), and tags an EXISTING master company with a cohort-lead:<niche> signal so warm prospects surface in the same cohort queries used for benchmarking. PII (email) is captured behind a service-key POST; the only public read is aggregate + PII-free (counts by niche/status/source). Unknown lead-companies are not auto-created (the lead row is the record).
- Cluster
- Platform
- Type
- capability
- Status
- Shipped
- Used by
- people-analytics-toolbox, peopleanalyst-site
Maturity evidence
- Functioning
- 8 pure tests (identity.test.ts — leadId idempotency/case-insensitivity, email→company SLD incl. two-part TLD + free providers, companyKey resolution precedence, signal tag) + end-to-end smoke against prod DB (captured founder@acme.ai→acme, idempotent case-insensitive re-capture count→2, gmail lead→no company signal, aggregate stats correct, smoke rows deleted). Migration 0172 applied + verified. check:types-changed + check:spokes clean.
- Valuable
- Turns inbound interest (the value-first report gift) into a warm, benchmarkable cohort prospect with zero manual entry — the missing backend for the Frontier Cohort landing CTA and the pa-site signals. Warm prospects join the same cohort queries used for comp/HR/survey benchmarking.
- Understood
- company-intelligence README (Cohort leads section) + CHANGELOG 0.3.0 + Layer-1 mermaid + session report docs/session-reports/2026-07-09-cohort-lead-capture.md. Privacy stance documented (service-key capture; aggregate-only public read).
- Integrated
- Extends the live company-intelligence company-master — reuses keyOf identity + the additive-jsonb signal pattern + the cohort query surface; no new spoke. Front-end wiring (landing CTA + pa-site signals) and unknown-company promotion are war-carded follow-ups.
How to use it
- REST
- POST /api/spokes/company-intelligence/leads (service-key — PII in) · GET /api/spokes/company-intelligence/leads/stats (aggregate, PII-free)
- MCP
- company-intelligence.leads.capture | company-intelligence.leads.stats
- Data
- company_intelligence.cohort_leads (migration 0172) — first-class lead record + a cohort-lead:<niche> signal on the resolved master company
Other Platform capabilities
- Comp audit self-serve — CSV intake, free validate, commerce-gated watermarked run (HO-155)
- Gift pass — gifted ownership on the entitlement store (magic-link claim)
- JobFrame canonical Job Family × Focus × Level taxonomy + classifier
- SMB pay-system wizard — chocolate/vanilla over the pay-system catalog
- Support channel — portfolio-wide /support form → ticket store → operator email
- Ask-your-data — generalizable NL→rank→tier→cite spoke (HO-378)
- Diagnostic acquisition — next-best-ask over a live hypothesis set
- Executive-Priorities Elicitation Instruments (static catalog)
Capability detail sourced from the People Analytics Toolbox capability feed (source of truth), snapshot retrieved 2026-07-23.