A relationship manager inheriting 40 client relationships needs the history behind each one before the first client call: how the relationship began, what has been promised, who the client trusts, which decisions were already made and why, and what was offered and declined. Most of that is already recorded in Salesforce, SharePoint and Teams.
What does a new RM actually inherit?
More than a list of names.
On paper, a new relationship manager inherits a book: forty client records, each with a balance, a product set and a review date. That part transfers cleanly. The CRM reassigns it in a click.
What doesn't transfer is everything that made each relationship work:
- Why this client moved their business here, and what nearly made them leave.
- What the previous RM agreed to on a call and never wrote into a field.
- Which contact makes the decisions and which one answers the email.
- What was proposed last year, declined, and should not be proposed again in the same words.
Your onboarding covers licensing, attestations and system access, as it must. Your procedures are documented thoroughly, for good reason. The client-context part of onboarding is usually a shadowing schedule with the outgoing RM. It's a sound plan. It depends on Dave, and Dave left.
Where does the history live?
In three systems, and none of them is the onboarding program.
- SharePoint. Procedures, product documentation, credit memos, review templates. This is what the firm does and how.
- Salesforce. The client record: accounts, contacts, logged activity, notes from calls and reviews. This is what happened with each client.
- Microsoft Teams. The channel threads where a pricing exception was discussed, where operations flagged a problem, where the previous RM asked for help. This is why things were done the way they were.
The record is there. It was written at the time, by the people involved. It has never been read in order for one client, let alone forty, and a new RM in their first month has neither the time nor the map.
So the context arrives another way. The client mentions a commitment the new RM has never heard of. A colleague remembers something at the coffee machine. The new RM pieces it together, one conversation at a time, while already responsible for the relationship.
What should a client-by-client handover cover?
For each client in the inherited book, five things in writing.
- Relationship history. How the client came to the firm, what they hold, what has changed, and how the relationship has gone. A short narrative, not a field list.
- Open commitments. Anything promised and not yet delivered: a fee review, a callback, a product change, a document.
- Who the client trusts. The contacts on both sides. Who at the client decides, and who at your firm they have relied on.
- Decisions already made, and why. Pricing exceptions, structure choices, service arrangements, with the reasoning recorded at the time.
- What was pitched and declined. What was offered, when, and the reason it was turned down.
Written by hand, that's a serious piece of work for one client. For forty, it's weeks of a senior person's time, which is why the shadowing schedule exists instead.
There's a cost to the gap either way. The new RM is on payroll from day one, and until they have this, a good share of each week goes to reconstructing it, with colleagues stopping their own work to help. The onboarding cost calculator puts your own numbers on that.
Why should every statement link to its record?
Because in financial services, an unsourced statement about a client is a liability, however accurate it is.
A handover note that says "the client was promised a fee review in Q2" raises three questions immediately. Who promised it? When? Where is that written down? If the note can't answer, the new RM either acts on hearsay or goes digging, and neither is a comfortable position in a regulated business.
A citation answers all three. Every statement in the handover should link to the activity record, document or thread it came from. That does two jobs:
- The manager can check it. Before the new RM sees anything, their manager can open the source behind any claim and correct what's wrong or out of date.
- Your auditor can check it. The path from statement to record is visible. Nothing in the document rests on memory.
This is what Firstweek writes. It reads Salesforce, SharePoint and Teams through read-only connections and writes each new RM one cited onboarding artifact covering the clients, people and decisions they are inheriting. Every statement links to the record it came from. The hiring manager approves it before the new RM sees it. There is a sample written for a relationship manager inheriting a book.
How do the security review and the pilot fit together?
The review comes first. The pilot starts after it.
A tool that reads client records should go through your InfoSec process, and Firstweek expects it to. Send your questionnaire and it gets answered. These are the facts a reviewer will want up front:
- Connections are read-only. Firstweek never writes to, changes or deletes anything in a connected tool.
- Content is summarized at ingest. Raw messages and documents are never stored; only summaries persist.
- Single sign-on with Microsoft Entra ID or Google, role-based access and audit logging are built in.
- Your admin chooses which sites, channels and records are in scope. Nothing outside that scope is read.
- Firstweek holds no third-party security certification. If your policy requires one from every vendor, it won't pass today.
The full detail is on the security page, and what is read from each tool is on the Microsoft 365 and Salesforce connection pages.
A pilot is one real hire: a relationship manager inheriting an existing book. The 30 days start when your security review clears, not at the first call. Nothing is purchased during it. At the end, you and the RM's manager decide whether it's worth keeping.
FAQ
How should you onboard someone inheriting 40 client relationships?
Give them the history of each relationship in writing before their first client call: how it began, open commitments, who the client trusts, decisions made and why, and what was declined. Link each statement to its record.
Where does client history live when an RM moves on?
In the CRM notes and logged activity, in document libraries, and in the team's channel threads. It stays there after the RM has gone. The work is assembling it.
Is Firstweek certified to SOC 2 or ISO 27001?
No. Firstweek holds no third-party security certification. Security reviews run on your own questionnaire.
When does the pilot start?
When your security review clears. The 30 days run from that point, on one RM inheriting an existing book.
Talk to us about a pilot. The 30 days start after your security review, not before. Start a pilot or see a sample artifact. How it works for financial services.