Relationship intelligence reads the metadata - sender, recipient, timestamp, attendee list - and builds a graph of who knows whom and how well. The question it answers is "who at my company can reach this buyer". Orbb, Introhive and Connect the Dots.
Revenue intelligence reads conversations and deal activity to judge whether a deal is healthy. Gong, Clari and Chorus. The question is "will this close", and the answer comes from call recordings and engagement patterns inside open opportunities.
Activity capture reads email and calendar to stop reps doing data entry. Nektar, Scratchpad, Dooly. The question is "what happened, and is it in the CRM".
Scheduling and meeting tools read calendars to find free time. Chili Piper, Calendly. A different job entirely.
The overlap is the data source, not the purpose. A team that buys revenue intelligence expecting warm paths will not get them, because Gong sees your reps talking to contacts they already found.
Revenue intelligence and activity capture are both inward-looking: they describe the deals you already have. Relationship intelligence is outward-looking: it finds the accounts you cannot get into and tells you who can open them.
That is why the two sit together rather than competing. Cresta used relationship mapping to find a route into a top enterprise target and closed $160,000 in 90 days; a revenue intelligence tool would have had nothing to say about that account until a conversation already existed.
Worth asking every vendor, because the answers differ more than the category pages suggest:
| Metadata only | Message bodies | Call recordings | |
|---|---|---|---|
| Relationship intelligence | Usually | Rarely, and should not need to | No |
| Revenue intelligence | Yes | Yes | Yes |
| Activity capture | Yes | Often | No |
Metadata - who, when, replied or not - carries nearly all the relationship signal and almost none of the privacy risk. A vendor that needs message bodies to tell you who knows whom is doing something harder than the job requires.
Email and calendar are sensitive, and the failure mode is organisational rather than technical. Tell the employees whose mailboxes are being read before you switch it on, write the legitimate interests assessment, and agree where the data lives. The detail is in our answer on compliance.