You Inherited the Account and Renewal Is in Three Weeks: A 20-Minute Prep Routine

You open the account on a Monday. Renewal date is twenty-two days out. The rep who owned it left in March, the CSM who owned it before that left in November, and the entire history in the CRM is nine activity records that say some version of "good call, they're happy."

That is the job now. Rep churn in this industry means somebody is always walking into a renewal cold, and more often than not that somebody is you, and nobody is going to give you two weeks to get up to speed. You get an afternoon, maybe.

So here is the triage I run. It takes about twenty minutes if you have the tabs open and you do not go wandering. The point is not to become an expert on the account. The point is to walk into the call knowing whether you are running a renewal or running a save, because those are two completely different calls and the worst outcome is discovering which one you are in at minute eighteen.

Why the CRM is not going to help you

Let me get this out of the way, because most reps waste their first ten minutes here.

CRM notes on a healthy-looking account are written by people who were not worried. They are optimistic by construction. "Good call, they're happy" is what a rep writes when nothing specific happened and they need to log something before the end of the day. It is not a lie. It is just not evidence.

Worse, the notes are written from the seller's side of the table. They record what the seller said and what the seller hoped. They almost never record who was in the room, who stopped showing up to the QBRs, or what the customer asked for and did not get.

So read the notes, sure, but read them for names and dates, not for sentiment. Who is mentioned? Who used to be mentioned and stopped? When was the last real conversation, as opposed to a scheduling email logged as an activity? That is all you need out of the CRM, and it should take you three minutes.

The truth about the account is in the product and in the support queue. Go there.

Minutes 1 through 8: usage data

This is the single highest-value block of the twenty and I would give it more time if I had it.

You are not looking for a health score. Health scores are averages, and averages hide exactly the thing you need to see. You are looking for individual humans and whether they still log in.

Pull the user list. Sort by last login. Now you have three groups.

People who log in every week. These are your champions whether or not anyone ever labeled them that. If the person your CRM lists as the champion is not in this group, your champion is not your champion.

People who used to log in and stopped. This is the group that matters most and the one nobody looks at. Find the month the drop happened. Then go find out what else happened that month. A wave of users going dark in the same six-week window is almost never a coincidence — it is a manager change, a competing tool getting rolled out, a policy change, or a bad release. Somebody knows the answer and you are going to ask them.

People who were provisioned and never activated. If the customer bought fifty seats and thirty of them have never had a first login, you do not have a renewal problem, you have a math problem that the customer's finance team is going to find before you do. They are paying for something they can count and see they are not using.

Write down the actual names. Not "usage is down." Names. "Priya in ops logged in four times a week through August, then nothing." That sentence, said out loud on the call, is worth more than any deck you could build, because it tells the buyer you looked.

While you are in there, look at what people do when they log in. There is a difference between an account where twelve people run reports every Monday and an account where twelve people click in, look at a dashboard, and leave. The first one is embedded in a workflow. The second one is a browser tab somebody feels guilty about. Only one of those survives a budget review.

Minutes 9 through 13: the support tickets

Open every ticket from the last twelve months. Read the subject lines first, all of them, in one pass. You are looking for repeats.

One ticket about a broken export is a bug. Five tickets about a broken export, filed by three different people, is a story the customer has been telling internally for months, and the story ends with "we've been asking them about this since spring." You need to know that story before they tell it to you, because if you hear it for the first time on the renewal call, your only available response is to look surprised, and looking surprised is the same as admitting nobody was paying attention.

Then read the tickets that got escalated, and read who escalated them. When a director files a support ticket personally, something went wrong badly enough that it reached them. That is a name for your list.

Then look at the tone. Support tickets are the one place in your company's systems where customers are allowed to be annoyed, and they take the opportunity. Somebody writing "this is the third time" in a ticket in February is somebody who will bring it up in the renewal conversation.

One more thing here, and reps skip it constantly: look for tickets that were closed without a real resolution. "Closed — no response from customer" is often not a resolved issue. It is a customer who gave up on you and worked around it. Sometimes the workaround is a spreadsheet. Sometimes the workaround is a competitor's free tier.

Minutes 14 through 17: who left

Now the org chart. This is the block that saves renewals nobody thought were at risk.

Software does not get churned by companies. It gets churned by people, and specifically it gets churned by people who did not sign the original contract and feel no ownership of it. The person who bought your product had their name on the decision. Their successor inherited a line item.

So: is the economic buyer still there? Is the champion still there? Is the person who ran the implementation still there? Check LinkedIn, not your CRM — your CRM has whatever somebody typed eighteen months ago. LinkedIn has what happened.

If your buyer left, find out who took the role and when. A new VP in the seat for less than a year is auditing every contract they inherited, because that is what new VPs do, and that is what you would do. That is not a hostile act. But it means your renewal call is a first meeting with a stranger who has a spreadsheet of everything they are paying for, and you should treat it as one.

Also look at the direction the org is moving. Job postings tell you a lot. A team that is hiring for the function your product supports is a team investing in it. A team that has not backfilled two departures is a team shrinking, and shrinking teams cut seats.

And check whether the champion who left went somewhere else in the same industry. That is a separate conversation for a different quarter, but write the name down.

Minutes 18 through 20: send exactly two questions

Here is the part that changes the call, and almost nobody does it.

