Three teams, one stakeholder

Sales owns the opportunity. Marketing owns the audience. Communications owns the
public position. Each team is competent, each has a system that suits its work, and
each holds roughly a third of the same relationship.

The person on the other side does not experience three teams. They experience one
organization that appears not to talk to itself.

How it shows up

It is rarely dramatic. It is a second approach a fortnight after the first, from
someone who did not know the first had happened. It is a campaign that lands the
week a delicate negotiation reaches its final stage. It is a public position that
contradicts a commitment made verbally in a meeting nobody logged. It is a renewal
call that opens by asking something the account has already answered twice.

Any one of these is forgivable. The pattern is what costs you — because the pattern
reads as an organization that does not have its own house in order, which is a
difficult impression to argue your way out of.

Why the usual fixes don’t hold

The standard response is process: a shared calendar, a weekly sync, a rule that
campaigns get checked against the pipeline. These work for a while and then decay,
for a predictable reason — they are a manual reconciliation layer over three systems
that still disagree. The moment the meeting is skipped, the disagreement returns.

The second standard response is consolidation: put everyone in the CRM. This fails
differently. A CRM is built around the deal, and a deal is a poor container for a
relationship that outlives it. Communications has no deal. Neither does the
regulator who will decide whether the programme is viable.

Make the stakeholder the object

The structural fix is to stop treating the deal, the campaign and the position as
the primary records, and to make the stakeholder itself the thing every team writes
to. Then each function keeps its own view, but all three views resolve to one entity
with one history.

What that requires in practice is unglamorous: named ownership on the entity —
who holds the commercial relationship, who holds delivery, who holds the technical
conversation — plus the partners in the same frame, because your message reaches
them too.

The gap is the useful part

The first thing most teams find when they put coverage on one surface is not
duplication. It is absence: accounts with no named relationship owner, partners
nobody has spoken to since the contract was signed, whole territories where the
organization is present commercially and absent relationally.

That is worth more than the deduplication. Two teams calling the same person is
embarrassing. Nobody calling them at all is expensive.

What good looks like

Marketing can see which accounts are mid-negotiation before a send. Communications
can see which relationships a position will land on. Sales inherits context at
handover instead of rebuilding it. And leadership can read coverage without
commissioning three lists that will not reconcile.

None of that requires the three teams to merge. It requires them to be pointed at
the same object.