Seven pieces of metadata. Per field.
We model this on Acxiom InfoBase and HL7 FHIR — the difference is every field carries provenance and license at the field level, not the record level. Most vendors ship a record with one timestamp. We ship a record with one timestamp per field.
Confidence on every derivation.
No value ships without a signal telling you how much to trust it. Three patterns appear throughout the dictionary.
Nothing here. Try a different search.
Identifiers
The persistent keys you use to track a lead through your CRM, your campaigns, and your conversations.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| lead_ref | Lead Reference | Text · GL-{STATE}-{NNNNN} | derived | Derived | Always | Speak about a lead in plain language: "GL-CO-12345 just hit Very Hot." Stable across enrichment cycles. |
| contact_ref | Contact Reference | Text · GLC-{NNNNN} | derived | Derived | Always | Track a person across multiple businesses. One contact may link to many entities. |
| state_entity_id | State Entity ID | Text | co_sos · fl_sunbiz · va_scc | Public | Always | The state's own ID. Use to look up the original filing. |
| source_system | Source System | Categorical · CO_SOS, FL_Sunbiz, VA_SCC | co_sos · fl_sunbiz · va_scc | Public | Always | Which state the record came from. |
Business Profile
The core firmographic record — what every B2B data product ships, normalized to a single canonical schema across 50 state formats.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| entity_name | Business Name | Text | SOS pull | Public | Always | The legal name as filed. |
| entity_type | Entity Type | Categorical · LLC, Corporation, LP, LLP, PC, PLLC, Partnership, Other | SOS pull | Public | Always | Legal structure — drives qualification rules and tax/banking pitches. |
| formation_date | Formation Date | Date · ISO 8601 | SOS pull | Public | Always | The day the business was created. Days-since-formation is the single strongest "moment of formation" signal. |
| status | Filing Status | Categorical · Active, Inactive, Dissolved, Withdrawn | SOS pull | Public | Always | Current standing with the state. |
| jurisdiction | Jurisdiction of Formation | Categorical · DOMESTIC_{ST}, FOREIGN_{ST} | SOS pull | Public | Always | Where the entity was formed (domestic vs. foreign authority). |
| officer_count | Officer Count | Integer | SOS pull | Public | FL/VA: yes; CO: ra_only | Number of officers on the filing. Drives our "is this a solopreneur" inference. |
| public_available_at | Public Available Date | Date | SOS pull | Public | Always | When the record became publicly searchable — the start of the speed-to-contact race. |
| standing_status_as_of | Standing Status As Of | Date | co_sos | Public | CO only | Date status was last refreshed with the state. |
Location & Geography
The SOS gives you a string. We give you a parsed, geocoded, census-attributed location.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| principal_address_raw | Principal Address (Raw) | Text | SOS pull | Public | Always | The address string exactly as filed. Kept for audit. |
| principal_address_normalized | Principal Address (Normalized) | Object · {street, city, state, zip, country} | derived | Derived | Always | Parsed and standardized. USPS-style normalization across 50 state formats. |
| principal_city | Principal City | Text | SOS pull | Public | Always | Geographic targeting at city granularity. |
| principal_state | Principal State | Text · 2-letter | SOS pull | Public | Always | State of the principal address (may differ from formation state for foreign filings). |
| principal_zip | Principal ZIP | Text | SOS pull | Public | Always | ZIP-level targeting and DMA rollup. |
| mailing_address_raw | Mailing Address (Raw) | Text | SOS pull | Public | State-dependent | Where the business receives mail (often a personal address — strong contact signal). |
| mailing_address_normalized | Mailing Address (Normalized) | Object | derived | Derived | State-dependent | Parsed mailing address. |
| mailing_city | Mailing City | Text | SOS pull | Public | State-dependent | — |
| mailing_state | Mailing State | Text · 2-letter | SOS pull | Public | State-dependent | — |
| mailing_zip | Mailing ZIP | Text | SOS pull | Public | State-dependent | — |
| latitude | Latitude | Numeric · decimal degrees | us_census_geocoder | Public | ~92% | Map placement, radius search, drive-time targeting. |
| longitude | Longitude | Numeric · decimal degrees | us_census_geocoder | Public | ~92% | Same as above. |
| geocode_status | Geocode Match Status | Categorical · Match, No_Match, Tie | us_census_geocoder | Derived | Always | Whether the address geocoded cleanly. Tie flags ambiguous addresses. |
| county_fips | County FIPS Code | Text · 5 digits | us_census_geocoder | Public | ~92% | Federal county code. Joins to BLS, IRS, and FEMA data. |
| census_tract | Census Tract | Text · 11 digits | us_census_geocoder | Public | ~92% | Demographic and income-band rollups via ACS data. |
Industry Classification
We don't buy NAICS/SIC from a third party. We classify every entity ourselves at load time — rule-based fusion of suffix patterns, keyword matching, and entity-type rules. Confidence ships with every value.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| industry_sector | Industry Sector | Categorical · 14 values incl. Healthcare, Construction, Technology, Real Estate, Finance, Retail, Manufacturing, Hospitality, Transportation | classification_svc | Derived | ~96% | High-level segmentation for campaign routing. |
| industry_name | Industry | Categorical · 113 values (Psychology, Landscaping, Software Development, Property Management, Accounting, Dental Practice…) | classification_svc | Derived | ~96% | Granular industry — the right altitude for vertical-specific outreach. |
| industry_formation_code | Industry Code | Text · hierarchical (HC-PSY, CON-LAND…) | classification_svc | Derived | ~96% | Stable code for joins and CRM mappings. |
| industry_confidence_score | Industry Confidence | Numeric · 0.0–1.0 | classification_svc | Derived | ~96% | Numeric confidence from the fusion classifier. |
| industry_confidence_tier | Industry Confidence Tier | Categorical · confirmed (≥0.85), likely (≥0.60), possible (≥0.40), unknown (<0.40) | classification_svc | Derived | Always | Decision rule for downstream filtering — most teams target confirmed + likely only. |
| industry_signals_count | Classifier Signals | Integer | classification_svc | Derived | Always | How many independent signals agreed on the classification. Higher = more robust. |
Property Intelligence
Where most B2B data products end, we begin. Every principal address joined against ~16M parcel boundaries. A residential principal address is a different sales motion than a commercial one — we surface that distinction at load time.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| property_classification | Property Type | Categorical · RESIDENTIAL, COMMERCIAL, INDUSTRIAL, AGRICULTURAL, MULTI_FAMILY, MIXED_USE, VACANT, EXEMPT, UNKNOWN | property_classification_svc | Derived | ~83% | Distinguish home-based businesses from offices. Filter out shell companies (vacant). |
| property_classification_raw | Property Type (Raw Code) | Text | property_classification_svc | Public | ~83% | The unmodified county property-use code. |
| property_type_detail | Property Subtype | Text · Single Family, Condo, Office Building, Warehouse, Apartment… | property_classification_svc | Public | ~83% | Sub-type granularity from county records. |
| property_is_vacant | Is Vacant | Boolean | property_classification_svc | Derived | ~83% | Strong shell-company signal — vacant principal address = exclude. |
| property_assessed_value | Assessed Value | Integer · USD | property_classification_svc | Public | ~83% | County-assessed total value. Proxy for owner net worth and account size. |
| property_lookup_confidence | Property Match Confidence | Categorical · MATCHED, NEAREST, NO_MATCH | property_classification_svc | Derived | Always | How confident the spatial join is. MATCHED = exact parcel; NEAREST = best guess within 50m. |
| parcel_id | Parcel ID | Text | property_classification_svc | Public | ~83% | County parcel identifier for deeper records lookup. |
| data_vintage | Property Data Vintage | Date | property_classification_svc | Public | ~83% | When the parcel data was last published — tells you how fresh the assessed value is. |
Registered Agent Intelligence
Proprietary IP. The SOS gives you an RA name and address. We give you cross-state volume, market tier, formation-service brand attribution, and a GTM segment — all derived from a curated registry built from SEC filings, BBB records, and acquisition tracking.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| registered_agent_name | Registered Agent Name | Text | SOS pull | Public | Always | The named RA on the filing. |
| registered_agent_address_raw | RA Address (Raw) | Text | SOS pull | Public | Always | Raw RA address. |
| registered_agent_address_normalized | RA Address (Normalized) | Object | derived | Derived | Always | Parsed RA address. |
| ra_type | RA Type | Categorical · P (Person), C (Corporation) | fl_sunbiz | Public | FL only | Person or commercial RA service. |
| ra_self_represented | Self-Represented | Boolean | derived | Derived | Always | True if the owner filed as their own RA — strong "founder-led, no formation service" signal. |
| ra_market_tier | RA Market Tier | Categorical · premium ($300+/yr), midmarket ($100–200), budget ($0–50), local, individual, suspicious, unknown | ra_intelligence_svc | Derived | Always | Indicates the price tier the founder paid for formation help. Premium = mature / cost-insensitive; Budget = price-shopping DIY founder. |
| ra_entity_volume | RA Entity Volume (Cross-State) | Integer | ra_intelligence_svc | Derived | Always | How many entities this RA serves across our entire dataset. |
| ra_address_cluster_count | RA Address Cluster Size | Integer | derived | Derived | Always | Number of entities sharing the exact RA address — flags shared commercial offices and mail-drops. |
| ra_is_attorney | RA Is Attorney | Boolean | ra_intelligence_svc | Derived | Always | Attorney-as-RA pattern. Strong signal of premium legal-services formation path — different motion than DIY founders. |
| contact_name_in_entity_name | Contact Name In Entity Name | Boolean | ra_intelligence_svc | Derived | Always | Owner's name appears in the business name (e.g. "Smith Consulting LLC"). Lifts contact-relevance and confidence. |
| gtm_segment | Go-to-Market Segment | Categorical · owner_operator, budget_formation, midmarket_formation, premium_established, suspicious_exclude, unclassified | ra_intelligence_svc | Derived | Always | The single most useful field for campaign segmentation. Combines RA tier + self-rep + jurisdiction + officer count. |
What this RA's book of business actually looks like
Beyond volume and price tier — three percentages that describe the kind of clients an RA serves. A budget RA with 95% LLC + 90% single-officer clients is selling to one persona; a premium RA with 30% foreign-filed corporates is selling to a completely different one.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| domestic_pct | Domestic Filing % | Numeric · 0–100 | ra_intelligence_svc | Derived | Always | % of this RA's clients formed in the same state where the entity is registered. High = local RA serving local businesses; low = cross-border filing operation. |
| llc_pct | LLC Mix % | Numeric · 0–100 | ra_intelligence_svc | Derived | Always | % of clients that are LLCs vs. corporations / LPs. Discount RAs skew heavily LLC; corporate-focused RAs less so. |
| single_officer_pct | Single-Officer % | Numeric · 0–100 | ra_intelligence_svc | Derived | FL / NY (officer data); CO/VA may report 0 — sparse officer data, not a bug | % of clients filing with exactly one officer/member. Proxy for "kitchen-table" small businesses vs. real operating entities. |
Formation Service Attribution
Who did this founder buy their LLC from? LegalZoom? Bizee? TailorBrands? We answer that with a curated registry of 20+ formation services and their RA subsidiaries — evidenced from SEC 10-Ks and acquisition disclosures.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| formation_service | Formation Service | Categorical · LegalZoom, ZenBusiness, Bizee, TailorBrands, Inc Authority, Northwest, IncFile, Stripe Atlas, Doola, None… | ra_intelligence_svc | Derived | ~30% (when identifiable) | Identify which formation product the founder already trusts — informs partnership conversations and competitive displacement plays. |
| ra_provider | RA Provider | Categorical · same enum as formation_service | ra_intelligence_svc | Derived | Always (when RA is a known provider) | Who operates the RA subsidiary. May differ from formation_service when ownership is layered. |
| formation_service_confidence | Attribution Confidence | Categorical · certain, very_high, high, medium, low | ra_intelligence_svc | Derived | When formation_service is set | Higher = brand name appears directly in RA. Lower = inferred from address co-location. |
| formation_service_attribution | Attribution Method | Categorical · direct, ra_only | ra_intelligence_svc | Derived | When formation_service is set | How we made the call. direct is bulletproof; ra_only requires confidence-tier filtering. |
Contact
The person you actually call. We never ship "info@" addresses or main switchboard numbers — every contact is name-matched to an officer, owner, or self-representing RA.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| contact_name | Contact Name | Text | SOS pull · tracerfy · derived | PublicEnriched | Always | Full name. From the filing when officers are listed; from skip trace otherwise. |
| role_title | Role / Title | Text · CEO, President, Owner, Manager, Member, MGR, P/S… | SOS pull | Public | State-dependent | Job title from the filing. Drives decision-maker scoring. |
| relationship_type | Relationship to Business | Categorical · OWNER, OFFICER, REGISTERED_AGENT | derived | Derived | Always | How this person relates to the business. |
| phone_primary | Primary Phone | Text · E.164 | tracerfy · enformion | Enriched | ~60% Tracerfy + gap-fill | Best phone. Mobile preferred over landline; landline preferred over VoIP. |
| phone_secondary | Secondary Phone | Text · E.164 | tracerfy | Enriched | Enriched | Second-best phone. |
| phone_tertiary | Tertiary Phone | Text · E.164 | tracerfy | Enriched | Enriched | Third-best phone. |
| email_primary | Primary Email | Text | tracerfy · enformion | Enriched | ~48% Tracerfy + gap-fill | Best email. |
| email_secondary | Secondary Email | Text | tracerfy | Enriched | Enriched | Second-best email. |
Email Validation
Every email runs through ZeroBounce. We report the result, the inbox-activity recency, and whether the name on the inbox matches the person on the filing. Most providers ship "valid" or "invalid." We ship the full diagnostic.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| zb_email_status | Deliverability Status | Categorical · valid, catch-all, abuse, invalid, unknown | zerobounce | Enriched | Enriched | Whether the email will deliver. |
| zb_email_sub_status | Deliverability Sub-Status | Categorical · alternate, mailbox_not_found, greylisted, role_based, disposable… | zerobounce | Enriched | Enriched | Detail behind the status. role_based = info@-style. alternate = better address available. |
| email_is_free_provider | Is Free Provider | Boolean | zerobounce | Enriched | Enriched | Gmail/Yahoo/Outlook/Apple flag. Personal vs corporate signal. |
| email_smtp_provider | Email Infrastructure | Categorical · google, microsoft, yahoo, apple, comcast, rackspace… | zerobounce | Enriched | Enriched | Who runs the inbox. Tier-1 providers (Google, Microsoft) deliver more reliably. |
| email_mx_found | MX Records Present | Boolean | zerobounce | Enriched | Enriched | Prerequisite for delivery. |
| email_mx_record | MX Record | Text | zerobounce | Enriched | Enriched | The actual MX string. |
| email_domain_age_days | Domain Age (Days) | Integer | zerobounce | Enriched | Enriched | Domain age. New domains = higher spam risk. |
| email_activity_found | Inbox Activity Detected | Boolean | zerobounce | Enriched | Enriched | The strongest "is this person reading mail" signal we have. |
| email_active_in_days | Days Since Last Activity | Integer / categorical · 60, 90, 180, 365, 365+ | zerobounce | Enriched | Enriched | Recency of inbox activity. Drives the Reachability score. |
| zb_name_first | Inbox Account First Name | Text | zerobounce | Enriched | Enriched | The first name registered on the inbox account. |
| zb_name_last | Inbox Account Last Name | Text | zerobounce | Enriched | Enriched | Last name registered on the inbox. |
| email_name_verification | Name vs. Filing Match | Categorical · FULL_MATCH, LAST_MATCH, FIRST_MATCH, NO_MATCH | derived | Derived | Enriched | Does the name on the inbox match the name on the filing? Catches forwarded inboxes, family-shared addresses, and impersonation. |
Phone Validation
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| phone_validity | Phone Validity | Categorical · MOBILE_VALID, LANDLINE_VALID, VOIP_VALID, INVALID, UNKNOWN | tracerfy | Enriched | Enriched | Active mobile, landline, or VoIP. Mobile has the highest connect rate. |
| enf_phone_primary | Gap-Fill Phone | Text · E.164 | enformion | Enriched | Gap-fill only | Best phone from EnformionGo when Tracerfy missed. |
| enf_phone_connected | Gap-Fill Phone Active | Boolean | enformion | Enriched | Enriched | Whether the gap-fill phone is currently connected. |
| enf_phone_last_seen | Gap-Fill Phone Last Seen | Date | enformion | Enriched | Enriched | Most recent date the number was reported active. |
Reachability Score
0–100 composite answering one question: can we reach this person? Every component ships alongside the score. See exactly how it was built. Tune your own thresholds.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| reachability_score | Reachability Score | Integer · 0–100 | scoring_svc | Derived | Always | The headline score. Tunable threshold for cohort selection. |
| reachability_tier | Reachability Tier | Categorical · On Fire (80–100), Very Hot (60–79), Hot (40–59), Warm (20–39), Cold (0–19) | scoring_svc | Derived | Always | Named tier — drop into a CRM lifecycle stage without further work. |
Shipped in the parameters payload
| Component | Max points | What it measures |
|---|---|---|
| email_validity_pts | 25 | ZeroBounce status — valid and catch-all score highest. |
| email_activity_pts | 20 | Inbox activity recency. 0–60 days = full points. |
| phone_reach_pts | 20 | Phone availability and type. Mobile > landline > VoIP. |
| geo_intel_pts | 10 | Geocode precision — lat/lon + county + census tract all present. |
| name_verify_pts | 10 | First/last name match between ZeroBounce inbox and SOS filing. |
| identity_conf_pts | 10 | Skip-trace identity confidence (Tracerfy name match). |
| email_infra_pts | 5 | Top-tier email provider + MX records present. |
| industry_bonus_pts | 5 | Industry classification confidence bonus. |
Once a record reaches a score, a subsequent reload cannot lower it. Paid enrichment is irreversible — the data is too.
Contact Relevance Score
0–100 composite answering an orthogonal question: is this the RIGHT person to sell to? A contact can be highly reachable but the wrong person — a commercial RA employee instead of the founder. This score separates them.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| contact_relevance_score | Contact Relevance Score | Integer · 0–100 | scoring_svc | Derived | Always | Headline relevance score — decision-maker proxy. |
| contact_relevance_tier | Contact Relevance Tier | Categorical · Decision Maker (85–100), Likely Decision Maker (65–84), Probable Contact (45–64), Uncertain Contact (25–44), Unlikely Decision Maker (0–24) | scoring_svc | Derived | Always | Named tier — most teams target Decision Maker + Likely. |
Shipped in the parameters payload
| Component | Max points | What it measures |
|---|---|---|
| self_representation_pts | 25 | Self-rep RA + individual RA = founder filing alone. |
| contact_name_source_pts | 20 | Officer (best) > Owner > RA person > Commercial RA. |
| location_uniqueness_pts | 20 | How many entities share this lat/lon. Unique = real address. |
| contact_exclusivity_pts | 15 | How many entities this contact links to. 1 = exclusive; 51+ = shared mail-drop. |
| name_in_entity_pts | 10 | Person's name appears in the business name (e.g. "Smith Consulting LLC"). |
| ra_tier_pts | 5 | Individual RA scores higher than commercial. |
| entity_type_pts | 5 | Domestic LLC + 1 officer = highest. |
| interaction_penalty | −10 | Applied when contact is on 4+ entities AND 6+ entities share location. Catches commercial-RA office pattern. |
Contact Confidence Score
0–100 composite answering a third orthogonal question: are we confident this email or phone really belongs to this person? A reachable, relevant contact can still be the wrong identity — a forwarded inbox, a family-shared phone, a name collision. This score isolates that risk.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| contact_confidence_score | Contact Confidence Score | Integer · 5–100 (floor of 5; never zero) | scoring_svc · contact_confidence_v1.1 | Derived | Always | Headline identity-confidence score. Pair with Reachability + Relevance for a three-axis lead-quality picture. |
| contact_confidence_tier | Contact Confidence Tier | Categorical · Verified Contact (75–100), Likely Contact (50–74), Possible Contact (25–49), Uncertain Contact (5–24) | scoring_svc · contact_confidence_v1.1 | Derived | Always | Named tier — most teams gate outbound at Verified + Likely. |
Five weighted signals · sum to 100
| Component | Max points | What it measures |
|---|---|---|
| email_name_match | 30 | Does the email local-part contain name tokens that match the filing? Strongest single identity signal. |
| zb_quality | 20 | ZeroBounce validity + recent inbox activity (someone is actually reading this mailbox). |
| phone_ra_alignment | 20 | Mobile phone + self-represented RA = the founder's personal line. Strongest paired identity signal. |
| property_context | 15 | Residential principal address raises confidence (vs. shared commercial / virtual-office address). |
| ra_self_rep | 15 | Self-rep RA = the contact almost certainly IS the founder, not an employee or RA service rep. |
Reachability answers "can we reach them?" · Relevance answers "are they the right person?" · Confidence answers "is this contact really them?" A lead can be high on any two and low on the third. Most providers ship one score (or none). We ship all three, with components.
Pre-Enrichment Strategy
Before we spend a single skip-trace credit, our Contact Intelligence service decides how to enrich each entity. This is the field that explains why some leads got 2-credit advanced traces and others got 1-credit basic.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| enrichment_strategy | Enrichment Strategy | Categorical · name_and_address, address_only, mailing_fallback, hold | contact_intelligence_svc | Derived | Always | The strategy we used (or would use) for skip-tracing this entity. |
| name_confidence | Name Confidence | Categorical · high, medium, low | contact_intelligence_svc | Derived | Always | How confident we are that the contact name is a real, unique person. |
| address_confidence | Address Confidence | Categorical · high, medium, low | contact_intelligence_svc | Derived | Always | How confident we are that the address is a real, residential, non-shared location. |
| name_density | Name Density | Integer | contact_intelligence_svc | Derived | Always | Number of entities sharing the same contact name. High = generic/common name (lower identity confidence); 1 = unique person. |
| address_density | Address Density | Integer | contact_intelligence_svc | Derived | Always | Number of entities at the same principal address. 1 = real address; 50+ = mail-drop / virtual office / commercial RA building. |
| cross_state_contact_count | Cross-State Contact Count | Integer · 1–4 | contact_intelligence_svc | Derived | Always | How many of the live states this contact name appears in. Multi-state presence is a strong serial-founder / professional-filer signal. |
Gap-Fill Vendor Data
When Tracerfy can't find a contact, we fall back to EnformionGo. These fields show up only on records where the gap-fill ran.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| enf_identity_score | Gap-Fill Identity Score | Integer · 0–100 | enformion | Enriched | Gap-fill only | EnformionGo's own match-confidence score. Average ≥96 on matches. |
| enf_email_primary | Gap-Fill Email | Text | enformion | Enriched | Gap-fill only | Best email from gap-fill when Tracerfy missed. |
| enf_age | Estimated Age | Integer | enformion | Enriched | Gap-fill only | Reported age — useful for life-stage targeting. |
Provenance & Audit
Every value above ships with three pieces of audit metadata. Available on request via the provenance sidecar export.
| Field | Label | Type | Source | License | Coverage | Use case |
|---|---|---|---|---|---|---|
| source_name | Source (per attribute) | Text | derived | Derived | Always | Where this specific value came from. Per-field, not per-record. |
| license_flags | License (per attribute) | Categorical · PUBLIC_RECORD, ENRICHED, DERIVED | derived | Derived | Always | Licensing tier — drives compliance and data-sharing rules. |
| observed_at | Observed Timestamp (per attribute) | DateTime · ISO 8601 | derived | Derived | Always | When this specific value was captured or last refreshed. |
| score_version | Score Version | Text · semver | scoring_svc | Derived | Always | The scoring algorithm version that produced this record's scores. Lets you reason about model drift. |
Coverage by State
Observed fill rates from production runs (refreshed monthly), plus forward-looking forecasts for newly-onboarded states. Forecasts are dashed and prefixed with "~" so they're not mistaken for measurement — they reflect the deal-requirement floors (45% phone / 35% email) and the average of established states.
data-status="observed" · production fill rate
Dashed cell = data-status="forecast" · projection · not yet measured
| Stage / Source | CO | FL | VA | NY | GA next |
|---|---|---|---|---|---|
| SOS filing fields | 100% | 100% | 100% | 100% | 100% |
| Geocoding | 90% | 92% | 93% | 92% | — |
| Industry classification | 95% | 96% | 96% | 96% | — |
| Property classification | 76% | 88% | 84% | 80% | — |
| RA intelligence | 100% | 100% | 100% | 100% | — |
| Skip-trace phone | 56% | 64% | 87% | 45% | — |
| Skip-trace email | 41% | 53% | 59% | 35% | — |
| Email validation | 48% | 48% | 48% | 48% | — |
| Reachability score | 100% | 100% | 100% | 100% | — |
| Contact Relevance score | 100% | 100% | 100% | 100% | — |
| Contact Confidence score | 100% | 100% | 100% | 100% | — |
What's Different
A scraper ships you SOS data with a timestamp. We ship you the same SOS data — plus six things nobody else delivers.
Three Orthogonal Scores
Reachability ("can we reach them?"), Contact Relevance ("are they the right person?"), Contact Confidence ("is this contact really them?"). Plus 15+ derived classifications — Industry, Property Type, RA Market Tier, GTM Segment, Formation Service, RA Portfolio Shape, Density signals, Enrichment Strategy. All computed by us.
Cross-State Entity Resolution
Same RA, same contact — identified across CO, FL, VA at load time. Without you doing any joins.
Per-Field Provenance
Every value carries source, license, and timestamp. Audit any cell. Most vendors ship one timestamp per record. We ship one per field.
Per-State Semantic Mapping
"What does mailing address mean in NY vs FL vs CO." We've solved that. Your CRM sees one canonical schema across 50 state formats.
Confidence on Every Derivation
No value ships without a tier or score telling you how much to trust it. No black boxes.
Field-Level License Classification
PUBLIC_RECORD, ENRICHED, and DERIVED tracked at the field level. Your compliance team can reason about residency, sharing, and resale.