CRMs accumulate duplicates and inactive accounts, wasting SDR time and inflating pipeline. Salesforce and HubSpot surface duplicates and clean fields, but they don’t resolve viability: a bankrupt entity looks as good as a healthy one, and multi-BU CRMs remain fragmented.
This segment merges duplicates, normalizes identifiers, and overlays solvency to flag viable accounts — delivering a re-import-ready watchlist that is both clean and strategically filtered.
Match CRM records to verified external company IDs.
Detect and cluster duplicates into one entity.
Normalize names and domains, preserving CRM IDs.
Overlay solvency, turnover, and active status for viability.
Apply merge rules: external source trumps CRM, log conflicts.
Generate comments per record for analyst and RevOps traceability.
This segment is activated with a blend of trusted sources and your own inputs
AI reasoning
Curated APIs
Web intelligence
User Input
A deduplicated, viability-flagged account list ready for pipeline cleaning.
Normalized fields (names, domains, IDs) with full traceability.
Conflict log and merge comments for analyst and RevOps transparency.
Viability scoring based on solvency and activity, not just CRM status.
Ready-to-use exports for Salesforce, HubSpot, or MS Dynamics.
Your questions on this segment, answered
Your questions on this segment, answered
What’s the value for RevOps or Finance teams?
RevOps gain a clean, viable account universe for segmentation and routing. Finance teams gain confidence that reported pipeline is tied to solvent and active companies, reducing risk in forecasting.
Will this process overwrite our CRM data?
No. Your raw CRM IDs are preserved. Normalized and enriched fields are delivered in parallel, so you can re-import them or run them alongside your existing structure.
How does this improve our pipeline quality in practice?
It removes inflated pipeline caused by duplicates or bankrupt entities, ensuring SDRs and account teams focus only on accounts that are real, solvent, and active.
Can we trust the system with complex, multi-entity CRMs across regions or BUs?
Yes. The segment reconciles records against verified external IDs and applies clear conflict-resolution rules, so you get one clean, auditable record per company.
What exactly is a “viability score”?
It combines solvency (creditworthiness) and active business status. A company that is insolvent or inactive will be flagged, even if it looks valid in your CRM.
How does this segment differ from the built-in deduplication features of Salesforce or HubSpot?
Native tools remove duplicate fields, but they don’t validate viability. Our segment consolidates duplicates across systems, normalizes identifiers, and overlays solvency and activity to ensure only viable accounts remain in your CRM.
{ "_meta": { "dictionaryColumns": ["Variable", "Data_Type", "Sample_Value", "Description"] }, "data": [ { "Variable": "crm_account_id_input", "Description": "Original CRM account identifier from client system", "Business_Rules": "Pass-through; not altered", "Source_System": "CRM", "Data_Type": "VARCHAR", "Sample_Value": "SFDC_001" }, { "Variable": "company_name_input", "Description": "Raw company name as stored in CRM", "Business_Rules": "Free text; may be duplicated or stale", "Source_System": "CRM", "Data_Type": "VARCHAR", "Sample_Value": "FinServe Nordic" }, { "Variable": "website_input", "Description": "Raw website value from CRM", "Business_Rules": "May be missing or not canonical", "Source_System": "CRM", "Data_Type": "VARCHAR", "Sample_Value": "finservenordic.com" }, { "Variable": "vat_id_input", "Description": "Raw VAT/registration ID from CRM (if present)", "Business_Rules": "Unvalidated; optional", "Source_System": "CRM", "Data_Type": "VARCHAR", "Sample_Value": "SE556677-1234" }, { "Variable": "company_name_normalized", "Description": "Standardized legal/company name", "Business_Rules": "External reference is source of truth", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "FinServe Nordic AB" }, { "Variable": "website_domain_verified", "Description": "Verified canonical domain for the company", "Business_Rules": "Active, resolvable domain", "Source_System": "Web Intelligence", "Data_Type": "VARCHAR", "Sample_Value": "finservenordic.se" }, { "Variable": "company_id_external", "Description": "Stable external company identifier for cross-system mapping", "Business_Rules": "Unique; used to cluster duplicates", "Source_System": "Curated APIs", "Data_Type": "VARCHAR", "Sample_Value": "CS_100045" }, { "Variable": "duplicate_cluster_id", "Description": "Identifier for a group of CRM records matched to one entity", "Business_Rules": "Same value across merged records", "Source_System": "Web+AI Reasoning", "Data_Type": "VARCHAR", "Sample_Value": "CL_01" }, { "Variable": "match_confidence", "Description": "Similarity score of CRM record to verified entity", "Business_Rules": "0–100; review threshold typically 85", "Source_System": "Web+AI Reasoning", "Data_Type": "INTEGER", "Sample_Value": "95" }, { "Variable": "master_record_preference", "Description": "Rule applied when CRM and external disagree", "Business_Rules": "ENUM: external_source|crm_source|custom_rule", "Source_System": "Web+AI Reasoning", "Data_Type": "ENUM", "Sample_Value": "external_source" }, { "Variable": "merge_conflict_flag", "Description": "Whether conflicting values were detected during merge", "Business_Rules": "TRUE if any field conflict occurred", "Source_System": "Web+AI Reasoning", "Data_Type": "BOOLEAN", "Sample_Value": "true" }, { "Variable": "merge_conflict_log", "Description": "Concise log of conflicting fields and winning source", "Business_Rules": "≤280 chars; human-readable", "Source_System": "Web+AI Reasoning", "Data_Type": "TEXT", "Sample_Value": "Website mismatch (CRM .com vs verified .se): kept verified domain; name normalized." }, { "Variable": "turnover_latest", "Description": "Latest annual turnover (local currency, whole units)", "Business_Rules": ">=0; currency tracked separately", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": "320000000" }, { "Variable": "solvency_score", "Description": "Composite solvency/creditworthiness score", "Business_Rules": "0–100; higher is better", "Source_System": "Curated APIs", "Data_Type": "INTEGER", "Sample_Value": "85" }, { "Variable": "active_status_flag", "Description": "Company currently active/operating", "Business_Rules": "TRUE if active", "Source_System": "Curated APIs", "Data_Type": "BOOLEAN", "Sample_Value": "true" }, { "Variable": "viability_flag", "Description": "Viable for pipeline (solvency ≥ threshold AND active)", "Business_Rules": "Rule default: solvency ≥60 AND active", "Source_System": "Web+AI Reasoning", "Data_Type": "BOOLEAN", "Sample_Value": "true" }, { "Variable": "viability_confidence", "Description": "Confidence that viability flag is correct", "Business_Rules": "0–100; based on data freshness & match quality", "Source_System": "Web+AI Reasoning", "Data_Type": "INTEGER", "Sample_Value": "94" }, { "Variable": "custom_taxonomy_tags", "Description": "Client-defined sector/ICP tags", "Business_Rules": "Array of strings", "Source_System": "Web+AI Reasoning", "Data_Type": "ARRAY", "Sample_Value": "[\"Financial Services\"]" }, { "Variable": "overall_comment", "Description": "Short human explanation of merge + viability", "Business_Rules": "≤300 chars; plain language", "Source_System": "Web+AI Reasoning", "Data_Type": "TEXT", "Sample_Value": "Merged 2 CRM duplicates; verified domain; solvency 85, active: viable." } ] }
