Client Relationships Held by One Person

A client who deals with one person is a client who belongs to that person. In a small organisation this is usually most of the revenue.

The principles in “Client Relationships Held by One Person” become easier to maintain when ownership and time spent are visible. Teams evaluating time management software can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with ICO employment data guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

What it looks like

The client rings a mobile, not the office.

Nobody else has met them.

Nobody else knows what was agreed beyond the contract.

And if asked, the client would describe the relationship as being with the individual rather than with the company.

Why it matters more than other dependencies

A process can be documented. A relationship cannot.

And unlike other knowledge, this one can walk to a competitor: if the person leaves, the client may follow, and in some sectors that is the normal expectation.

Which makes it the dependency with both the highest cost and the slowest remedy.

The slow mechanism

A second person involved over months, not introduced at handover.

Copied on correspondence. Present at meetings, saying something. Handling one workstream.

After a year the client knows two people at your organisation, which is the whole objective.

There is no fast version of this.

Raising it with the person

Frequently uncomfortable: it can be heard as distrust, or as preparation for removing them from the account.

The framing that works is coverage rather than replacement: what happens when you are on holiday or ill, and the client needs something.

Most people recognise that problem immediately, because they have experienced it.

Where resistance is real

Some people hold relationships deliberately, as security.

Its own note covers the expert who resists, and the short version is that the reason is usually economic and addressing it directly works better than pressure.

And in commission-based arrangements the incentives may actively oppose sharing, which is a structural problem rather than an attitude one.

What to write down even so

Who at the client decides, who influences, who is difficult.

What was agreed verbally that is not in the contract.

History: what went wrong, what they are sensitive about, what they have been promised.

This does not replace the relationship and it substantially shortens the recovery if the relationship is lost.

The client's view

Clients generally prefer knowing two people at a supplier, because their own continuity depends on yours.

Which means introducing a second person can be presented to the client as a benefit rather than explained apologetically.

Several will say they had wondered what happens if your person is unavailable.

What to check

How many clients have met only one person at your organisation?

What proportion of revenue does that cover?

Is anything about those relationships written down?

And has a second person been introduced anywhere, or is it still planned?

The point

A client who deals with one person is a client who belongs to that person.

There is no fast version of transferring that; a second person involved over months is the only mechanism.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.