Growth & Digital/ICP Targeting
EDIT VIA GITHUB · /contentICP Targeting
The Redis ICP definition — verbatim from the Keyplay data dictionary (Jan 2026): core fields, tiering logic, and every enrichment field the R500 candidate calculation runs on.
MARKETS
2
Digital Native · Traditional Enterprise
TIERS
A–D
Keyplay model score → AI-reviewed final tier
R500
candidate rule
the one field computed via explicit logic
GRAIN
1 row / CRM record
upload key: CRM ID · canonical: Final Domain
Data Dictionary — Keyplay Core Fields
Overview
Purpose: Core Keyplay enrichment fields exported for CRM upload + account analysis. Grain: 1 row per CRM company record (multiple records may map to the same company via Final Domain). Primary upload key: CRM ID
Core Fields
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| CRM ID | string | 0013z00002LZXQFAA5 | Unique CRM record identifier used as the key for uploads. | Use this to map back into Salesforce. |
| Input Domain | string | example.com | The domain pulled from the CRM “Website” field (raw input domain). | May include redirects / non-canonical domains. |
| Name | string | Acme Corp | Company name resolved via LinkedIn lookup. | Best-effort enrichment (source: LinkedIn) |
| Final Domain | string | acme.com | Canonical domain after following redirects to the final landing domain. | Used for deduping and consistent enrichment across CRM records. |
| Dupe? | boolean (0 / 1) | 0 | Flags whether this CRM record is a duplicate of another record that resolves to the same Final Domain. | 0 = primary record (chosen by revenue or alphabetical). 1 = duplicate. All rows still get enriched. Deduping used to analysis and counting. |
| Market | string | Digital Native | Market classification for the company. | Traditional vs Digital Native. |
| Segment | string | Financial Services & Fintech | Keyplay segment assigned to the company. | Single select |
| R500 Candidate | Boolean (TRUE / FALSE) | true | Indicates whether the company qualifies as a Redis 500 candidate. | Described as the only field computed via a specific logical rule. |
| ICP Tier (Final AI Reviewed) | single select | A | Final ICP tier after an AI review pass. | Single select |
| ICP Tier (Keyplay Model) | single select | A | Tier produced directly by the Keyplay scoring model. | Deterministic based on ICP Score (Model) for the best fit Market (digital or traditional) |
| ICP Score (Model) | number | 86 | Numeric ICP fit score output by the Keyplay model. | Input used to compute ICP Tier (Keyplay Model). |
| ICP Fit Reasoning | Long text | Large regulated financial enterprise (81k employees, \~12k engineers) with very high real-time dependency for payments/authorization and fraud detection, public-cloud deployments and active AI hiring — clear need for millisecond latency, geo‑replication, SLA/compliance support and platform consolidation; research gaps: current caching/datastore stack and PCI/regional certs. | Short explanation of why the company received its score/tier. | Intended to be rep-friendly CRM context (2–3 sentences). |
Key Relationships / Logic
- Upload key: CRM ID
- Company canonical identifier (for grouping): Final Domain
- Deduping for analysis: Use Dupe? = 0 to avoid double counting across records that share a Final Domain.
- Tiering logic flow: ICP Score (Model) → ICP Tier (Keyplay Model) → ICP Tier (Final AI Reviewed) → R500 Candidate
Data Dictionary — Additional Enrichments (Optional)
Overview
Purpose: Optional enrichment fields available in the export. Primary use: These fields feed the R500 Candidate (Final) calculation. Note: Outside of the R500 candidate logic, these fields are optional and used for deeper segmentation, filtering, and rep context.
Additional Enrichment Fields
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Final LinkedIn | URL | https://www.linkedin.com/company/microsoft | Canonical LinkedIn company profile URL used for enrichment. | Source anchor for several fields. |
Digital Native Model Outputs
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Digital Native Fit Score | number (0–100) | 74 | Overall fit score for the Digital Native ICP model. | Higher = better fit. |
| Digital Native Most Similar To | string / domain | stripe.com | Reference company the record is most similar to within Digital Native clustering. | Used for explainability. |
| Digital Native Signal Score | number (0–100) | 74 | Score contribution from signals (rules/attributes) for Digital Native fit. | Component score. |
| Digital Native Similarity Score | number (0–100) | 0 | Score contribution from vector similarity / nearest neighbors for Digital Native fit. | Component score. |
| Digital Native Signals | multi-select (text list) | Software & Cloud Tech, Hiring, Using Public Cloud... | Human-readable list of signals detected for Digital Native evaluation. | Used in R500 logic + debugging. |
| Digital Native Tier | single select (A/B/C/D) | A | Tier bucket for Digital Native fit. | Derived from Digital Native scores. |
Traditional Enterprise Model Outputs
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Traditional Enterprise Fit Score | number (0–100) | 90 | Overall fit score for the Traditional Enterprise ICP model. | Higher = better fit. |
| Traditional Enterprise Most Similar To | string / domain | apple.com | Reference company the record is most similar to within Traditional Enterprise clustering. | Used for explainability. |
| Traditional Enterprise Signal Score | number (0–100) | 90 | Score contribution from signals for Traditional Enterprise fit. | Component score. |
| Traditional Enterprise Similarity Score | number (0–100) | 60 | Score contribution from similarity for Traditional Enterprise fit. | Component score. |
| Traditional Enterprise Signals | multi-select (text list) | Employees 5001+, Traffic Rank Top 100K... | Human-readable list of detected signals for Traditional Enterprise evaluation. | Used in R500 logic + debugging. |
| Traditional Enterprise Tier | single select (A/B/C/D) | A | Tier bucket for Traditional Enterprise fit. | Derived from Traditional Enterprise scores. |
Intent Model Outputs
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Intent Tier | single select (A/B/C/D/none) | none | Bucketed intent strength for near-term buying signals. | none means no intent detected. |
| Intent Score | number (0–100) | 0 | Numeric intent score. | Often 0 for “no intent.” |
| Intent Signals | multi-select (text list) | Jobs mention Real-Time, Hiring spike... | Detected intent-related signals that contribute to the score. | Used in R500 calc when present. |
Company Profile & Categorization
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Business Overview | text | Multifaceted business model... | Short company description / summary. | Rep context + model explainability. |
| Primary Category | multi-select | Media & Entertainment, SaaS & Cloud | Primary industry/category tags. | Category taxonomy is Keyplay-defined. |
| Secondary Category | multi-select | Collaboration & Productivity... | Additional product/industry categories. | Used for filtering and segmentation. |
| Audience | multi-select | B2B, B2C | Primary go-to-market audience. | Often multiple. |
Company Size, Growth, Hiring
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Employees | number | 225865 | Estimated employee count. | Typically from LinkedIn or similar sources. |
| Year Founded | number (YYYY) | 1975 | Company founding year. | Used for maturity heuristics. |
| Headcount Growth (6 mo) | number (ratio/%) | \-0.05 | Headcount growth over the last 6 months. | Negative indicates shrinkage. |
| Headcount Growth (1 mo) | number (ratio/%) | 0.02 | Headcount growth over the last month. | Short-term momentum signal. |
| Hiring | number | 2464 | Count of open roles or hiring signal volume. | Interpret based on your data source. |
| Open Roles / Total Headcount | number (ratio) | 0.01 | Open roles divided by employee count. | Hiring intensity proxy. |
| Recruiting Velocity Score | number | 21.82 | Composite score for hiring velocity. | Used as a normalized hiring metric. |
Traffic & Social Signals
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Traffic Rank | number | 3 | Website traffic rank bucket/value. | Lower often implies higher traffic (depends on source). |
| Follower Count | number | 27062289 | LinkedIn follower count. | Company popularity / reach. |
| Follower Change (6 mo) | number (ratio/%) | 0.06 | Change in followers over the last 6 months. | Growth signal. |
| Follower Change (1 mo) | number (ratio/%) | 0.01 | Change in followers over the last month. | Short-term growth signal. |
Public Company Info
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Stock Ticker | string | NASDAQ:MSFT | Public market ticker identifier. | Optional; only populated when applicable. |
Headquarters & Locations
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| HQ Country | string | US | HQ country. | ISO-like shorthand is common. |
| HQ City | string | Redmond | HQ city. | |
| HQ State | string | Washington | HQ state/region. | US-specific field when applicable. |
| HQ Postal Code | string | 98052 | HQ postal code. | Optional. |
| Location Cities | multi-select (text list) | Bratislava, Reading, Singapore... | Cities where the company has locations. | Can include noisy/unicode entries. |
| Location States | multi-select (text list) | Ontario, Dublin, Tokyo... | States/regions where the company has locations. | Source-dependent formatting. |
| Location Countries | multi-select (text list) | US, CA, GB... | Countries where the company has locations. | Useful for geo filtering. |
| Location Count | number | 44 | Count of distinct locations detected. | Proxy for global footprint. |
Funding
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Total Funding | number | 1000000 | Total funding raised (if known). | May be blank for public/bootstrapped firms. |
| Last Funding Date | date | 12/9/22 | Date of most recent funding round. | Format may vary by export settings. |
Internal Flags & CRM Metadata
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Tags | multi-select | *(blank)* | Freeform tags associated with the company. | Optional annotation layer. |
| Status | single select | Ok | Processing/status flag for the enrichment output. | Useful for QA. |
| In SAM | boolean (yes/no) | yes | Indicates whether the account is in the Serviceable Available Market. | A gating filter before ICP. |
| In CRM | boolean (yes/no) | yes | Indicates whether the company already exists in CRM. | Useful for backfills. |
| Account Source | single select | CRM | Where the account record originated. | Example: CRM, imports, etc. |
Assets & Links
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Logo Url | URL | https://media.licdn.com/... | Company logo URL (often LinkedIn-hosted). | Useful for UI/display. |
| Job Board URL | URL | https://www.linkedin.com/company/microsoft/jobs/ | Primary jobs page link. | Hiring validation + sales trigger. |
AI-Derived Categorization Fields (with reasoning)
| Field | Type | Example | Description | Notes |
|---|---|---|---|---|
| Digital Native vs Traditional (Category) | single select | Traditional Enterprise | AI classification of company as digital native vs traditional. | Used in segmentation and R500 logic. |
| Digital Native vs Traditional (Category) Reasoning | text | Founded in 1975... | Explanation for the category assignment. | Rep + audit trail. |
| Key Segments (Category) | single select | Software & Cloud Tech | AI classification into a key segment category. | Higher-level version of Segment. |
| Key Segments (Category) Reasoning | text | Primarily develops software... | Explanation for segment assignment. | Auditability. |
| Software Engineers (Team Size) | single select | 50+ | Estimated engineering team size bucket. | Bucketed, not exact. |
| Software Engineers (Team Size) Reasoning | text | Found 115,740... | Explanation for the team-size estimate. | Useful for trust/debugging. |
| AI-Native (Boolean) | boolean | FALSE | Whether AI is foundational to the business model. | Not “uses AI” — “built on AI.” |
| AI-Native (Boolean) Reasoning | text | Predates AI era... | Explanation for AI-native assignment. | Auditability. |
| Engineering Ideology (Rating) | rating (1–10) | 5 | Qualitative score for engineering philosophy/approach. | Interpretable heuristic score. |
| Engineering Ideology (Rating) Reasoning | text | Balances proprietary builds... | Explanation for ideology rating. | |
| Real-Time Data Dependency (Rating) | rating (1–10) | 9 | Degree to which the company depends on real-time data. | Strong R500 signal. |
| Real-Time Data Dependency (Rating) Reasoning | text | Critically depend on... | Explanation for real-time dependency rating. |
Verbatim content from the source DOCX (downloadable above). These definitions feed the 6sense segments, the Redis500 list, and tier A/B targeting — changes ripple into 004 · Signal-Based Orchestration and 002 · Paid Media.