Every relationship mapping tool demos the same way. A graph of colourful nodes with an executive at the centre. Pulses of activity flowing between contacts. A partner smiling as they "discover a warm path." You buy it. You roll it out. Six months later, nobody opens it.
The difference between tools that stick and tools that don't isn't the graph. It's five much less exciting things. Use this checklist when you evaluate — and honestly, run it past two partners at your firm before you sit through the demo.
1. Where does the signal come from?
The only signal that reliably matters is your team's real communications: mailbox, calendar, meeting transcripts. If the demo relies on manually entered "known relationships," or on scraped LinkedIn connections, the graph will be stale within a quarter. Insist on a live Microsoft 365 or Google Workspace ingestion path with delta sync.
2. Can it survive job changes?
People move. Your champion at Client A becomes the buyer at Client B. A good tool follows the person, not the email address — the relationship history from the old employer should be visible on the new record, with proper provenance. Watch the demo carefully. Most tools quietly drop the history and hope you won't notice.
3. Does it score, or just visualise?
A graph tells you what exists. A score tells you what matters. Any serious tool ranks relationships by strength (with a decay curve) and rolls per-contact scores up into a per-account health score. Without a score, users have to interpret the graph themselves. They won't.
4. Does it surface next actions in your workflow?
Ask the vendor to show you exactly where the tool appears when a partner opens their calendar on a Monday morning. If the answer is "they log into our dashboard," you have a problem. The tools that work push the intelligence into the account page, the deal record, the pre-meeting briefing email and the pipeline review — the places partners already look.
5. What's the privacy posture?
Reading every partner's mailbox is a big commitment, and it should feel like one. Look for read-only OAuth scopes, tenant-scoped access, per-user opt-out of specific domains or contacts, no long-term storage of full message bodies unless required, and clear regional data residency. Your privacy officer will ask. It should not be the vendor's first time answering.
What to ignore
- Third-party "warm intro" databases. Interesting for cold outbound, barely relevant for BD inside your existing accounts.
- AI-generated bios and personality profiles. Fun on a demo, dangerous in a partner meeting.
- Fancy graph physics. A ranked list of the ten most-at-risk accounts is worth ten force-directed layouts.
The two-question test
Before you sign anything, put these two questions to a partner in your firm:
- "When you open this tool on a Tuesday morning, what does it tell you to do?"
- "If you don't open it for two weeks, what breaks?"
If the answers aren't specific and slightly painful, you're buying a screensaver. If they are, you have a tool that will pay for itself inside a year.