Relationship intelligence

    Who knows whom? Why organisations still struggle to answer a simple question

    Most organisations can't say quickly who knows whom at a client or prospect. The knowledge exists, but it sits in individual inboxes and memories rather than anywhere the organisation can see it.

    Inhere · 7 November 2026 · 4 min read

    Here is a situation most people in professional services will recognise, simplified a little. A partner is preparing a pitch to a regional council and wants to know whether anyone in the firm knows the council's new chief financial officer. She emails the partnership. Over the next day she gets three replies: one "not me", one suggestion that turns out to be wrong, and one that arrives after the pitch.

    Two weeks later, a senior associate mentions that he has been dealing with that CFO for years. They worked together on a previous client's audit and still meet for lunch a few times a year. Nobody asked him. He wasn't on the partners' email.

    The question was simple, and the answer existed. The firm just couldn't find it when it mattered.

    The knowledge is there, but it is private

    Every organisation holds a remarkable amount of relationship knowledge. It lives in years of email threads, meeting invitations, introductions and shared projects. Between them, your people probably know someone at most of the organisations you care about.

    The difficulty is where that knowledge sits: in individual inboxes and people's heads. It belongs to each person rather than to the organisation. Nobody else can see it or search it, so the organisation falls back on asking around, sending the all-staff email or relying on whoever is in the room. Those methods work occasionally. They are slow, they depend on memory and they favour the loudest or most senior voices.

    Why the usual fixes fall short

    Most leaders have tried to solve this already, and the usual fixes run into the same wall.

    Asking people to record their relationships, in a CRM or a spreadsheet, produces patchy data that decays quickly. Busy people record what they must, usually the formal client contact, and little else. The associate in the example would never have logged his lunches with the CFO. He wouldn't have thought of them as work, yet that was the most useful relationship the firm had for that pitch.

    Relying on senior people to know the landscape works for their own clients and not much further. Partners rarely know who a project manager, a specialist or a colleague in another office is in regular contact with. And many of the most active relationships with a client sit a level or two below the formal relationship lead, with the people answering emails and fixing problems.

    Asking around is the method most organisations actually use, and it is the most expensive. Each "does anyone know…?" interrupts dozens of people and depends on the right one reading it and remembering accurately. A firm might ask some version of the question several times a week. Each instance is small. Together they add up to a lot of lost time and a lot of missed connections.

    It is several questions, not one

    "Who knows whom" sounds like a single question, but organisations usually mean one of several.

    • Who do we know at this organisation? Useful before a pitch, a meeting or a negotiation.
    • Who knows this particular person, and how well? Useful when you need an introduction or some context.
    • How many of us know how many of them? Useful for judging whether an important relationship is broad or rests on one person.
    • Is the relationship getting stronger or weaker? Useful for client service, and for spotting accounts that need attention.

    The word "know" does a lot of work, too. Exchanging one email two years ago isn't the same as meeting someone every month. A useful answer has to say something about strength and recency, not just whether a connection exists.

    What not knowing costs

    The costs are real but rarely visible, because they show up as things that didn't happen. A cold approach where a warm introduction was available. A pitch team walking in without knowing a colleague has worked closely with the client's general counsel. Two teams contacting the same person in the same week with different messages.

    The quieter cost is in decisions. Leaders judge which clients are secure without knowing how many people actually hold those relationships, and find out when someone leaves. We look at that in what happens to client relationships when someone leaves.

    Making it visible

    The practical answer is to stop relying on people to declare their relationships, and to see them in the activity that already exists. Email and calendars already show who is in contact with whom, how often and how recently. Nobody has to fill in a form for that record to exist.

    That is the idea behind relationship intelligence. It has to do a few things well to be worth having. It should cover everyone, not just the diligent. It should stay current, because relationships change. It should distinguish a close working relationship from a passing contact. And it should respect privacy: showing that a relationship exists and how active it is, without exposing anyone's inbox. People are rightly wary of anything that looks like monitoring, and the aim is to show the organisation what it collectively knows, not to read colleagues' email.

    Inhere works this way. It builds the picture from Microsoft 365 or Google Workspace, shows on each company page who across the organisation is in touch with whom, and lets people ask the Assistant who could introduce them to someone. In the example above, the partner would have found the associate in a minute, on the first morning rather than two weeks too late.

    Knowing who knows whom isn't an advanced capability. It is basic organisational knowledge that has simply been hard to reach.

    What could your organisation’s relationships be telling you?

    We’ll show you Inhere with the questions your organisation is trying to answer.

    Book a demo