Renewal Call vs Upsell Call: Running Both at Once Is How You Lose Both

Two calls that look identical on the calendar

Both are on the calendar as a thirty-minute Zoom with the same buyer. Both have a number attached. Both get reported to the same forecast. So reps treat them as one motion with two outcomes, and they walk in planning to secure the renewal in the first fifteen minutes and float the expansion in the last ten.

That plan fails almost every time I have watched it run. Not because the rep is bad. Because the two conversations are built on opposite emotional footing, and running them back to back inside one call forces the customer to hold two contradictory thoughts at once.

A renewal call is about restoring confidence. An upsell call is about extending it. You cannot extend something you are still in the middle of restoring.

When you combine them, here is the sentence the customer actually hears: you want more money for the thing that already disappointed me. They will not say it out loud. They will say "let me take that back to the team," and then the renewal you thought you had closes late, at a discount, or not at all.

So let me put the two calls side by side — objective, opening line, attendees, proof, good outcome — and then give you the sequencing rule I would enforce on any team I ran, plus the one exception where combining them genuinely works.

The renewal call, stripped to its parts

The objective

The objective of a renewal call is not to renew. That sounds like word games, so let me be precise. The objective is to get the customer to say out loud what has gone wrong, and to leave the call believing that the next twelve months will be different in a way they can describe to their own boss.

The signature comes after that, sometimes on the same call, usually not. If you go in aiming at the signature, you will steer away from the ugly part of the conversation, because the ugly part feels like it costs you the deal. It is the deal.

The opening line

A renewal opening has to give the customer permission to complain. Most of them are polite by default and will tell you everything is fine right up until the day they leave.

What I use, more or less:

"Before we talk about the term, I want to spend most of this call on the last year. My read is that it did not go the way either of us wanted. I would rather hear the unvarnished version now than find out in procurement. What is the thing you would change first?"

Notice what that does. It names the problem before they have to. It costs you nothing — they already know it went badly — and it removes the awkward job of being the first person in the room to admit it.

Compare that to the opening most reps use: "So, how's everything going with the platform?" That question has exactly one answer, and the answer is "good, yeah, pretty good," and now you have nothing to work with. The full sequence for the version where you are genuinely behind is in the SaaS renewal script for a save call you are six weeks from losing, and the thing to notice when you read it is how little of it is about the product.

Who should be on it

More senior than you think, on both sides.

On their side, you want the person who signs and the person who uses. If only the champion shows up, you are getting a filtered version of the year and you will not hear the objection that actually kills you. If only the economic buyer shows up, you get a spreadsheet conversation and no story.

On your side, bring somebody with authority to fix things. A CSM who can commit to a support tier, a solutions person who can commit to a rebuild of the workflow, someone who can say "yes, we will do that, and here is when." A renewal call where every remedy is "let me check internally" is a call that restores nothing.

I would rather bring one senior person and no deck than three people and a QBR slide.

The proof you bring

Proof in a renewal is proof of change, not proof of value. This is where most reps get it backwards. They arrive with a usage report showing everything the customer got, which reads as an argument, and nobody has ever been argued out of a bad year.

Bring instead: what broke, what you have already changed about it, what is still open, and who owns each open item by name. If a ticket sat for three weeks, say so before they do. Own it flatly and without a paragraph of context. Context sounds like excuses.

In regulated industries this matters even more, because the failure has a clinical or compliance shadow attached to it. The healthcare renewal script for saving a clinical documentation account after a bad year is built almost entirely around this idea — you are not defending the product, you are demonstrating that the organization behind it noticed and reacted.

What a good outcome looks like

A good renewal call ends with the customer describing the fix to you. Not you describing it to them. When they say "so the way I'd explain this internally is that you're putting a named engineer on the integration and we get weekly check-ins through Q1," you have won, whether or not the paper is signed.

Second-best outcome: a specific, dated next step tied to a specific person. Worst outcome that still counts as progress: they tell you the real objection for the first time.

And notice what is not on that list. Nobody bought anything new.

