Every RevOps leader I've talked to has a version of this problem. They know their CRM lies about revenue. They know it lies about pipeline stages. They know the hygiene is a running joke — half the accounts have stale owners, a third of the opportunities have wrong close dates, and the forecast is a monthly exercise in spreadsheet reconciliation.
What most of them don't realize is that the CRM is also lying about who they know.
Between 60% and 80% of the relationship signal inside a company never makes it into the CRM. Not because reps are lazy. Not because the data model is bad. Because the CRM was never designed to hold it. Emails from three years ago, calendar meetings from a rep's previous employer, LinkedIn touches that never turned into a logged activity, alumni networks, portfolio overlaps — the CRM has no field for any of it. And when your team runs "who do we know at Snowflake?" the answer is drawn from the 20% that made it in.
This is the CRM warm-path data gap. This piece is how to diagnose it, what fills it, and what a 10-question audit looks like for a RevOps leader who wants to stop pretending the map is the territory.
The framing debt
Common Room built a good business around a simple sentence: "the CRM is lying to you." Their version was about signals — product usage, community engagement, buyer intent. Everything the CRM couldn't see because it was designed for a sales-led motion in a product-led world.
That framing is correct. It's also incomplete.
The CRM is also lying about relationships. Every mid-sized B2B sales team is sitting on tens of thousands of relationship records — email threads, calendar invites, LinkedIn connections, prior-company overlaps — that never get structured. When a rep asks the CRM "who do we know at ThoughtSpot," the CRM answers with whatever three contacts happen to have logged a call or a meeting inside the CRM's activity feed. Everything else is invisible.
The consequence is that most warm-intro programs are running on the 20% of the graph the CRM happens to have caught. The other 80% sits in Gmail, Outlook, Google Calendar, LinkedIn, and the personal address books of individual reps. It doesn't exist to the system.
Where CRM relationship data actually comes from
If you audit a typical enterprise CRM, the relationship data is coming from five places:
- Manual rep entry. Reps typing contact names into new opportunities. This captures maybe 30% of who a rep has actually interacted with in a given account.
- Email logging (partial). Some Gmail plugin or Outlook integration is logging some emails, from some reps, some of the time. Coverage varies by team and by rep. Reps who don't want their pipeline visible turn logging off.
- Calendar sync (partial). A subset of meetings from a subset of reps. Historical meetings from before the rep joined the company are not represented at all.
- Form fills. Marketing-sourced leads. This tells you who filled out a demo request, not who a rep already knew inside that account.
- Marketing automation. Email opens, page views, gated-content downloads. Useful for intent. Useless for warm paths.
Notice what's missing. LinkedIn connections. Past-company overlaps. Alumni networks. Investor portfolios. Champion job changes. Partner-side conversations. Every relationship signal that lives outside the CRM's four walls.
Where CRM data should come from
The full relationship dataset for a modern B2B sales team looks nothing like the CRM export. It includes:
- Emails. All reps. All threads. All directions. Including emails from before the rep joined the company, if the rep has forwarded or preserved them.
- Calendars. All meetings, including past meetings from prior employers. That 8am coffee a rep had in 2021 with a VP who is now at a target account is warm-path data.
- LinkedIn. First-degree connections, plus interactions — comments, likes, shared connections. Second-degree paths through employees, customers, and investors.
- Past-company overlaps. Employee alumni networks. Every current employee who used to work at Datadog, Snowflake, Databricks, or wherever your target account list points. This is the graph most teams undercount by 90%.
- Investor and advisor graph. Whoever your investors and advisors have introduced you to before, plus everyone in their broader portfolios. Portfolio CEOs know portfolio CEOs.
- Customer champion graph. Every customer champion's LinkedIn network, prior colleagues, and adjacent-company relationships. Your customers know your prospects — 95% of your target buyers know at least one of your customer champions.
Each of these lives in a different system. None of them show up in the CRM by default. And the aggregate is the actual four-pillar network your team can pull from.
What gets missed, in concrete terms
The gap is easiest to see with examples. Some of these will look familiar.
- A rep has a 1st-degree LinkedIn connection who is now VP of Data at a target account. They connected four years ago at a conference. Never logged. CRM sees nothing.
- A director on your customer success team used to work at your prospect's company. Six years ago, three roles ago. She still has the Slack contacts, the alumni email chain, the old peer group. CRM has no field for prior-company overlap.
- Your CEO had a 1:1 with the prospect's CFO in 2022, when both were at different companies. The meeting is in a Google Calendar backup somewhere. The CRM has no idea it happened.
- A rep's college roommate is now a founding engineer at a strategic prospect. They still text. There is no CRM field called "college roommate."
- An investor introduced your CEO to a portfolio-company COO 18 months ago. The intro landed, the meeting happened, no deal came of it. The COO has since moved to a top-10 target account. That relationship is dormant and invisible.
- A partner-side account manager has been talking to the same buyer for a year. Their CRM has it. Yours doesn't. And no one has asked.
Every one of these is a live warm path. None of them are in the CRM. And in aggregate, they represent more relationship equity than the entire logged-activity feed.
The Gartner context
The buying committee has expanded to 6-10 people, and often up to 11 (Gartner). Traditional data vendors — the ones your CRM enrichment budget goes to — miss up to 30% of that committee because they refresh on a batch cadence and buying committees change monthly.
So the compounding failure is:
- The CRM has 20% of the relationship signal your team has actually generated.
- Enrichment vendors filling in the buying committee miss 30% of it.
- Your reps are asked to multithread across a committee they can't fully see, using a relationship graph that's 80% invisible.
The math means the average rep is trying to multithread a 10-person committee with visibility into maybe two contacts and warm paths to zero. Then leadership wonders why cold outbound response rates keep collapsing.
The 10-question RevOps audit
Every RevOps team should run this audit at least once a quarter. Answer each question honestly. If you get to seven "no" answers or more, your warm-path data gap is closer to 80% than 60%.
- Do you have all rep email and calendar synced — both historical and ongoing? Ongoing sync is common. Historical sync is rare. Most teams only capture activity from the date the rep set up the plugin.
- Is LinkedIn 1st-degree connection data captured for every employee? Not "LinkedIn Sales Navigator is provisioned." Actual capture of who each employee is connected to, refreshed weekly.
- Do you have alumni-network overlaps computed? For every target account, do you know which of your current employees previously worked at that account?
- Do you track past-company overlaps between employees and prospects on a rolling basis? People move. The overlap you had six months ago has shifted.
- Are investors' portfolio graphs mapped? Do you know which of your investors' portfolio companies overlap with your target account list?
- Are partner accounts and their contact graphs in the CRM? Not "we have a partners tab." Actual contact-level graph of who your partners are working with.
- Are champion job changes tracked systematically? When a champion leaves for a new company, does that generate a signal — an account to prioritize, a relationship to warm?
- Do you have a champion-to-buying-committee map for each target account? For your top 100 targets, do you know which of your existing champions have relationships with someone on the current buying committee?
- Is your data refresh cycle continuous or batch? Batch refresh — quarterly, semi-annually — is where the 30% miss on the buying committee comes from. Traditional vendors are batch. The market moved faster than that in 2022 and never went back.
- Can any rep pull a "who do we know at [account]" report in under 60 seconds? Not "can our RevOps analyst pull it by end of day." Any rep. Under a minute. From their laptop. If not, the graph doesn't exist operationally, even if it exists in theory.
Most teams score 3-4 out of 10. The ones scoring 7 or more have usually already invested in a relationship intelligence layer that sits on top of the CRM.
What to do about it
The answer is not "buy Boomerang." The answer is: instrument the graph first.
- Fix email and calendar sync. Both directions, historical and ongoing, every rep. Gong and Salesloft cover parts of this. Neither is complete. If your logging depends on individual reps remembering to click a plugin, you're already losing.
- Add relationship-graph enrichment. This is the layer that sits between the CRM and the underlying systems — email, calendar, LinkedIn, prior-employer records — and builds a queryable graph. Traditional enrichment vendors add contact records. Relationship-graph enrichment adds paths.
- Instrument the four pillars separately. Employees, customers, partners, investors. Each has different volume, cadence, and incentive structure. Treating them as one graph is the mistake most teams make.
- Run a quarterly warm-path audit. Same 10 questions. Track the score. If it isn't going up, you're accumulating debt.
- Turn on the multi-hop pathfinding layer. First-degree paths are easy. Second-degree paths — where your rep knows someone who knows the buyer — are where the volume actually lives. And they only surface if you're computing them.
None of this is glamorous work. It's the same category of hygiene as fixing your revenue recognition or your account ownership rules. It compounds silently for two quarters and then shows up as a step-change in pipeline coverage.
Frequently asked questions
How do I know if my CRM warm-path gap is closer to 60% or 80%? Run the 10-question audit above. Fewer than four "yes" answers and you're at 80% or worse. Seven or more and you're closer to 60%. The gap narrows as you instrument more of the underlying systems — email, calendar, LinkedIn, alumni overlap — into a single graph.
Isn't this what Sales Navigator does? No. Sales Navigator is a database of people and companies. It surfaces search results and saved lists. It doesn't compute warm paths across your team's aggregate graph, it doesn't sync back to your CRM at the account level, and it doesn't tell a specific rep who on their team is best positioned to make an intro to a specific buyer. Different job.
Does Gong or Salesloft solve this? Partially. Both capture more email and calendar activity than a bare CRM. Neither builds a relationship graph across the four pillars — employees, customers, partners, investors — and neither surfaces multi-hop paths. They close some of the logging gap. They don't close the graph gap.
Why can't we just export from LinkedIn? LinkedIn's terms of service block bulk export of connection data, and even if they didn't, a flat list of connections isn't a graph. You need connection strength signals — mutual interaction frequency, recency, meeting overlap — and those live outside LinkedIn. The value is in the join, not the export.
How long does it take to close the gap? Getting from a score of 3 to a score of 7 is a one-quarter project if the CRM data model is stable and the executive team is bought in. Getting to 9 or 10 requires a relationship intelligence platform sitting on top of the CRM, and it usually takes another quarter to see the operational impact in win rates and pipeline coverage.
What's the single highest-leverage fix? Historical email and calendar sync for every rep, including data from prior employers where the rep still has access. That single change typically moves the audit score by 2 points and surfaces warm paths teams didn't know they had. Everything else builds on top of that foundation.
