Hand your clone a messy contact list. Get it back complete.

Contact lists decay. People change jobs, rows get imported with blank columns, and someone pastes a company name where the domain should be. Filling the gaps by hand takes a person several minutes per row.

The Lead Enrichment Autopilot is for enriching contacts you already have. It is not a lead-generation tool: it won't go looking for new people to add to your list. Clone Lead Generation Skill finds NEW leads and doesn't enrich an existing list (see section 10).

When you hand it a list, your clone:

• reads your Google Sheet or Excel workbook (or a CRM list you export into one) and maps the columns,
• cleans the data (trims, normalizes, dedupes, derives company domains, flags gaps),
• picks the strongest identifier for each row (work email, LinkedIn URL, name + domain, or name + company),
• runs a test batch of 10–25 rows and shows you the results and a credits and time estimate before going further,
• after your "yes", fills the empty fields with web research (firmographics, titles, LinkedIn URLs, plus best-guess emails and phones, always marked UNVERIFIED with a source URL and a confidence score),
• gives every value a confidence score (0–100),
• optionally scores each row against your ideal customer profile (A/B/C tier),
• appends new columns (value, source, confidence, date) and never overwrites your originals,
• sends low-confidence and unmatched rows to a Needs Review tab,
• processes the rest in batches with a progress update after each one,
• optionally writes back to Salesforce or HubSpot (empty fields only) and optionally builds a repeatable pipeline script with Clone Code.

Not included: third-party data providers and email or phone verification. Verified email/phone data needs a paid data provider. If your org adds an operator for one, add it as an extra step. It isn't required for this use case.

Clone Lead Generation Skill finds NEW leads. It doesn't enrich an existing list.

What you get:

• Sales reps and SDRs with a conference list, event export or old account list that's missing domains, titles and contact details.
• Marketing ops cleaning a list before importing it into Salesforce or HubSpot.
• Rev Ops running a periodic data-quality pass on contacts (re-enrich every 90 days).
• Founders and small teams who want a tidier list without a data subscription.

It works with Salesforce or HubSpot (or no CRM at all), and with Google Sheets or Excel. The examples assume a B2B contact list.

 ┌─────────────────────────────────────────────────────────────────────┐
 │  You share {SOURCE_SHEET} (Google Sheet or Excel workbook)          │
 │  and tell the clone which fields to fill: {FIELDS_TO_FILL}          │
 └──────────────────────────────────┬──────────────────────────────────┘
                                    │
                                    ▼
 ┌─────────────────────────────────────────────────────────────────────┐
 │  "Lead Enrichment" skill                                            │
 │                                                                     │
 │  1. Intake           ──►  read the list, map columns (source        │
 │                           untouched)                                │
 │  2. Data hygiene     ──►  normalize, dedupe, validate, derive       │
 │                           domains, flag gaps                        │
 │  3. Match key        ──►  work email > LinkedIn URL >               │
 │                           name + domain > name + company            │
 │        ┌────────────────────────────────────────────────────┐       │
 │        │ TEST BATCH (10–25 rows) + credits and time         │       │
 │        │ estimate ──► you approve ("yes") before full run   │       │
 │        └────────────────────────────────────────────────────┘       │
 │  4. Web research     ──►  cache ► web research (clone), every       │
 │                           value with source URL, UNVERIFIED         │
 │  5. Score            ──►  confidence 0–100 per field                │
 │  6. ICP fit (opt.)   ──►  {ICP_RULES} ──► fit_score + A/B/C tier    │
 │  7. Write to file    ──►  append enr_* columns, never overwrite     │
 │  8. Review           ──►  conf < {CONFIDENCE_THRESHOLD} or no match │
 │                           ──► "Needs Review" tab                    │
 │  9. Delivery         ──►  updated Sheet / .xlsx · optional          │
 │                           Salesforce / HubSpot write-back (empty    │
 │                           fields only) · summary email              │
 │                                                                     │
 │  Runs in batches of {BATCH_SIZE} with a progress update per batch.  │
 │  Stops when {CREDIT_BUDGET} is reached.                             │
 └──────────────────────────────────┬──────────────────────────────────┘
                                    │
 ┌──────────────────────────────────┴──────────────────────────────────┐
 │  ∞ GOVERNANCE (always on): credits cap · {DO_NOT_CONTACT_LIST}      │
 │  honored · GDPR/CCPA · lookup cache · never overwrite ·             │
 │  re-enrich every 90 days                                            │
 └─────────────────────────────────────────────────────────────────────┘

#What web research can and can't do

Verified email/phone data needs a paid data provider. If your org adds an operator for one, add it as an extra step. It isn't required for this use case.

#Output: what gets added to your sheet

Your original columns stay exactly as they were. The clone adds columns to the right:

Plus these tabs: Enriched Leads (the full list with new columns), Needs Review (rows a person should check, with the reason), and Run Summary (counts, fill rates, credits and time used). A Lookup Cache tab stores every result so the same person or domain is never researched twice.

Names below are the exact operator names. Confirm them against your skill catalog (your clone will report what it finds).

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

Clone Lead Generation Skill finds NEW leads. It doesn't enrich an existing list.

Verified email/phone data needs a paid data provider. If your org adds an operator for one, add it as an extra step. It isn't required for this use case.

• Connect your accounts and switch the clone on first. The most common onboarding blocker. If your Google (or Microsoft) account isn't connected, or the clone isn't switched on / active, it can't open the sheet and setup stalls.
• This enriches existing contacts. It does not find new leads. Clone Lead Generation Skill finds new people that match a profile; it does not fill in blanks on your list. If you want new prospects, use it first, then run this use case on its output.
• Web results aren't verified. Pattern-guessed emails (first.last@domain) can bounce. They are always marked UNVERIFIED. Don't load them into a sending tool without verifying them elsewhere.
• Verified email/phone data needs a paid data provider. If your org adds an operator for one, add it as an extra step. It isn't required for this use case.
• Respect do-not-contact and privacy laws. Under GDPR, CCPA/CPRA and similar laws you need a lawful basis (often legitimate interest, documented) to process personal data, should collect only what you need, and must honor opt-outs and deletion requests. Keep {DO_NOT_CONTACT_LIST} current. This is not legal advice; check with your privacy lead.
• Batch large lists. Running thousands of rows at once makes mistakes expensive. Batches of 50 with a progress check are safer.
• Share the sheet with the clone. "Permission denied" almost always means the sheet isn't shared with the clone's account (edit access needed to add tabs).
• Duplicate rows. The same person often appears twice with different spellings. Duplicates are marked Enr Status = duplicate and not researched, but check the hygiene results in the test batch.
• Phone formats. Phones are normalized to E.164 (+ country code + number). Rows with no country can't be normalized reliably; set a default country if your list is single-country.
• Use the cache. The Lookup Cache tab stops repeated research for the same person or domain. Don't delete it between runs.
• Personal emails. A gmail.com or outlook.com address doesn't tell you the company. The clone won't derive a company domain from it.
• Similar names. Web research can match the wrong person with the same name. Name + company matches are the weakest and get low confidence.
• Use exact skill/operator names from your catalog. The clone checks them during discovery.
• Read the skill before you save it. You're responsible for what your clone does.