Walking in cold: what it costs when nobody knows who already knows the client

Here is a scene that happens in every firm, several times a week, and is never recorded as a loss anywhere.

A partner has a meeting with a client-side director. The account is ten years old. The partner has been at the firm for three. They have never met this person.

They do what a diligent person does. They open the CRM. They find a contact record: name, title, office location, an email address, a note from 2021 that reads "attended kick-off". They look the director up on LinkedIn, which tells them where the director worked before. They ask the two colleagues nearest to them, who do not know.

Then they walk in cold.

What is actually available, and unreachable

Elsewhere in the firm, at that same moment, the following facts exist:

• A senior manager ran a programme for this director in 2022 and knows they will not sign anything without their finance lead in the room.
• A former colleague, now three years gone, had a difficult procurement with them and left a long email thread explaining why the relationship recovered.
• A partner in another office pitched them last year and lost, and knows exactly which competitor won and on what basis.
• The firm delivered a report in 2023 that this director personally commissioned and cites in their own board papers.

None of it is secret. None of it is even hard to obtain, if you know to ask the right four people. It is simply unreachable in the twenty minutes a partner has to prepare, because the route to it runs through human memory and nobody knows to activate it.

The firm has a ten-year relationship with this person. The partner in the room has a name and a job title.

Why the CRM does not hold this

This is not a failure of CRM discipline, and firms that respond to it with an adoption campaign are treating a symptom.

A CRM is built to record a pipeline: opportunities, stages, values, next actions. Contacts exist in it as attributes of deals. That is the correct design for a transactional sales motion, where the relationship is short and the deal is the unit.

Professional services inverts this. The relationship is the durable thing, lasting decades and spanning dozens of engagements, and the deals are episodes within it. A structure that treats contacts as deal attributes cannot represent a relationship that outlives every deal in it.

Then there is the data entry problem, which is fatal on its own. Asking a partner to record what they learned in a meeting is asking them to convert billable time into administrative time. Firms know how this ends: low adoption, inconsistent entry, and a database where the best relationships are the least documented, because the people with the best relationships are the busiest.

What a usable stakeholder history contains

Preparing for that meeting properly requires four things, in rough order of value.

Who in the firm has engaged this person, and on what. Not who has emailed them. Who has actually delivered work they were involved in. The distinction matters: an associate who copied them on forty status reports has a weaker claim than a manager who sat opposite them in eight steering meetings.

What the firm has delivered that they touched. Named engagements, with dates, and the documents. This is what lets a partner open with something specific rather than something generic.

What is known about how they operate. Their stated priorities, their constraints, the way they make decisions. This is the softest material and the most valuable, and almost all of it lives in email rather than in any deliverable.

Where the relationship has been difficult. The lost pitch, the escalation, the procurement that went badly. A history that only records successes will get a partner into trouble, because the client remembers the rest.

Every one of these has the same shape: a link between a person and an event, with a document behind it. That is why a contact record cannot carry it. A contact record has no place to put the evidence.

The compounding version of the problem

There is a version of this that costs considerably more than one awkward meeting.

Relationships in firms are held personally. That is deliberate and largely good: clients want a person, not an institution. The consequence is that when the person leaves, the client does not experience a personnel change, they experience amnesia. The successor arrives, asks questions the client answered three years ago, and the client draws the obvious conclusion about how much the firm was paying attention.

With average knowledge-worker tenure around four years, this is not an occasional event. On a ten year account it is a recurring one, and every occurrence resets the relationship a little further back than the last.

Every handover is a chance for the client to notice that the firm's memory is shorter than theirs.

What has to be true of a fix

Three conditions, and they rule out most of what is on the market.

It must record delivery, not just contact. Interaction frequency tells you who is in touch. It does not tell you what the firm did for that person, which is the thing a partner actually needs to open a meeting with.

It must build itself from what already exists. The material is in proposals, reports and the threads where the work was negotiated. If capturing it requires anyone to fill in a form, the best relationships will be the emptiest records, exactly as they are today.

It must be checkable. A briefing note that asserts a director "values delivery certainty" is worth nothing to the partner reading it, who has no idea whether that is an observation from a real meeting or a guess. The same claim with the thread behind it is worth acting on.

In OrgAtlas, stakeholder history is assembled from material the account team sends deliberately: threads forwarded in, outgoing mail blind copied to the account address, and documents dropped in the browser. Each client-side individual carries their history with the firm, and every line of it names the document it came from. Nobody fills anything in, and nothing is asserted without something behind it.

That is the whole ambition here. Not to make the partner an expert on the director. Just to make sure they walk in knowing what their own firm already knows.

Next: relationship intelligence as a category, what it does well, and the half of the map it leaves out