There is an awkward truth about most management information: once you can see everything, you can act on almost nothing. A dashboard showing every client relationship in a firm, with a score beside each one, is impressive for about ten minutes. Then someone asks what they are supposed to do with it, and the honest answer is often "not much".
Relationship information is no different. Knowing who your organisation knows is genuinely valuable. It answers questions that used to take a round of emails and a fair amount of luck. But a map of relationships doesn't keep a client, win an introduction or protect the firm when someone resigns. People do those things, when they notice something in time and decide to act on it.
So the test of any relationship information isn't how much it shows. It is whether it helps someone make a better call this week.
Most change is noise
Start with an unglamorous fact. At any given moment, most of an organisation's relationships are fine, and most of the movement in them means nothing.
Contact with a client drops over January because half of New Zealand is at the beach. A project finishes and the emails slow down, as they should. A contact goes quiet for a month because they are on parental leave. Any system that treats each of these as an alert will train people to ignore it within a fortnight.
The changes worth attention are the ones that are unusual for that particular relationship. Six weeks of silence from someone you speak to twice a year is normal. Six weeks of silence from a client you normally hear from every few days is not. Judging change against each relationship's own rhythm, rather than against a single rule, is what separates a useful prompt from background noise.
Even then, a prompt is only a question. It says "this looks different". It can't say why.
What actually deserves a response
In practice, acting early tends to pay off in a handful of situations.
The clearest is when something is owed. A client has written twice without a reply, or a meeting happened and nobody followed up. These are the easiest to fix and, from the client's side, the most telling. Few people would describe an unanswered email as a relationship problem. Clients often do.
Drift is harder to spot. A key contact has gone quiet against their usual pattern, or engagement with an important account has been falling for a quarter. Nothing has gone wrong yet, and that is the point. A conversation now is easy. The same conversation after a tender has been announced is not.
Then there is fragility that nobody has noticed, because everything is going well. A major client known by one person in your organisation is a risk whether or not that relationship is strong. It just doesn't feel like one until the resignation letter arrives.
Some changes are positive, and they deserve attention too. Several people at a client suddenly engaging at once might be the start of a new piece of work. It might also be a busy month. Someone close to the relationship can usually tell the difference in a minute.
Who should act is often the real decision
When people talk about acting on relationship information, they tend to imagine the person who noticed the change picking up the phone. Often that is the wrong person.
The better question is who is best placed to respond. That might be the colleague who knows the contact best, the one who was last in touch, or someone senior enough for the conversation to land. Sometimes the answer is that nobody else knows the person at all, which is a finding worth more than the original prompt.
This is where organisation-wide visibility earns its keep. A client services director who sees that a finance lead has gone unusually quiet can also see that two colleagues know her, and that one met her last month. The sensible response is a one-line message to that colleague. It takes a minute to decide and a day to act on, and the client hears from someone they already know.
Proportion matters
Most good responses are small. A reply. A call to check in. Bringing a second colleague to the next meeting. Raising an account at the monthly review. Very few relationships need a plan, and treating every change as a project is a good way to make sure nothing gets done.
Equally, sometimes the right decision is to do nothing. If the partner knows the client is in the middle of a restructure and has asked for space, the silence is expected. Relationship information can't know that. The person who holds the relationship does.
The same logic, different questions
This way of thinking isn't specific to business development, although that is where it is most often discussed.
A leadership team uses it to ask where the organisation is exposed: which important clients rest on one person, and what would walk out of the door if a particular partner left. The decision might be to introduce a second relationship at five key accounts over the next quarter, and check progress at the following review.
Client service teams use it to stop things slipping, from unanswered requests to relationships quietly cooling after a project ends. Risk and succession planning use it to build handovers around the people who already know each client, rather than a list of names. Business development uses it to find out who could make an introduction, and whether that relationship is strong enough to carry the request.
The information underneath is the same in each case. What changes is the question being asked of it.
Identifying an action is not the same as taking one
There is growing interest in software that does more than point things out: tools that draft messages, schedule follow-ups or contact people on someone's behalf. In some areas that makes sense. For client relationships it deserves caution.
A badly timed or clumsy message to an important client can do real damage, and the context that would prevent it rarely lives in a system. It lives with the people involved. For now, the more useful role for software is to make sure the right person notices the right thing, with enough context to decide well. The decision, and the call, should stay with them.
Where Inhere sits
Inhere is built on that view. It builds a picture of an organisation's relationships from everyday email and meetings. Flow lists the replies owed and the relationships that have gone quiet against their usual rhythm, with who else knows each person, and lets people mark items done or come back to them later. Coverage shows where an account rests on one colleague. The Assistant answers questions such as which relationships have gone quiet, and can suggest a sensible next step. Inhere doesn't send messages or act on anyone's behalf.
The point of all of it is the one this article started with. Seeing more is only useful if it helps someone decide what to do, and what to leave alone.
