The case for relationship data in a CRM used to be simple: people don't log their activity, so let's capture it for them. That argument has mostly been overtaken. Most major CRMs can now pull email and meetings in from connected inboxes, and many organisations already do.
So it is worth being precise about what relationship intelligence adds to a CRM today. The answer isn't more activity. It is a different kind of information: a view of relationships across the whole organisation, summarised in a way people can use at a glance.
Activity is not the same as a relationship
An activity log tells you that something happened. Forty emails and three meetings with a client this quarter is a fact. It doesn't tell you whether the relationship is getting stronger or weaker, who in your organisation is closest to the client's chief financial officer, or whether everything is running through a single person.
Those are the things people actually want to know when they open an account record. They are also hard to work out from a list of activities, even a complete one. You would need to read the whole history, across everyone involved, and form a view.
Relationship intelligence does that summarising. It looks at patterns across the organisation's email and calendars, such as how recently and how often people are in touch, whether contact goes both ways and whether they meet, and turns them into a few things a person can read in seconds: how strong a relationship is, which way it is heading, and who holds it.
The people who never open the CRM
There is a second difference, and in many organisations it matters more.
CRM activity capture usually covers the people who use the CRM. In a professional services firm that tends to mean partners, account leads and business development. It often leaves out the senior manager who runs the client work, the specialist who talks to the client's operations team every week, and the colleague in another office who sat on a board with the chief executive.
Relationship intelligence built from connected mailboxes includes those people, whether or not they have a CRM licence. That is often where the surprises are. The strongest relationship with a client regularly turns out to belong to someone who would never think of themselves as the relationship holder, and whose name appears nowhere in the CRM.
What is worth bringing into the CRM
Not everything belongs in the CRM. Account and contact screens are already busy, and the quickest way to make new information ignored is to add too much of it.
A short list tends to be enough:
- Relationship strength. A single indicator, with its direction of travel, tells a reader more than a page of activity.
- Recent activity. How much contact there has been lately, and when the last interaction was.
- The strongest internal contact. Who in the organisation knows this person or account best. This is often the most useful field of all, because it tells people who to talk to first.
Those few fields change how a record is used. An account plan can start from who already knows the client rather than who is listed as owner. A pipeline review can see at a glance whether anyone has spoken to the client recently. A client service lead can spot an important account that has gone quiet. And when someone leaves, the record shows who else has a relationship to build on.
Keep the CRM as the system of record
The cleanest arrangement keeps the two systems doing different jobs. The CRM remains the place for things that need human judgement and process: opportunities, pipeline stages, formal ownership, contracts, notes. Relationship intelligence supplies evidence about contact and relationships, drawn from activity rather than entered by hand.
That division also keeps the data honest. If relationship strength is pushed into the CRM, it should come from one place and flow in one direction. Otherwise it quickly becomes something people edit to match their view of the relationship, and stops being evidence at all.
How Inhere works with Salesforce and HubSpot
Inhere builds its picture from Microsoft 365 or Google Workspace. People and companies are created automatically, and each relationship has a strength indicator drawn from patterns such as recency, frequency, two-way exchange and meetings.
Its CRM sync is optional and one-way. An administrator chooses which Salesforce or HubSpot records to update, and Inhere pushes relationship strength, activity counts, the last interaction and the strongest internal contact. HubSpot syncs can be previewed before they run and limited to relationships above a chosen strength. Nothing flows back from the CRM into Inhere, and Inhere doesn't need a CRM at all: many of its uses, from leadership visibility to succession planning, have nothing to do with pipeline.
The scores are indicators drawn from communication patterns. They don't replace the judgement of the person who knows the client. What they do is give everyone looking at the record, including people who have never met the client, a better starting point. More detail is on our CRM page and integrations page.
