본문으로 건너뛰기
cccskills
무료GitHub에 공개

crm-data-enrichment

Enrich CRM records with firmographic and contact data, filling gaps in company and person profiles to improve segmentation, routing, and outreach quality. Use when the user requests crm data enrichment or provides relevant inputs for this workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구LinkedIn

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

CRM Data Enrichment

Enrich company and contact records in your CRM with up-to-date firmographic, technographic, and demographic data. This skill identifies gaps in existing records, sources enrichment data from available signals, merges and deduplicates entries, validates accuracy, and updates fields — giving sales teams cleaner data for segmentation, lead routing, and personalized outreach.

Workflow

  1. Identify Gaps in CRM Data — Audit the target CRM records to surface missing or outdated fields. Common gaps include annual revenue, employee count, industry classification, technology stack, direct phone numbers, verified email addresses, and current job titles. Prioritize fields that directly impact lead scoring and routing logic.

  2. Source Enrichment Data — Pull data from company websites, LinkedIn profiles, SEC filings, job postings, DNS/TXT records (for tech stack detection), press releases, and third-party data providers. Cross-reference at least two independent sources per data point to reduce single-source risk.

  3. Match and Merge Records — Align enrichment data to CRM records using deterministic matching on domain, email, or unique identifiers, supplemented by fuzzy matching on company name and location. Deduplicate records where enrichment reveals two CRM entries represent the same entity, preserving the most complete record as the primary.

  4. Validate Accuracy — Apply confidence scoring to each enriched field. Flag data points sourced from a single unverified origin as low-confidence. Cross-check revenue and headcount against recent earnings reports or LinkedIn company pages. Validate email deliverability and phone connectivity where possible.

  5. Update CRM Fields — Write validated enrichment data back to the CRM, respecting field-level permissions and avoiding overwrites of manually verified data. Log all changes with timestamps and source attribution for audit trails. Trigger downstream automations (lead scoring recalculation, territory reassignment) based on newly populated fields.

Usage

Provide the CRM records (or describe the fields and current data) you want enriched, along with which fields to prioritize. Specify the CRM system if relevant (Salesforce, HubSpot, etc.) and any enrichment constraints.

Example prompt:

Enrich this company record for NovaTech Solutions. Currently we only have the company name and domain (novatech.io). Fill in revenue, employee count, industry, headquarters, founding year, tech stack, and key contacts. Format as a before/after comparison.

Examples

Example 1: Company Record Enrichment

Input: Sparse CRM record for NovaTech Solutions.

Before:

FieldValue
Company NameNovaTech Solutions
Domainnovatech.io
Industry—
Annual Revenue—
Employee Count—
Headquarters—
Founded—
Tech Stack—
LinkedIn URL—

After Enrichment:

FieldValueSourceConfidence
Company NameNovaTech Solutions, Inc.SEC filingHigh
Domainnovatech.ioExisting—
IndustryEnterprise Software (SaaS)LinkedIn + CrunchbaseHigh
Annual Revenue$42M ARRCrunchbase Series C filingMedium
Employee Count280LinkedIn company pageHigh
HeadquartersAustin, TXCompany website footerHigh
Founded2017CrunchbaseHigh
Tech StackAWS, React, PostgreSQL, Snowflake, SegmentDNS records + job postingsMedium
LinkedIn URLlinkedin.com/company/novatech-solutionsLinkedIn searchHigh

Fields added: 7 of 7 gaps filled. Revenue flagged as medium confidence (sourced from fundraising disclosure, not audited financials).


Example 2: Contact Record Enrichment

Input: Contact record with only name and email.

Before:

FieldValue
First NameSarah
Last NameNguyen
Emails.nguyen@novatech.io
Title—
Phone—
LinkedIn—
Location—
Reports To—

After Enrichment:

FieldValueSourceConfidence
First NameSarahExisting—
Last NameNguyenExisting—
Emails.nguyen@novatech.ioExisting (verified deliverable)High
TitleVP of EngineeringLinkedIn profileHigh
Phone+1 (512) 555-0173Company directory pageMedium
LinkedInlinkedin.com/in/sarah-nguyen-engLinkedIn searchHigh
LocationAustin, TXLinkedIn profileHigh
Reports ToJames Park, CTOLinkedIn org chart + press releaseMedium

Fields added: 5 of 5 gaps filled. Phone flagged as medium confidence (directory pages can lag behind extensions changes).

Best Practices

  • Always enrich the company record before enriching associated contacts — firmographic context improves contact validation.
  • Set confidence thresholds for auto-update vs. manual review; fields below 70% confidence should be queued for human verification.
  • Preserve manually entered data by default; only overwrite when enrichment data has demonstrably higher confidence and recency.
  • Run enrichment on a recurring schedule (monthly for active pipeline accounts, quarterly for nurture) rather than one-off batches.
  • Log every field change with source and timestamp so sales reps can assess trustworthiness.
  • Respect data privacy regulations (GDPR, CCPA) — do not enrich with personal data where consent requirements are unmet.

Edge Cases

  • Domain mismatch or redirect — When a company domain redirects to a parent org, verify whether the CRM record refers to the subsidiary or parent before merging firmographic data.
  • Stale LinkedIn data — Job titles on LinkedIn can lag real-world changes by months. Cross-reference with recent press releases, company announcements, or email signature blocks for current titles.
  • Duplicate records post-enrichment — Enrichment may reveal that two CRM accounts (e.g., "NovaTech" and "NovaTech Solutions Inc.") are the same entity. Flag for merge review rather than auto-merging to prevent accidental data loss.
  • Private companies with no public financials — Revenue and funding data may be unavailable or speculative. Mark these fields as estimates with explicit confidence bands (e.g., "$30M–$50M estimated ARR").
  • Contacts with common names — When matching contacts by name alone, require a secondary identifier (domain, company, location) to avoid false positive matches. Never enrich a contact record based solely on name similarity.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

Design reproducible evaluations for AI agents with representative task sets, explicit rubrics, appropriate graders, baselines, regression gates, and failure analysis. Use when defining agent quality, comparing prompts or models, validating a release, measuring tool-use reliability, investigating regressions, or deciding whether an agent is ready for production.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

Design privacy-aware observability for AI agents using traces, spans, structured events, metrics, cost attribution, dashboards, alerts, and investigation workflows. Use when instrumenting an agent, debugging intermittent tool or model failures, defining service-level objectives, analyzing latency or spend, auditing agent decisions, or preparing production monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings. Use when defining red-team rules of engagement, assessing prompt injection or excessive agency, testing tool and identity boundaries, evaluating memory or cross-agent attacks, scoring a campaign, or verifying remediation in an approved environment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

Generate comprehensive marketing analytics reports by collecting KPIs, analyzing trends, and delivering actionable insights with attribution modeling and funnel analysis. Use when the user requests analytics reporting or provides relevant inputs for this workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

Design RESTful APIs with proper resource modeling, HTTP method semantics, status codes, pagination, versioning, and documentation. Use when the user requests api design or provides relevant inputs for this workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

seb1n/awesome-ai-agent-skills2272026년 8월 10일 업데이트

seb1n의 스킬 모두 보기

이 스킬의 문제 신고