The upsell call, stripped to its parts

The objective

The objective of an upsell call is to get the customer to connect a result they already believe in to a place it has not reached yet. Second team, second region, second workflow, more seats, higher tier.

The emotional starting point is completely different. In a renewal you are digging out of a hole. In an upsell you are standing on something solid and pointing at the next thing. If you are not standing on something solid, you are not on an upsell call. You are on a renewal call that has not been labeled correctly yet.

The opening line

An upsell opening should reference a result, and it should be the customer's result, described in the customer's language.

"Last time we spoke, the ops team had cut their weekly reconciliation down to a single pass and Dana said it was the first quarter she hadn't worked a weekend. I want to talk about the second warehouse, because I think the same thing is sitting there untouched. Is that a fair read?"

That opening only works if the result is real and specific. Generic openings — "we've seen great adoption" — do the opposite of what you want, because they signal that you have not actually looked at the account and you are about to ask for money anyway.

Who should be on it

Different people. Genuinely different, and this is the part that surprises reps.

The person who saved you in the renewal is often the wrong person for the expansion. Your renewal champion is the one who took the hit internally for choosing you. Asking them to also carry the expansion is asking them to spend political capital twice on the same vendor. Sometimes they will. Often they will quietly stall.

The upsell buyer is usually the leader of the team that has not adopted yet, and your renewal champion's job is to introduce you, not to sell for you. On your side, bring fewer people than for a renewal. A well-run expansion conversation is a rep and a buyer. Extra bodies make it feel like a campaign.

The proof you bring

Here proof is proof of value, and it needs to survive scrutiny. The single most common way an upsell call dies is that the rep asks for more seats in a room where somebody has the utilization report open.

If the seats you already sold are half dormant, you do not get to ask for more of them until you have an answer for why. The answer might be a good one — the dormant seats belong to a team that never got onboarded, and you have a plan for that. But you need it ready before you walk in, which is the whole premise of the upsell script for SaaS customers that survives a seat utilization report.

The freight and 3PL version of this problem is subtler. The proof is not seats, it is lanes and load volume, and the risk is that a routine check-in turns into a price conversation you did not want. The freight and 3PL upsell script for turning a check-in into an expansion is mostly about controlling that turn.

What a good outcome looks like

A scoped next step with a new stakeholder attached. "Send me the pricing for the second region" is fine. "Let's get Marcus on a call, he runs the second region" is better, because expansion is an access problem far more than a pricing problem.

The outcome you do not want is a vague yes. Vague yeses on expansion calls are how pipeline gets built out of nothing and how forecasts get embarrassing.

Side by side

	Renewal call	Upsell call
Emotional job	Restore confidence	Extend confidence
Opening move	Name the problem first	Name the result first
Their attendees	Signer plus user	Leader of the un-adopted team
Your attendees	Someone who can commit to a fix	Just you, usually
Proof	Evidence of change	Evidence of value
Talk ratio	They talk most	Roughly even
Good outcome	They describe the fix back to you	A scoped step with a new name attached
Bad outcome	"Everything's fine"	"Send me something"

Read the two columns again. There is not one row where the right behavior is the same. That is why the combined call fails — you are trying to be contrite and expansive in the same half hour, and human beings can hear the seam.

The sequencing rule

Here is the rule, and I would put it in writing for the team.

Renewal first. Upsell no earlier than the next value milestone. Unless usage data says otherwise.

Three parts, so let me take them in order.

Renewal first means the renewal conversation closes completely — signed, or at minimum agreed and in procurement — before anyone opens an expansion thread with that account. Not the same week. Closed.

The next value milestone is the part people skip, so define it concretely for every account. A milestone is an event where the customer experiences the thing they bought, after the fix you promised. First clean month-end close on the new workflow. First full cycle with the integration working. The onboarding of the team that was never onboarded. It is an event, not a date on a calendar. "Ninety days after renewal" is not a milestone, it is a countdown, and if nothing good happened during those ninety days you have just scheduled a second bad conversation.

