<aside> ⚡ TLDR — Read This First
</aside>
<aside> ℹ️ How to read: 🟩 = positive fit signal, 🔴 = anti-fit. Each square ≈ 2x relative odds. Lift = (won rate) ÷ (lost rate) with Laplace smoothing.
</aside>
<aside> 🏆 ✅ Positive Fit Signals — These appear more in won deals
</aside>
| Signal | Lift | Strength | Source | What to Look For |
|---|---|---|---|---|
| account creation | 11.1x | 🟩🟩🟩🟩🟩🟩 | 🌐 Website | Website describes structured customer account opening flow |
| customer identification program (CIP) | 3.0x | 🟩🟩🟩🟩 | 🌐 Website | Exact phrase "Customer Identification Program" — BSA-mandated term |
| developer sandbox | 2.5x | 🟩🟩🟩🟩 | 🌐 Website | Sandbox environment in developer docs — API-first culture |
| zero trust architecture | 2.2x | 🟩🟩🟩 | 🌐 Website | Zero trust = mature security posture, comfortable with identity layer |
| synthetic identity fraud | 1.9x | 🟩🟩 | 🌐 Website | Blog or product page mentions synthetic identity fraud |
| FDIC mention | 1.6x | 🟩🟩 | 🌐 Website | FDIC-regulated or FDIC-partner fintech = required BSA compliance |
| account takeover (ATO) | 1.6x | 🟩🟩 | 🌐 Website | ATO awareness = companies with real user account risk |
| fraud leadership hiring | 1.8x | 🟩🟩 | 💼 Jobs | Open roles: Head of Fraud, VP Risk, VP Fraud Ops — budget signal |
| anti-money laundering (AML) | 1.5x | 🟩🟩 | 🌐 Website | AML compliance program = mandatory identity verification at onboarding |
| financial operations hiring | 1.4x | 🟩 | 💼 Jobs | CFO, Payments, Treasury roles = finance stakeholders in buying committee |
| Braze (tech stack) | 3.7x | 🟩🟩🟩🟩 | 💻 Tech | Enterprise lifecycle messaging = large, active user base to verify |
| Stripe (tech stack) | 1.8x | 🟩🟩 | 💻 Tech | Developer-forward payments stack |
| Adyen (tech stack) | 5.1x | 🟩🟩🟩🟩🟩 | 💻 Tech | Enterprise payment infra = high-volume, sophisticated payment operator |
<aside> 🚩 🚫 Anti-Fit Signals — These appear more in lost deals or indicate an existing solution
</aside>
| Signal | Lift | Risk | Why |
|---|---|---|---|
| adverse media screening | 0.08x | 🟥🟥🟥🟥🟥 | Advanced AML stack = existing IDV solution in place |
| kubernetes + terraform + docker (all present) | 0.06x | 🟥🟥🟥🟥🟥🟥 | Heavy DevOps = internal build culture, won't buy IDV tooling |
| SOC 2 Type II (actively marketed) | 0.14x | 🟥🟥🟥🟥🟥 | Strict vendor certification posture = complex, slow procurement |
| politically exposed person (PEP) screening | 0.28x | 🟥🟥🟥 | Sophisticated AML ops = PEP screening vendor already selected |
| document verification (standalone focus) | 0.34x | 🟥🟥🟥 | Already using dedicated doc verification vendor (Mitek, Onfido) |
| ISO 27001 (prominently marketed) | 0.34x | 🟥🟥🟥 | Strict vendor certification requirements, may require ISO 27001 from you |
| liveness check (as core offering) | 0.43x | 🟥🟥 | Liveness-first = already has biometric IDV vendor |
| IPO in progress | 0.40x | 🟥🟥 | Pre-IPO procurement is frozen during lock-up period |
| Azure (only cloud) | 0.22x | 🟥🟥🟥🟥 | Microsoft ecosystem lock-in = may prefer Microsoft identity tools |
| Snowflake (prominent) | 0.20x | 🟥🟥🟥🟥 | Data warehouse focus = internal ML/analytics culture, build preference |
<aside> ℹ️ Direct Apollo links — click to open a pre-filtered search. Adjust headcount range or location as needed. Best results: add US + 100–1,000 employees for mid-market fintech.
</aside>