Data enrichment is adding verified fields to a record you already have so you can reach the person. In B2B sales that usually means email and mobile on a Contact, sometimes company details, written into the CRM you already report in.
It is not "buy a million rows." It is not scraping LinkedIn in the background. In SurroundR it is the same click that captures a LinkedIn profile into HubSpot: a waterfall of 20+ premium data vendors runs, the first verified email and mobile win, and standard Contact properties update in about two seconds.
What enrichment is (and is not)
Is: you have a human in mind (a LinkedIn profile, an inbound name, a Navigator lead). You need a way to email or call them. A provider (or a chain of providers) returns verified fields. Those fields land on the CRM record.
Is not: building the target list from a database. That is list building or data buying. Cognism is a B2B contact-data platform for that job. Kaspr is a reveal-and-export tool. SurroundR assumes you already found the person on LinkedIn.
Is not: HubSpot form field defaults, or ads Lead Gen Forms. Different pipes.
Is not: an enrichment waterfall. The waterfall is how you try more than one provider. Enrichment is the job those providers are hired for. See what is an enrichment waterfall when the question is sequencing, not definition.
Verified, in this glossary, means the provider returned a field it treats as a hit, and SurroundR writes it to HubSpot. It does not mean the person will answer. Bounce rates still belong in your HubSpot reports. Do not treat "enriched" as "guaranteed inbox."
The enrichment waterfall product page owns credits, tiers, and how SurroundR runs the chain. This glossary owns the definition. When you need mechanics, leave this page.
Contact enrichment versus company enrichment
Most seller pain is contact-level: no email, no mobile. Company enrichment (industry, size, domain) is useful when the Company object is empty, but it does not let you send the first message. SurroundR's capture-time job is the person in front of you. Firmographic fields can come along. The reason to install is still reachability on the Contact.
If HubSpot already has a Company and you capture a person at that company, match keys should keep you on one Company plus one Contact, not a second company named the same thing. Dedup detail belongs on the HubSpot integration page. The hygiene operating list is CRM data hygiene for RevOps.
Where the data should live
If HubSpot is the system of record, enrichment that stays in a vendor UI is not enrichment. It is a second spreadsheet. SurroundR writes to standard HubSpot Contact properties and matches on email, phone, or LinkedIn URL so you update rather than duplicate.
The HubSpot integration page is the writeback evaluation: OAuth, objects, every HubSpot tier. Use it when security asks where fields go.
HubSpot also ships native enrichment on some plans. Those features are HubSpot's. SurroundR does not replace them and does not wait for them. It enriches when you capture from LinkedIn. If a record already has a good email from a form, capture should match and fill the gaps, not invent a twin.
How SurroundR does enrichment
Capture the LinkedIn profile. Enrichment runs on save. Providers rotate until a verified email and mobile resolve, then SurroundR writes the contact to HubSpot, deduped. Free is 100 credits per month with no card.
The integrations hub explains HubSpot as destination plus the waterfall without turning this glossary into a second integrations page. At the overlap: enrichment in SurroundR is capture-time, vendor-agnostic in public copy ("20+ premium data vendors"), not a named-supplier pitch.
A waterfall is the sequencing pattern. Clay lets you design waterfalls in an orchestration sheet. SurroundR runs one in the feed. Clay vs SurroundR is the compare if that is the buying question.
Batch enrichment of a CSV you never look at is a different motion. SurroundR enriches the profile you capture. If the team works a list, they still capture (or they import, which is the hygiene risk in the RevOps checklist). Inbound is the same click after the lead already exists: inbound lead enrichment in HubSpot.
When enrichment fails hygiene
- Fields never reach HubSpot
- Credits buy data you look at once in another tab
- Duplicates because LinkedIn URL was not a match key
- Inbound leads that nobody captures, so nothing enriches
- A nightly fantasy that every stale record rewrites itself (SurroundR does not claim that; see data decay)
Credits, pay-on-miss, managed versus bring-your-own keys, and the Free tier live on the product page. This glossary will not impersonate a billing contract. If you need the number of credits on Mono or Stereo, open pricing.
When you should not enrich
Skip enrichment when you already have a working email and mobile on standard properties and you are only updating a title. Capture can still refresh the LinkedIn URL and the job title. Spending a credit to re-find an inbox you already use is a waste unless the old email bounced.
Skip it when no human will open LinkedIn. Batch jobs over people nobody will work are how credits disappear and HubSpot still looks stale next quarter. SurroundR is capture-time. The people you capture are the people you intend to reach.
Skip it when the destination is not HubSpot. If the team wants a reveal in a sidebar and an export on Friday, that is a reveal tool, not this glossary. SurroundR assumes HubSpot is where the field must live.
Short version
Data enrichment completes a contact you already chose. In SurroundR that happens on LinkedIn capture, into HubSpot, through a waterfall you can inspect on the product and integrations pages. Install if you want that click. Do not install if you wanted a database of people you have never seen.