The reason to wait for the milestone rather than the clock is that the milestone gives you your opening line. You cannot say "the ops team cut reconciliation to a single pass" until the ops team has actually done it. Wait for the sentence to become true, then make the call.

Unless usage data says otherwise is the release valve. If the customer is already pressed against a hard limit — seats exhausted, volume at the cap, a team using the product through a shared login — the expansion conversation is not you asking for money. It is you solving a problem they are already having. Constraint-driven expansion is not really an upsell, it is a service call with a purchase order at the end, and it can happen whenever the constraint appears.

The test is simple. Would this conversation happen even if you got paid nothing for it? If a team is sharing a login, you would call them about that regardless. Go ahead. If you are pitching a tier they have not asked about and are not blocked by, wait for the milestone.

The one exception where combining them works

There is exactly one situation where I will run both on a single call, and it is narrower than most reps want it to be.

The exception is when the expansion is the remedy.

Sometimes the reason the year went badly is that the customer bought the wrong shape of the thing. Too few seats to reach critical mass, so adoption never took. The wrong tier, so the integration they needed was never available to them. One region deployed when the process spans three, so the data was always incomplete and nobody trusted the reports.

In those cases the fix and the expansion are the same object, and separating them makes you look like you are hiding the ball. But you have to run it in a very specific order, and the money has to come last and small.

Diagnose first, at length. Get them to agree on the cause before you name a remedy. Then present the remedy as a remedy: "the reason adoption stalled is that finance was never included, and the tool only works when the whole approval chain is inside it." Then — and this is the part reps rush — ask permission to talk about the commercial side: "there is a commercial piece to that. Do you want to get into it now or should I put it in writing?"

Half the time they will say put it in writing, which is fine. You have made the argument. And when you do quote it, discount it or absorb it into the renewal term, because charging full freight to fix your own mis-scope is how you win the quarter and lose the account.

If you cannot honestly say the expansion is the remedy, this exception does not apply to you. Reps talk themselves into it constantly. Be strict.

Reading the account before you pick the call

Most of this is moot if you cannot tell which call you are actually on. Reps guess, and they guess optimistically, because expansion is more fun to prepare for than a save.

The account is in save mode when the signals point at fading involvement rather than active complaint. Your champion has stopped replying quickly. Meetings get rescheduled by an assistant rather than by them. Support tickets drop off — which reps read as good news and is usually the opposite, because people stop reporting problems in a tool they have stopped depending on. Somebody new appears in the org chart above your buyer. Procurement reaches out before you do. And the tell I trust most: the customer starts asking about contract mechanics — notice periods, data export, term length — in a conversation that was supposed to be about the product.

The account is expansion-ready when other people start showing up uninvited. Someone you have never met joins a call. You get a question from a team that was never in scope. The customer asks about a capability adjacent to what they bought. Usage is not just high, it is pressed against something — the seat count, the volume cap, the record limit. And the cleanest signal of all: they reference your product in the first person plural. "The way we handle intake now" rather than "the way your tool does it." When the product has become part of how they describe themselves, you can talk about more of it.

When the signals are mixed — and they often are, because a big account can have one thrilled team and one furious one — treat it as save mode and run the renewal properly. The cost of running a renewal on an expansion-ready account is that you delayed some revenue by a quarter. The cost of running an upsell on a save-mode account is the account.

What I would do next

If I were running this on a team, I would not send a memo about it. I would make every rep run the two calls back to back in practice, same fictional account, same buyer persona, and I would listen for whether the first ninety seconds actually sound different. They almost never do at first. Reps have one greeting and one energy level, and the whole argument of this post is that the two calls need two of each.

That is the specific thing DrillCall is built for — putting a rep on a live simulated renewal where the buyer is quietly disengaged, then a simulated upsell where the buyer has the utilization report open, and letting them hear the difference in their own voice. Cheaper to find out there than on the account.

The rule holds either way. Renewal first. Upsell at the next real milestone. And when you are tempted to do both in one call because the calendar is tight, remember what the customer hears.