You just inherited forty accounts. Your first 90 days are not about learning the product

On your first day you get a laptop, a mailbox, and a spreadsheet with forty client names on it. Thirty-eight of them mean nothing to you. Somewhere in that list are two accounts already drifting toward the exit, one client who is going to test you in week three with a question about something agreed last October, and one relationship that has been carried for two years by a person who no longer works here.

Your onboarding plan, meanwhile, is mostly about the product. Sit with sales, shadow a call, read the wiki, learn the pricing tiers. All useful, all beside the point. Nobody is going to catch you out on the pricing tiers.

What you are actually ramping on

You are not ramping on the product. You are ramping on history you were not present for, and you are doing it while the clients grade you from the first email. That grading is the part new account managers underestimate. From the client's side of the table there was a person who knew them, and now there is a person who does not, and the transition is something that has been done to them rather than something they asked for. They are not hostile about it. They are just quietly waiting to find out how much re-explaining their life is about to require.

This is why clients experience being forgotten as being devalued. When you ask a question you should already know the answer to, you are not revealing that you are new. You are revealing that the four years they spent building a relationship with your company were stored in one employee, and that employee is gone. That is a much larger and more alarming piece of information than anything about you.

Why reading the archive does not work

The standard advice is to read back through the mail, and it is given by people who have never tried it against forty accounts. Fourteen months of another person's threads is not context, it is homework, and it is homework with no completion criterion. You do not know what you are looking for, most of what you read is operational noise you cannot distinguish from signal without the history you are trying to acquire, and the useful material is scattered across hundreds of threads in single sentences. Three days in, you will have read deeply about two accounts and nothing about thirty-eight.

Search does not rescue you either, because search only retrieves what you already suspect exists. The context that hurts you is by definition the context you did not know to look for. So the plan below is not read everything. It is triage, then targeted depth, in an order chosen by what will cost you most if you get it wrong.

Days 1 to 30: triage by risk, not alphabetically

Resist the instinct to work down the list in order. Rank the book first, then spend the month where the exposure is.

• Sort by revenue, then by fragility. Fragility is not size. A mid-sized account on its third account manager in two years is more fragile than your largest client, who has survived everything.
• Find the open loops before anything else. What did your predecessor promise that has not landed, and what have clients asked that nobody answered? These are the things that blow up in week two, and they are the cheapest possible early win if you catch them first.
• Identify who is actually quiet. Not who has written recently, but who has written less than they used to. Any account that has slowed noticeably in the last two months is a fire you inherited, not one you started.
• For your top ten, write one paragraph each from the mail: what they buy, what went wrong most recently, who the real decision-maker is, and what they have already said no to. One paragraph, not a page. You are building recall, not a report.
• Ask your predecessor exactly one question per account if they are still reachable, and make it the same question: what would I not know from reading the email? The answers are usually the texture that never got written down.

Everything in that list is doable by hand, and teams have done it by hand for decades. It takes about three weeks and it is the least productive three weeks of the year. A maintained relationship record turns the same work into an afternoon, which is the reason we built Sektra to read existing Gmail history rather than start counting from the day it is installed. That one design decision is the whole difference at this moment: a tool that begins empty is useless to someone inheriting a book, because the history is precisely what they are missing.

In practice it means a new joiner opens an account they have never heard of and sees it already assembled. Commitments outstanding in both directions with dates attached. Questions the client asked that are still unanswered, including the ones sitting inside threads that look handled. The normal rhythm of contact for that specific relationship, and whether it was warming up or cooling down at the moment it changed hands, which is the single most useful thing to know about an inherited account and the single hardest to work out manually. Whatever the record does not answer, they ask the Copilot, the way they would have asked the person who left, except this colleague has read every thread and is still here.

Days 31 to 60: the introduction that is not a reset

Most transition emails are a small disaster written with good intentions. I have taken over your account, I would love to set up a call to learn about your business and understand your goals. Read it from their side: this person knows nothing, and now I have to spend an hour teaching them what I taught the last one. You have asked for a favor in your first message.

Introduce yourself inside the ongoing conversation instead. Reference something real and specific, ideally something you can act on. I have picked up the account from Daniel, and the first thing I did was chase the revised scope you asked about on the fourth, which is attached. I can also see the reporting question from October never got a proper answer, so I am fixing that this week. Note what that message does: it proves continuity, it delivers something, and it does not ask them for anything. The call comes later, once you have earned it.

For the three or four accounts you flagged as fragile, do this by phone rather than email. A handoff is exactly when a quiet client decides quietly, and voice is much better than text at telling you which way they are leaning.

Days 61 to 90: follow-through is the only proof available

By now you have said a number of things you intend to do. This is the entire game, and it is worth being blunt about why. You have no track record with these people. They cannot evaluate your judgment yet, they have no basis to trust your advice, and your competence is a claim rather than an observation. The only evidence available to them in the first quarter is whether the things you said would happen on Thursday happened on Thursday.

So track every commitment you make in this period with something close to paranoia, and treat inherited commitments as yours. The promise your predecessor made in March is now a promise you are keeping or breaking, and the client does not experience the distinction. Teams lose transitional accounts through accumulated small slippage far more often than through any single failure, and the exit conversation says something vague about communication, because no individual moment was worth naming.

Somewhere around day 75, do a second pass on the quiet list from month one. Anyone who has not warmed up after two genuine touches has a reason, and finding that reason at day 75 rather than at renewal is the difference between a save and a post-mortem. The playbook for reading silence covers what to send and what to read into the reply.

Three mistakes that cost accounts in a transition

• Announcing the change as a change. Every email that centers your arrival reminds the client that their history just got deleted. Center the work instead, and let the introduction be a sentence rather than the subject.
• Working the list alphabetically. The first two weeks are your only period of protected attention. Spending them on accounts that were never at risk means the fragile ones get you at your busiest, in month three, after they have already decided.
• Treating inherited promises as somebody else's. It is the fastest way to confirm the client's real fear, which is that the company as a whole does not remember what it agreed to. Honor them or renegotiate them explicitly, but never let one simply lapse.

Ninety days from now, the accounts you keep will not be the ones where you learned the product fastest. They will be the ones where a client noticed, somewhere around week six, that the new person seemed to know what was going on. That impression is buildable, and it is mostly built out of things that were already sitting in the mailbox.