Before the renewal call, send an email with two questions. Not an agenda. Not "looking forward to connecting." Two questions, and they should be the two you cannot answer from the data you just pulled.

The reason is simple. If you walk in without them, the first twenty minutes of the call become archaeology — you asking what happened, them explaining, you taking notes, and then a rushed five minutes at the end where you try to do the actual work. You spend the meeting learning things you could have learned in an email, and then you ask for a decision from someone who has just spent twenty minutes narrating their own frustration.

Send the questions ahead and the call starts at the answers.

What the two questions are depends on what you found. But they are usually some version of:

"I noticed usage from the ops team dropped off around August and I want to understand what changed on your side before we talk — was that a process change, a team change, or something on our end?"

And:

"Who else needs to be comfortable with this renewal besides you? I would rather bring them in now than surprise them later."

That second one does more work than it looks like. It gets you the real decision path, it flushes out the finance review you did not know about, and it is a normal, unthreatening thing to ask. Nobody has ever been offended by being asked who else should be in the room.

Keep the email to four sentences. Say you have taken over the account, say you have gone through the usage and the ticket history, ask the two questions, propose the time. Do not attach anything. Do not write a paragraph about how excited you are.

The first thirty seconds when you are new

Say it plainly. That is the whole technique.

"I took over this account in April. I did not want to walk in here pretending I have been with you the whole time, so I spent a few hours going through the usage data and every support ticket from the last year before this call. I have some things I want to check with you."

That is it. Fifteen seconds. Then ask your first question.

What you are doing is trading a weakness for a credential. Yes, you are new. But you did the work, and you are telling them you did the work, and that is a sharper signal than continuity would have been. Half the reps who "owned" the account for two years never opened the usage report.

What you must not do is fake continuity. Do not say "we" about things you were not part of. Do not say "as we discussed last quarter" when you have read a two-line note about a conversation you were not in. Customers can hear it, and the moment they catch you, everything else you say gets discounted. You will be the fourth rep they have met and the first one they caught bluffing.

Also do not over-apologize. "I'm so sorry, I know you've had a lot of turnover on our side" invites them to agree with you and spend four minutes on it. One clean sentence acknowledging you are new, then forward.

The five-minute fork: renewal or save

By minute five you should know which call you are in. Here is how to tell.

You are running a renewal if they answer your questions in a normal tone, they can name a thing the product does for them without you prompting, and they treat the date as a formality. Renewals feel administrative. Somebody says "yeah, send it over, I just need Marcus to sign off" and you spend the rest of the call on expansion, on the users who never activated, on what next year looks like. Do not get greedy and do not manufacture a problem. Confirm the path, confirm the paperwork, confirm the people, and get off.

You are running a save if you hear any of these. They are vague about value in a way that suggests they have never had to articulate it. They mention a competitor by name, even casually. They say "we're looking at everything right now." They cannot tell you who signs. Or — the loudest one — they answer a question about usage by explaining a workaround they built. Somebody who has built a workaround has already decided the product does not do the thing.

The tell I trust most is silence in the wrong place. You ask what the team gets out of it and there is a beat before they answer. That beat is them constructing an answer instead of retrieving one. Retrieval is fast. Construction is slow.

If you are in a save, stop selling immediately. Do not go to the pricing conversation, do not offer a discount, do not start listing features from the roadmap. A save call is a diagnostic call, and the goal of the first one is to get the real reason out of them and to get a second meeting with the person who actually controls the decision. I have written the scripted version of that conversation in the SaaS renewal call script for a save you are six weeks from losing, including what to say when they name a competitor and what to do when the champion has already left the company.

The shape of the save changes with what you sell. In freight and 3PL, the account usually goes quiet because the shipper's ops team stopped trusting the tracking data, and the recovery runs through proving accuracy on specific lanes — the freight and 3PL version of the renewal script walks through that one. In staffing and recruiting, it is usually a fill-rate argument and a procurement review happening in parallel, which is a different sequence again. Same twenty minutes of prep, different second half of the call.

What twenty minutes actually buys you

It does not buy you the relationship. You are not going to have in three weeks what the last rep had in two years, and if the account was going to renew on relationship alone it was never at risk in the first place.

What it buys you is the ability to be specific. Specific is the only currency you have when you are new. "I saw that Priya stopped logging in around the time your ops team reorganized, and I want to know whether that is a workflow problem or a people problem" is a sentence that makes you credible in nine seconds. It says you looked, it says you are not going to waste their time, and it puts a real question on the table that they have to engage with.

The alternative is walking in and asking "so how have things been going?" Which is the question every rep before you asked, and which generated all those notes that said "good call, they're happy," and which is why the account is in the state it is in.

The other thing prep buys you is the right to be surprised in private. Everything you learn from usage data and tickets is something you did not have to learn live, on the call, in front of a buyer, with your face doing whatever your face does. Save your live reactions for the things you genuinely could not have known.

If you want to make it automatic, run the call before you run the call. Take the two questions you drafted, take the objection you know is coming from the ticket history, and say the whole thing out loud to something that pushes back — that is exactly what I built DrillCall for, and it is what I would do with the twenty minutes after the twenty minutes. Reading a script is not the same as having said the words once.

Then send the email. Two questions, four sentences. Twenty-two days is plenty.