Decide what belongs in the client's CRM
The client's CRM is the system of record for their pipeline. Opportunities, account ownership and forecast data belong there, in the client's conventions. Log what the client team needs to act on, not every thought you had about a contact.
Keep your own side of the work separate
What does not belong in a client CRM:
- Why a person in your network matters to you, and how you know them.
- Your relationship with the same person across other clients.
- Your own record of contributions: introductions made, meetings opened.
Keeping this separate protects your network and avoids exposing one client's context to another.
One person, several conversations
Senior networks overlap. If the same CFO is relevant to two clients, treat each as a separate conversation with its own status and next step. Mixing them is the fastest route to an awkward message, or a confidentiality problem.
Plan the day across engagements, not within one
Start the day with a single view of what is waiting on you everywhere: replies due, follow-ups promised, first messages after a new connection. Then decide where your limited hours go. Working client by client tends to favour whoever shouts loudest.
Write it down once
Duplicate logging is the core of CRM overload. Record a conversation once in your own workspace, and add only the commercially relevant summary to the client's system yourself.
Where a tool can help
YourSalesDay.com is built for the executive's side of this work: contacts linked to several engagements with separate dialogues, private relationship notes, and a ranked daily overview. It does not connect to client CRMs, and it never contacts anyone on your behalf. You send every message yourself. Access is currently by invitation.