Data decay is contact and company fields going stale after you save them. The email bounces. The title is last year's. The mobile is blank. The person exists twice. The conversation that moved the deal never hit HubSpot.
It costs pipeline because sellers work ghosts: sequences to dead inboxes, calls to numbers that are not theirs, forecasts on records that do not reflect the thread. RevOps feels it as merge queues and reports nobody believes.
This site will not invent a universal decay percentage. Put your HubSpot bounce rate, duplicate count, and "missing email" list size in the review. Those are your numbers.
A cost framework you can actually fill in
Do not start with a made-up annual rate. Start with four buckets you can count in HubSpot this week:
- Unreachable. Contacts you would sequence that have no email, or email that last bounced. Count them. Each one is a stalled follow-up.
- Duplicates. Same LinkedIn human, two Contacts. Count merge queue or a LinkedIn URL collision list.
- Off-CRM conversations. Deals where the real thread is LinkedIn DMs. You cannot count them perfectly. You can ask AEs. Logging is part of decay: the record is incomplete even if the email is valid.
- Time tax. Manual recapture. The homepage cost-of-inaction module assumes about 45 seconds of typing per contact over working days, labeled as an estimate, not a claim about your team. If your team still pastes, use that as a time bucket, not as SurroundR's revenue promise.
Money sits in pricing: Free is 100 credits per month with no card. Mono and Stereo add paid credit pools. Credits refresh data when you capture, they do not silently rewrite the portal overnight. Use pricing to size a pilot, not to fake an ROI percentage. We do not invent savings for your invoices.
Title decay, email decay, and mobile decay are not the same clock. Titles often move first on LinkedIn. Email decays when someone leaves and the inbox is closed. Mobile decays when the number was never verified, or the person changed it. Treat them as separate HubSpot lists if you can. A single "data quality" slide hides which bucket you can actually fix this month.
Why LinkedIn-sourced records decay fast
People change jobs. LinkedIn is often the first place a title updates. HubSpot is not. If the original capture was a CSV with no LinkedIn URL, you cannot match the human when they reappear in the feed. If enrichment never ran, you have a name. If DMs never synced, you have a Contact without the deal.
Slowing decay is operational, not magical:
- Capture from the profile you are on (fresh title, LinkedIn URL as a key)
- Enrich on that save (email and mobile on standard properties)
- Match on email, phone, or LinkedIn URL
- Recapture when you work them again instead of trusting last quarter's file
- Optional auto-sync so the thread does not decay off-CRM
The operating checklist is CRM data hygiene for RevOps. The stack story is the RevOps solution page. This post is the decay definition and the cost buckets. Link those pages instead of repeating OAuth and scope tables.
Recapture is not "SurroundR scanned the portal at 2am." It is a seller on the profile again, same click, updated fields if the waterfall hits. That is slower than a fantasy batch job and more honest about who still matters in the pipeline. If you need a designed ops waterfall over a sheet of old inbound, that is a different product job. SurroundR's job is the people you are actually looking at.
Pipeline stages where decay shows up
Early stage: sequences to bounced email, SDR time on records that were never reachable. Mid stage: the AE inherits a Contact whose title is wrong, so the buying map is wrong. Late stage: the thread that moved legal lived in LinkedIn and never hit the timeline, so forecast notes are fiction.
Inbound does not get a pass. A form fill from last quarter with no LinkedIn URL and no recapture is decay with a marketing source stamp. When follow-up returns to LinkedIn, capture again: inbound lead enrichment in HubSpot. The enrichment page is how that save fills fields. This page is why you bother.
What will not fix decay
- Buying another database and never writing it to HubSpot
- A bigger CSV of the same people without unique keys
- A meeting about "data quality" with no capture path
- Overnight enrichment of every record (SurroundR does not claim that)
- Quoting a blog percentage in a board slide instead of your HubSpot counts
How to run the four-bucket review in one meeting
Forty minutes, HubSpot open, no vendor slide deck:
- Pull unreachable: missing email, or last email bounce, on Contacts you still consider in play.
- Pull duplicates: merge queue, or Contacts sharing a LinkedIn URL.
- Ask two AEs which live deals have a LinkedIn thread that is not on the timeline. Write the number down. That is off-CRM decay.
- Watch one capture. If it takes a paste and a prayer, use the homepage 45-second estimate as a time bucket, labeled as an estimate.
Then decide whether capture-time enrichment and optional DM sync are the fix, or whether the real hole is that nobody opens HubSpot. SurroundR cannot repair a CRM the team has abandoned. It can stop new LinkedIn work from rotting in a tab.
SurroundR slows decay at the moment of LinkedIn capture. Start free, run a pod against the four buckets, then look at pricing if credits run out. That is the honest cost conversation: count your stale records, count your time, then decide. Do not paste a fake annual decay rate into a board slide from this URL.
